Skip to main content

Introhive MCP Server Configuration & Support Guide

This article describes how to configure, support and troubleshoot the MCP Server.

Introhive MCP Server Configuration & Support Guide

Purpose-built for professional services firms, the Introhive Model Context Protocol (MCP) Server provides AI assistants like Claude with real-time access to your firm's collective relationship network

By connecting Claude 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 Claude, 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.

  • 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 your AI client.

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 your AI platform may not provide the Redirect URI until the configuration is saved, you will use a placeholder first.

  1. Navigate to your Introhive instance: https://[instance].introhive.com/profiles/oauth_applications.

  2. Click Create OAuth Application.

  3. Enter an Application Name (e.g., "Claude MCP").

  4. For Redirect URI, enter a placeholder like https://introhive.com.

  5. Under Scopes, check AI Agents JWT (Note: This cannot be combined with other scopes).

  6. Click Create and securely save your generated Client ID and Client Secret, as they cannot be retrieved again.

Step 2: Configure the Server in your AI Client Input the following parameters into your AI platform's MCP or external tool configuration settings to establish the bridge layer:

  • Server Name: Introhive MCP

  • Server URL: https://[instance].introhive.com/pollen/mcp

  • Authentication Type: OAuth 2.0

  • Client ID: (Your generated ID from Step 1)

  • Client Secret: (Your generated Secret from Step 1)

  • Authorization URL: https://[instance].introhive.com/oauth/authorize

  • Token / Refresh URL: https://[instance].introhive.com/oauth/token

  • Scopes: pollenchain_jwt

Step 3: Update the Redirect URI (Crucial) Once your AI client generates its designated Redirect URI, you must go back to Introhive to update the placeholder.

  1. Return to https://[instance].introhive.com/profiles/oauth_applications.

  2. Edit your "Claude MCP" application and replace https://introhive.com with the exact Redirect URI provided by your AI client.

  3. 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 Claude 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. Claude will automatically discover how to use the tool and handle data queries, summaries, and recommendations.

Try asking Claude:

  • 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]?"


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: Claude 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 URI in your AI tool's settings 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"), Claude 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

Did this answer your question?