Clients

Setup guides for connecting ZoomInfo MCP to Claude, Claude Code, Claude Cowork, ChatGPT, Codex, Cursor, Microsoft Copilot, Amazon Quick, Gemini Enterprise, Gemini Spark, Perplexity, Slack, and custom-built AI tools.

Last updated September 25, 2026·

Rowan BaileySenior Director, Product

Supported Clients

ZoomInfo MCP works with any AI tool that supports the Model Context Protocol. The architecture is client-agnostic: the same server URL and authentication flow applies regardless of which client you use.

Claude→

Listed in the Claude connector marketplace. Easiest setup.

Claude Code→

Install the plugin for the hosted server plus our GTM skills in one command.

Claude Cowork→

Bring ZoomInfo into Anthropic's knowledge-work agent with the same plugin.

ChatGPT→

Listed in the ChatGPT app marketplace. Works on all tiers, including free plans.

Codex→

Install the ZoomInfo plugin, or add it as a Custom MCP entry.

Cursor→

Connect through the mcp-remote bridge and sign in over OAuth.

Microsoft Copilot→

Listed in the Copilot Studio marketplace. Add as a tool to any agent.

Amazon Quick→

Native ZoomInfo connector. Connect with the Default OAuth app and publish to your org.

Gemini Enterprise→

Native connector. Create a ZoomInfo data store with Google-managed OAuth, then link it to an app.

Gemini Spark→

Add as a custom connected app in the Gemini web app, then call ZoomInfo from Spark tasks.

Perplexity→

Native connector for paid Perplexity plans with Computer access.

Slack→

Install the ZoomInfo app, then call ZoomInfo tools from Slack AI.

Custom Connector→

Add ZoomInfo to any app that supports a custom MCP server.

MCP Server URL

All clients use the same endpoint:

text

https://mcp.zoominfo.com/mcp

Other Clients

Gemini CLI

Gemini CLI supports custom MCP servers. Add https://mcp.zoominfo.com/mcp to your ~/.gemini/settings.json and sign in with OAuth. Gemini CLI does not auto-discover MCP OAuth, so this path needs explicit client credentials. For Gemini Enterprise, use the native connector instead; for the consumer Gemini app, connect through Gemini Spark.

Any other MCP client

Tools that only offer a generic "add a custom MCP server" form connect the same way: point them at https://mcp.zoominfo.com/mcp over Streamable HTTP and sign in with OAuth. See Add ZoomInfo as a Custom Connector for the field-by-field defaults.

Next: run your first session. Paste this into your client once it's connected. You get your first account briefing, built from your saved GTM context and any customer sources your organization has connected. It asks before spending 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.

Try in Claude

New to ZoomInfo?

PreviousQuickstart Next Claude