MCP Hub Refresh
Hyperleap ships a first-party, read-only MCP server so you can query your leads, conversations, and pipeline from Claude Desktop, Cursor, or ChatGPT in plain English.
Hyperleap MCP Server: Query Your Leads and Conversations from Claude, Cursor, or ChatGPT
Hyperleap ships a first-party MCP server that turns your customer conversations, leads, and chatbot analytics into a tool-accessible business data layer — one that AI assistants like Claude Desktop, Cursor, and ChatGPT can query directly through the Model Context Protocol (MCP). In plain terms: your leads, inside Claude, right now.
MCP is an open protocol stewarded by Anthropic for connecting AI assistants to external tools and data. Hyperleap doesn't own or define MCP — it ships a first-party MCP server that exposes your Hyperleap data through it. This page covers both the plain-English "what can I do with this" view for business owners and the technical reference for the people wiring it up.
The plain-English version
Most chatbot platforms trap your leads behind a dashboard. You log in, click around, and export a CSV when you need to do real analysis. Hyperleap's MCP server lets you skip the dashboard entirely and just ask. Once connected, you can open Claude Desktop (or Cursor, or ChatGPT) and type questions like:
- "Which leads from this week haven't had a follow-up yet?"
- "Give me a summary of where my pipeline stands."
- "What did the Acme Corp lead ask about in their last chat?"
- "Which leads are the most engaged right now?"
The AI assistant pulls the answer from your live Hyperleap data and responds in natural language. No SQL, no exports, no switching tabs. It's the fastest way to run a sales standup, triage your pipeline, or coach a rep using real conversation transcripts.
What the MCP server exposes
Access is read-only and scoped per workspace — the MCP server can read your leads, conversations, and pipeline, but it cannot write to or update your CRM. Nine tools are available today:
| Tool | What you can ask |
|---|---|
list_leads | "Which leads from this week haven't had a follow-up yet?" |
get_lead_details | "What's the contact info for the Acme Corp lead?" |
get_lead_conversations | "What did this lead ask about in their last chat?" |
get_lead_activities | "Show me the full activity timeline for this lead." |
get_lead_notes | "What notes has my team added to this lead?" |
extract_lead_insights | "Which leads are the most engaged right now?" |
get_crm_dashboard | "Give me a summary of where my pipeline stands." |
get_pipeline_stages | "What are my current pipeline stages?" |
get_conversation | "Show me the full chat transcript for a conversation." |
Why this matters
An AI chatbot for business captures leads and conversations around the clock. The MCP server is what makes that data useful at the speed of thought — you query it from the same AI tools your team already lives in, instead of context-switching into yet another dashboard. It's the difference between "we have the data somewhere" and "I can ask a question and get the answer now."
For teams building agentic workflows, the read-only data layer also composes with other MCP servers — for example, reading Hyperleap leads alongside your project tracker or knowledge base inside a single assistant. See MCP for conversation QA for how to spot knowledge gaps from your transcripts.
Technical reference
Connecting a client
The MCP server works with any MCP-compatible client — Claude Desktop, Cursor, ChatGPT, or a custom agent. Setup typically takes under five minutes:
- Generate your MCP key from studio.hyperleapai.com.
- Add the Hyperleap MCP server to your client's configuration with the key.
- Restart the client; the nine tools appear and are ready to query.
How it relates to the REST API and webhooks
The MCP server, REST API, and webhooks serve different jobs. Webhooks push events to you in real time (lead.captured, conversation.started, and similar). The REST API gives programmatic read/write access for custom integrations. The MCP server gives AI assistants read-only, conversational access to the same lead and conversation data. Use webhooks for automation, the REST API for building, and MCP for asking questions.
Scope and safety
MCP access is read-only and scoped to your workspace. The server cannot modify leads, send messages, or change pipeline state — it surfaces what's already there. That keeps the data layer safe to expose to an assistant without risking accidental writes.
Availability and pricing
The MCP server sits on top of your Hyperleap plan — it is part of the platform, not gated behind a separate tier. To use it you need an active plan; see pricing for current plans (Plus, Pro, Max), response limits, and add-on eligibility, and the features overview for the full product picture.
Frequently asked questions
What is MCP?
The Model Context Protocol is an open, Anthropic-stewarded standard for connecting AI assistants to external tools and data. Hyperleap ships a first-party MCP server that exposes your lead and conversation data through it.
Which AI clients can connect?
Any MCP-compatible client, including Claude Desktop, Cursor, and ChatGPT, plus custom agents.
Can the MCP server change my data?
No. Access is read-only and scoped per workspace. It can read leads, conversations, activities, notes, and pipeline state, but cannot write to or update your CRM.
How long does setup take?
Generally under five minutes: generate a key, add the server to your client config, and restart.
Do I need a developer to use it?
No. Business users connect a client and ask questions in plain English. Developers who want deeper integration can also use the REST API and webhooks.
Get started
Stop logging into a dashboard to understand your pipeline. Connect Hyperleap to the AI tools your team already uses and just ask.
Generate your MCP key and start your free trial or review plans and pricing first.