ZoomInfo MCP
GTM in your AI assistant
Connect it once and your assistant can look up any company or person in ZoomInfo, with your CRM and call notes alongside.
Brief me on Uber before my call tomorrow: recent news, who’s hiring, and who in finance I should talk to.
✓ account_research · ZoomInfo
✓ search_contacts · finance, VP and above
Uber, ahead of tomorrow
- Freight is hiring 40+ platform engineers this quarter. ZoomInfo
- A new CFO started in September and is reviewing tooling spend. News
- Your last call stalled on security review. Calls
Talk to: VP Finance Operations, verified email and direct dial.
Every client
One server for every assistant
Claude, ChatGPT, Copilot, Slack, Cursor, Claude Code, Gemini and Perplexity all connect to the same server, as does any app that supports a custom MCP server. New tools show up the next time you open a chat.
See every clientYour context
Answers that include your CRM and calls
Ask about an account and the answer puts ZoomInfo’s company, contact and signal data next to your CRM and what was said on your calls. Each line shows where it came from.
How Account Research works- Stage: technical evaluation, $480KCRM
- Security asked for SSO before the pilotCalls
- CISO joined from Stripe in AugustZoomInfo
- Researching identity managementIntent
Next step: bring the CISO into Tuesday’s review and lead with SSO.
The platform
Built on the ZoomInfo platform
ZoomInfo MCP connects to the same data, agents and saved GTM context as every other ZoomInfo interface.
“Who should I call at Uber this week, and why?”
✓ account_research
✓ find_recommended_contacts
✓ get_gtm_context
Companies
1 parent · 14 subsidiaries
People
212 in buying roles
Signals
9 this quarter
Uber Freight is expanding its carrier platform and its new CFO is reviewing tooling spend. Lead with consolidation.ZoomInfoCRMCalls
The context graph
100M+ companies and 500M+ contacts, matched to the records in your CRM, calls, email and calendar, so every account resolves to a single record.
Explore the graphContext Agents
Account Research, Contact Research and Conversation Intelligence do the research on ZoomInfo’s side and return the answer with its sources.
Meet the agentsYour GTM context
Save your ICPs, personas, offerings and competitors once and every agent uses them. The marketplace adds ready-made skills, workflows and audiences.
Browse the marketplace
On GTM Bench, Claude with ZoomInfo used 24× fewer tokens than Claude with web search. Read GTM Bench
Get started
Connected in a few minutes
From signup to your first account briefing. Each client’s setup page has the details.
01
Get an account
Sign up and get 1,000 data credits and 1,000 AI credits. No credit card. ZoomInfo customers use their existing login.
02
Connect your assistant
Choose your client below. You sign in with your own ZoomInfo login, so results match what you can see in ZoomInfo.
Add ZoomInfo from the Claude connector directory, then sign in with your ZoomInfo login.
03
Run your first briefing
Ask “What ZoomInfo tools do you have access to?” to check the connection, then paste the prompt below.
- Asks which account to brief
- Combines CRM, calls and ZoomInfo signals
- Asks before it spends credits
First GTM session
(Use the ZoomInfo MCP tools if available; otherwise use the GTM CLI. Use the tool schema or CLI help for supported commands.) I just connected ZoomInfo. Help me complete the job below. 1. Read my saved business context with get_gtm_context, or the CLI equivalent. This read is free. Use the returned offerings, ICP, and role to frame the work. If context is missing, continue with the information we have. Save changes only if I explicitly ask; a first briefing does not require updating shared business context. 2. Prepare a connected account briefing. Ask me only which company or domain to brief if I haven't named one. Use the account and decision already in this conversation when available. Connect the account's available CRM history, including stage and status, with recent customer conversations and external buying signals. Use Account Research, and add Browse Engagements, Conversation Intelligence, or company signals when the briefing needs more evidence. Return a short briefing: where things stand, what changed, what remains unresolved, and one recommended next action. Cite the source and date for each material fact when returned. Distinguish the recommendation from the evidence. 3. Before calling a tool, check its schema or documented inputs rather than guessing at parameters. Ask only for missing inputs, in a single message, then name the tools and give a credit estimate if supported by their documentation. Label it as an estimate: actual charges depend on records and work done. Ask for approval once before paid research, then complete the selected job. If a tool call comes back "No approval received" or a similar permission response, say so plainly, name the tool, and continue with the remaining steps. Don't retry the same call hoping for a different result, and don't invent an approval that didn't happen. Include a source-coverage note of no more than 3 lines. Separate an unavailable or unauthorized source from a successful search with no matching records. If connection status is unknown, say so. Never infer "no customer history" from an empty result. Continue with available evidence and identify what is missing; use https://gtm.ai/guides/connect-customer-context for source setup. Recommend CRM changes as drafts. Applying them requires an available, separately connected CRM workflow and my authorization. Do not claim a CRM update was made by ZoomInfo research tools.
New to ZoomInfo?
Sample answers. Seller-side records (CRM, calls) are illustrative.