AI Assistant Integration (MCP)
Qubi plugs into AI assistants such as Claude and ChatGPT through the Model Context Protocol (MCP). Your assistant gets direct access to the same sales intelligence Ask Qubi uses: past meetings and transcripts, CRM deals, contacts, competitors, coaching, and your Knowledge Base.
Ask a question in plain language and your assistant works out which Qubi data to pull. Think of it as Ask Qubi, available wherever you already work with AI.
MCP access is read-only. Your assistant can read Qubi data. It cannot change anything in Qubi, your CRM, or your calendar.
What you can do
| Capability | Example question |
|---|---|
| Ask about meetings | "What objections came up in calls with Acme last month?" |
| Search deals | "What's the status of the TechCorp renewal?" |
| Count deals and pipeline | "How many deals did we close last quarter?" |
| Research people | "Who is the decision-maker at Globex?" |
| Prepare for a call | "What should I know before my 2pm with Initech?" |
| Review recent calls | "Summarize my meetings from last week" |
| Compare against competitors | "How do we stack up against CompetitorX?" |
| Search internal docs | "What's our onboarding process for enterprise customers?" |
| Check your todos | "What follow-ups are still open?" |
Before you start
- You need a Qubi account with data in it — recorded meetings, a connected CRM, Knowledge Base content, or a mix. Your assistant can only answer from what Qubi holds.
- Your Qubi user must be provisioned in your organization. If it is not, the connection succeeds but every question fails. See Not provisioned in Qubi.
- Your AI assistant must support remote MCP servers with OAuth. Claude and ChatGPT both do.
Connect your AI assistant
Qubi runs a hosted MCP server:
https://mcp.getqubi.com/mcp
There is nothing to install and no API key to copy. Your assistant discovers the server's OAuth metadata, registers itself, and sends you to a browser to sign in with your Qubi account. It then keeps the connection alive on its own, so you sign in once.
Claude Desktop
- Open Claude Desktop
- Go to Settings → MCP Servers (labelled Connectors in newer builds) → Add
- Name it
Qubiand enter the server URL:https://mcp.getqubi.com/mcp - Claude opens a browser window — sign in with your Qubi account
- Finish the browser flow, then restart Claude Desktop
- Click the tools icon in the chat input and confirm the Qubi tools are listed
Claude on the web
- Open Settings → Connectors → Add custom connector
- Name it
Qubiand enterhttps://mcp.getqubi.com/mcp - Click Connect and sign in with your Qubi account
ChatGPT
ChatGPT connects to remote MCP servers as a custom connector, and needs a paid plan (Plus, Pro, Business, Enterprise, or Edu).
- In the ChatGPT web app, open Settings → Connectors (or Apps) → Advanced settings and turn on Developer mode
- Create a custom connector and enter the Qubi server URL:
https://mcp.getqubi.com/mcp - Choose OAuth as the authentication method. ChatGPT discovers the remaining settings automatically
- Sign in with your Qubi account when prompted
On Business and Enterprise plans, an administrator may need to allow custom connectors and developer mode before you can add one.
Other MCP clients
Any assistant that supports remote MCP with OAuth can connect:
- Point it at
https://mcp.getqubi.com/mcp - Complete the OAuth sign-in when the client opens your browser
- Confirm the Qubi tools are listed
The protocol is young and client support moves quickly. If your assistant only supports local (stdio) MCP servers, it cannot connect to Qubi's hosted server.
Verify the connection
Once connected, you should see 21 Qubi tools listed — the same tools Ask Qubi uses. They are all listed in the tool reference below.
If they are missing, see Tools don't appear.
Tool reference
You rarely need to name a tool. Ask the question you care about and your assistant picks the right one. This reference is here for when you want to know what is available, or what a tool will not return.
Meetings and transcripts
| Tool | What it returns | Useful inputs |
|---|---|---|
search_summaries | Summaries of past meetings, filtered by date, topic, or deal | limit 1–20 (default 10), start_date, end_date, semantic_query, opportunity_id |
load_transcript | The full transcript of one meeting | transcript_id |
extract_from_transcripts_with_instructions | Answers pulled out of several transcripts at once — objections, pricing talk, next steps, competitors named | extraction_instructions, limit 1–20 (default 5), date and participant filters |
Deals and pipeline
| Tool | What it returns | Useful inputs |
|---|---|---|
search_opportunities | Deals by name or account, or a page of your whole book | query, limit, owner_email |
get_crm_opportunity_analytics | Counts: deals created in a date window, the won/lost/open split, close rate, and results per rep | start_date, end_date |
get_crm_deal_velocity | How long deals take to close — won and lost, per rep — and the days deals spend in each stage | start_date, end_date, owner_email |
get_crm_forecast_accuracy | A forecast graded: the deals expected to close in a period, read on a date, against what actually closed | period_start, period_end, as_of, owner_email |
Deal search returns a page of deals, not a total, so it cannot answer "how many". For any counting question your assistant uses get_crm_opportunity_analytics instead. Questions about timing — sales cycle length, time in each stage, how accurate a forecast was — use get_crm_deal_velocity and get_crm_forecast_accuracy.
People
| Tool | What it returns | Useful inputs |
|---|---|---|
search_participants | Contacts and meeting participants | query for names, roles, and companies; semantic_query for descriptions such as "who cares about security?" |
get_contact_email_history | Recent email engagement with one contact | email, limit 1–25 (default 10) |
Meeting preparation
| Tool | What it returns | Useful inputs |
|---|---|---|
get_upcoming_prep_notes | Prep briefs for your upcoming meetings | none |
get_prep_note_for_event | The prep note for one calendar event | event_id |
Competitors
| Tool | What it returns | Useful inputs |
|---|---|---|
list_competitors | Every competitor your team tracks | none |
get_competitor_intel | Detail on one competitor | competitor_id |
get_all_competitor_intel | Competitive intelligence for all tracked competitors | none |
Knowledge Base
| Tool | What it returns | Useful inputs |
|---|---|---|
search_knowledge_base | Passages from your documents, playbooks, and battlecards, plus Q&A pairs already verified against their source | query, top_k (default 10) |
multi_query_search | Results for several queries at once, deduplicated | queries, top_k_per_query (default 5) |
get_document_outline | A document's sections and headings, so the assistant can navigate a long document | document_id |
read_document_segment | One slice of a document, with surrounding context | document_id, start_chunk, end_chunk |
Analytics, coaching, and todos
| Tool | What it returns | Useful inputs |
|---|---|---|
get_meeting_analytics | Aggregated meeting analytics — distributions, trends, correlations | start_date, end_date, dimension_type, filter_user_id |
get_taxonomy_dimensions | Your company's meeting categories | dimension_type |
get_meeting_classifications | The taxonomy tags on one meeting | meeting_id |
get_coaching_profile | Strengths, growth areas, and metrics | email — omit it for your own profile |
get_user_todos | Your todo list | status_filter (default OPEN), account_query, category, sort_by, order, limit |
What MCP cannot do
- Change anything. Every Qubi tool is read-only. Your assistant cannot create todos, edit deals, or write to your CRM or calendar.
- Read a call that is happening right now. Live-call tools are not exposed over MCP. A meeting becomes available once it has been recorded and processed.
- See past your permissions. Results are limited to your own Qubi account, and Knowledge Base results to the spaces you can open in Qubi.
- Answer from data Qubi does not have. If a meeting was never recorded, or a CRM is not connected, there is nothing to return.
Example conversations
Preparing for a call
You: I have a call with Sarah Chen from Acme Corp in 30 minutes. What should I know?
Claude: (uses get_upcoming_prep_notes, search_summaries, extract_from_transcripts_with_instructions) From your last three meetings with Acme: the open question is security review timing, and they asked twice about SSO...
Checking deal status
You: What's happening with the Globex enterprise deal?
Claude: (uses search_opportunities) The Globex Enterprise deal is in Negotiation, valued at $85,000 with a 70% win probability. Expected close: March 15...
Counting pipeline
You: How many deals did we close last quarter, and who closed them?
Claude: (uses get_crm_opportunity_analytics) 18 deals were created in Q3, of which 7 are won and 3 lost today. Close rate 70%. By rep: Sarah 4 won, Marcus 2, Priya 1...
Finding competitor intel
You: What do we know about how we compare to CompetitorX?
Claude: (uses search_knowledge_base, get_competitor_intel) From your CompetitorX battlecard: your key differentiators are native CRM sync and per-seat pricing...
Privacy and security
- The MCP integration uses the same authentication and permissions as your Qubi web account. Your assistant can only read what you can read.
- All access is read-only.
- Authentication is OAuth 2.0 with PKCE. Your assistant stores a token and refreshes it in the background — Qubi never receives or stores your password.
- Qubi sends the data your assistant asks for into that assistant's own context. Once it is there, the assistant vendor's retention and training policies apply to it. Use an assistant whose data terms you are comfortable with.
Troubleshooting
Tools don't appear
- Check the server URL is exactly
https://mcp.getqubi.com/mcp - Quit and reopen your AI assistant completely
- Remove the Qubi connector and add it again
- In Claude Desktop, click the tools icon in the chat input — if the list is empty, the connection did not complete
Sign-in fails, or the connection stops working
- Finish the whole browser flow; a closed tab leaves the connection half-made
- Remove the connector and add it again to start a fresh sign-in
- Sign in with the same email you use for Qubi
Not provisioned in Qubi
If every question fails with a message about your user not being provisioned, your Qubi account exists in your identity provider but not in your organization's Qubi workspace. Ask your Qubi administrator to add you, then reconnect.
Empty or incomplete answers
- Confirm the data exists in Qubi first — open the meeting or deal in Qubi and check
- For questions about documents, confirm you have access to the relevant Knowledge Base space
- Ask for a wider date range, or name the company or person explicitly
A question about "how many" gets a list instead of a number
Deal and meeting search return a page of results, not totals. Ask for a count explicitly — "how many deals..." — so your assistant reaches for the analytics tool, or give it a count to make.
Related
- What Is Ask Qubi? — the same intelligence, inside Qubi
- Ask About Deals & Customers — question patterns that work well
- Build Your Knowledge Base — what the knowledge tools can reach
- Track Competitors — where competitor intelligence comes from
Need more help? Contact Qubi support.