Claude Code
How to connect ZoomInfo MCP to Claude Code: install the ZoomInfo plugin for the hosted server plus our GTM skills, then authenticate over OAuth.
Rowan BaileySenior Director, ProductOverview
Claude Code is Anthropic's CLI coding agent. ZoomInfo ships as a plugin in Anthropic's official marketplace, so one command gives Claude Code the hosted ZoomInfo MCP server and our GTM skills together. Authentication is OAuth, with no developer app to register and no client secret to paste; the sign-in happens in your browser.
Setup
Install the plugin
From your terminal, run:
claude plugin install zoominfo@claude-plugins-officialThe plugin lives in Anthropic's official marketplace, which Claude Code already knows about, so there's no marketplace to add first.
Connect and sign in
Inside a Claude Code session, run /mcp, pick zoominfo, and choose Authenticate. Claude Code opens your browser to the ZoomInfo login.
Authenticate
Sign in with your normal credentials or SSO. When the browser hands you back, the zoominfo server shows as connected and every tool and skill is live.
Verify the connection
Ask a question that needs ZoomInfo data, like "How many employees does Snowflake have?" You'll see the tool invocation and arguments inline.
Next - run your first session. With the plugin (or the raw MCP) in place, paste this into a new Claude Code session. It orients from your GTM context and only runs after you approve:
(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. If the **Account Research** skill is available, use it for the briefing. Otherwise, use the available ZoomInfo tools described above. 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?
What the Plugin Adds
The plugin bundles the hosted MCP server at https://mcp.zoominfo.com/mcp plus a set of skills, prewritten workflows that chain the underlying tools into finished output: account briefs, target lists, buying-committee maps, lead scores, meeting prep, and more. To run one explicitly, type its slash command, like /build-list or /account-research. Otherwise describe the outcome and Claude Code picks the skill that fits.
For the full skill list and a deeper walkthrough, see the Claude Code setup guide.
Add the MCP Server by Hand
If you only want the raw tools without the skills, register the server directly:
claude mcp add --transport http zoominfo https://mcp.zoominfo.com/mcpThen run /mcp, pick zoominfo, and authenticate the same way. --transport http selects HTTP transport, since ZoomInfo's server does not use stdio.
Troubleshooting
claude plugin install can't find the plugin: update Claude Code to a recent version. Older builds predate plugin support and the official marketplace.
/mcp lists zoominfo but it won't authenticate: re-run /mcp, select the server, and trigger Authenticate again. If the browser never opened, check that nothing is blocking your default browser from launching.
Claude Code doesn't see any ZoomInfo tools: run /mcp and confirm zoominfo shows as connected. If it's listed with an auth error, re-run the slash command to re-trigger OAuth.
The connection stops working after a few hours: your ZoomInfo session may have expired. Run /mcp to refresh tokens.
Credit errors on enrichment or research calls: MCP requires bulk data credits. Confirm with your ZoomInfo admin that your account has bulk credits enabled, not recurring monthly credits.
What's Next
For the full walkthrough including every GTM skill, see How to Connect ZoomInfo to Claude Code. For the same setup in OpenAI's coding agent, see Codex. For the full tool reference, see the MCP Tools documentation.