Purpose-built for professional services firms, the Introhive Model Context Protocol (MCP) Server provides AI assistants like Microsoft Copilot with real-time access to your firm’s collective relationship network.
By connecting Microsoft Copilot to Introhive, you can ask natural language questions to identify who knows a key prospect, uncover at-risk accounts, surface cross-sell signals, and generate meeting briefs based on your firm’s historical engagement data.
The MCP Server exposes the ask_introhive tool, allowing your AI assistant to “discover” your Introhive capabilities and dynamically synthesize relationship data into actionable insights and recommendations.
Overview: What Users Can Do
Find contacts and relationships — top contacts at a company, strongest colleague relationships, key decision-makers
Explore organizations — overview of any organization in your Introhive data, relationship scores, engagement trends
Review activity — recent meetings, email patterns, communication history with specific people or companies
Ask follow-up questions — “Who else do we know there?”, “Show me their email history” and the agent maintains conversation context
Disambiguate entities — when multiple matches exist (e.g. “Microsoft” matches several entities), the agent asks the user to pick the right one
Combine with web search — enrich relationship insights with relevant, real-time information
Use Cases:
Meeting Prep: “Summarize our last three interactions with [Company].”
Warm Introductions: “Who is the best person to introduce me to the CEO of Acme Corp—and why?”
Relationship Risk: “Which top accounts have declining relationship scores?”
Event Targeting: “Which of our top-tier contacts are based in [City Name]?”
1. Prerequisites
The Introhive MCP Server exposes the ask_introhive tool to Microsoft Copilot, empowering it to answer natural language questions about your firm’s relationship strength, engagement activity, and network paths.
Before you begin, ensure you have:
Active Introhive Licenses: Every user interacting with the agent must have an active Introhive user account and Ask Introhive access.
Admin Access: You must have administrator permissions in Introhive to create OAuth applications.
Microsoft Copilot Studio: Access to the full Copilot Studio at copilotstudio.microsoft.com. The simplified agent builder inside Microsoft 365 does not support MCP server connections.
Specific SKUs (Optional): Specialized datasets, like Alumni tracking, require the relevant organizational SKU to be active.
2. Administrator Setup & Configuration Details
Establishing the connection requires creating an OAuth 2.0 application in Introhive and mapping those credentials into Copilot Studio.
Step 1: Create a Placeholder OAuth Application in Introhive. Because of a circular dependency where Introhive requires a Redirect URI to create the app, but Copilot Studio does not provide the Redirect URI until the tool is created, you will use a placeholder first.
Navigate to your Introhive instance:
https://[instance].introhive.com/profiles/oauth_applications.Click Create OAuth Application.
Enter an Application Name (e.g., “MS Copilot MCP”).
For Redirect URI, enter a placeholder like
https://introhive.com.Under Scopes, check AI Agents JWT (Note: This cannot be combined with other scopes).
Click Create and securely save your generated Client ID and Client Secret, as they cannot be retrieved again.
Step 2: Configure the Server in Copilot Studio. In Copilot Studio, go to Tools > Add a tool > Model Context Protocol, and enter the following parameters:
Server Name: Introhive MCP
Server URL:
https://[instance].introhive.com/pollen/mcpAuthentication Type: OAuth 2.0 (Manual)
Client ID: (Your generated ID from Step 1)
Client Secret: (Your generated Secret from Step 1)
Authorization URL:
https://[instance].introhive.com/oauth/authorizeToken / Refresh URL:
https://[instance].introhive.com/oauth/tokenScopes:
pollenchain_jwt
Step 3: Update the Redirect URI (Crucial). Once the tool is created, Copilot Studio generates its Redirect URI. To find it, open the tool from the tools list in Copilot Studio (refresh the page if it doesn’t appear). This opens its configuration in Power Automate. Go to the Security tab, scroll to the bottom, and copy the Redirect URL. Then go back to Introhive to update the placeholder.
Return to
https://[instance].introhive.com/profiles/oauth_applications.Edit your “MS Copilot MCP” application and replace
https://introhive.comwith the exact Redirect URI provided by Copilot Studio.Save. The connection will fail if this URI does not match exactly.
3. User Authentication & Security
The Introhive MCP is built on a “Human-in-the-loop” security model.
Per-User Authentication: The first time a user prompts Copilot for relationship data, they will be asked to log in with their personal Introhive credentials and authorize the connection.
Short-Lived Tokens: Access is granted via short-lived OAuth access tokens that refresh automatically, ensuring no long-lived credentials are stored.
Data Privacy: Data is encrypted in transit via TLS 1.2+, and no customer relationship data is retained or used to train third-party AI models. Access generally mirrors the permissions users have in the Introhive web app, though minor context boundaries may vary.
4. Capabilities & Example Queries
The ask_introhive tool is highly versatile. Copilot will automatically discover how to use the tool and handle data queries, summaries, and recommendations.
Try asking Copilot:
Meeting Prep: “Summarize our last three interactions with [Company Name].” or “Who from our team has met with [Contact Name] recently?”
Warm Introductions: “Who is the best person to introduce me to the CEO of Acme Corp—and why?”
Relationship Risk: “Which organizations did we have a surge in activity with over the past year, but have since gone dormant?”
Event Management: “Which of our top-tier contacts are based in [City Name]?”
Recommended Agent Instructions
To help your Copilot agent use the ask_introhive tool effectively, add the instructions below to your agent. In Copilot Studio, open the agent’s Overview page and click Edit in the Instructions section. These are suggested instructions; tune them to your organization’s needs.
# Role
You are the Introhive Relationship Intelligence assistant. Answer questions about the organization's relationship and communication data, and when a question spans more than one of your tools, combine them into a single answer rather than making the user stitch results together.
# Combining tools
Some questions use one tool's data as context for another — e.g. "any news about Acme, and do we know them?" or "relationship strength for my open deals." Watch for loose phrasing that implies this too ("...that we have a relationship with", "...for my pipeline"). When a question plausibly spans tools, combine rather than pick one. Follow these steps in order:
1. Get the entity set from the OTHER tool first (the companies, accounts, or people the question is about).
2. Extract the concrete names from that result.
3. Call /ask_introhive with a focused question that names those entities explicitly — e.g. "Relationship strength and key contacts for: Acme, Globex, Initech" — instead of forwarding the user's original wording. - Name no more than 10 entities per call. If there are more, split them into groups of 10 or fewer and ask the same question for each group in turn. - If there are more than 30, tell the user how many there are and ask whether to narrow the list or continue in batches before calling.
4. Merge into one answer, labeling which facts came from which source.
# Using ask_introhive
Call /ask_introhive one request at a time and wait for each response. Never call it more than once at the same time — it is stateful per conversation, and a second call before the first returns will fail. Pass the conversation_id from the prior response to continue a conversation or ask a follow-up. Each call can handle at most 10 named organizations or people combined. This also applies when the user lists the names themselves.
# Disambiguation
If /ask_introhive replies asking which entity was meant (e.g. "Which Microsoft?"), stop and present the options to the user. Do not call it again until the user answers — the conversation is paused and any other call will fail. This applies when combining tools too: if entities pulled from another tool need clarification, surface the choices before continuing. When working in batches, resolve each batch fully before starting the next.
# Responses
- Only present data a tool returned. Do not fabricate or fill gaps from your own knowledge.
- Keep each tool's formatting (tables, lists). When combining sources, merge into one coherent view, not two separate dumps, and label each source.
- When results came from several ask_introhive batches, you may combine them into one list or table, but do not re-rank, total, or compare across batches — each batch was answered separately.
- Highlight key metrics such as relationship scores and contact counts.
- If a tool returns nothing, say so and suggest rephrasing.
- End answers with a relevant follow-up question when a sensible next step exists.
5. Known Limitations
To get the most out of the Introhive MCP, be aware of the following constraints:
Read-Only: The MCP server retrieves relationship intelligence (contacts, meetings, emails, engagement scores, etc.). It cannot create, modify, or delete records in Introhive.
Scope of Data: The server does not have access to financial metrics like revenue, active deals, pipelines, or contracts.
File Analysis Constraints: Copilot allows you to upload CSV files, but the Ask Introhive tool cannot analyze or ingest uploaded CSV files to cross-reference against the database.
Industry Field Requirements: If you are asking for relationships within a specific industry (e.g., “Which accounts in legal do we have the best relationships with?”), your Ask Introhive will not be pulling from Industry data fields.
6. Troubleshooting & Debugging
If you run into issues, check these common resolutions:
Authentication Errors / Connection Fails: This is almost always caused by a Redirect URI mismatch. Verify that the Redirect URL shown in Copilot Studio (Power Automate > Security tab) matches the URI in your Introhive OAuth Application exactly.
Tool Pauses or Asks for Clarification (Entity Disambiguation): If you search for a common name (like “Microsoft” or “Allen & Overy”), Copilot may pause and ask “Which one did you mean?”. You must reply with your selection to continue the query.
Unexpected Empty Results: If the tool claims it cannot find a client, confirm you are asking about people or organizations. The tool cannot search by “active project” or “contract name”.
7. Support & Privacy
Get Help: For bugs, technical assistance, or integration issues, contact our support team at [email protected].
Privacy Policy: Review our data handling and privacy commitments at https://www.introhive.com/privacy-policy/.