GTM AI
GTM AIby ZoomInfo
Sign up

Quickstart

Connect ZoomInfo to your AI app over MCP: what you need, which client to pick, and how to run your first account briefing.

·Rowan BaileyRowan BaileySenior Director, Product

Choose Your Access Path

New builders can start free with 1,000 data credits and 1,000 AI credits, issued once at signup. No credit card is required, and those credits work with MCP. See pricing for usage and top-ups.

Existing ZoomInfo customers sign in with their current login and draw on their organization's credits. Any package qualifies: Sales, Copilot, Studio, or ZI Lite. Not sure how many credits you have? Your ZoomInfo admin can check in the Admin Portal.

📝

Building your own app?

If you signed up through gtm.ai, register your app in the API/MCP tab of the ZoomInfo app. Existing customers use the Developer Portal, which needs a DevPortal subscription assigned by your ZoomInfo admin. See How to Build a Custom App. For terminal access, use the GTM CLI.

Requirements

  • Your own ZoomInfo login. Results reflect your account access and customer relationships. Admin-only seats, which have no data access, can't use MCP.
  • Credits. Enrichment uses data credits and research uses AI credits. Some older subscriptions carry recurring monthly credits, which MCP can't draw from; see Which credits MCP uses.
  • An MCP-compatible client. ZoomInfo doesn't require any particular AI subscription tier.
  • Connected customer sources (optional). To include CRM and conversation history, your organization connects those sources and grants you access. Follow Connect Customer Context.

MCP Server URL

All clients connect to the same endpoint:

text
https://mcp.zoominfo.com/mcp

Choose a Client

Each client has a step-by-step setup page.

AI assistants

  • Claude: listed in the Claude connector marketplace.
  • ChatGPT: listed in the ChatGPT app marketplace.
  • Claude Cowork: Anthropic's agent for knowledge work, installed as the ZoomInfo plugin.
  • Perplexity: native connector for paid plans with Computer access.
  • Gemini Spark: custom connected app for Google's personal agent in the Gemini apps.
  • Slack: install the ZoomInfo app, then turn on ZoomInfo MCP in Slack AI.

Coding agents

  • Claude Code: installed as a plugin (skills and MCP) or with claude mcp add.
  • Codex: installed as a plugin or as a custom MCP server.
  • Cursor: connects through the mcp-remote bridge, which handles the browser sign-in.

Enterprise platforms

Anything else

Verify Your Connection

Once connected, start a new session and ask:

"What ZoomInfo tools do you have access to?"

The model lists the tools described in the Tools reference. If none appear, disconnect and reconnect ZoomInfo in the client's connector settings, then check that individual tools aren't switched off there.

Get Your First Account Briefing

Paste this into your connected AI client. It asks which company to brief, then combines available CRM history, customer conversations, and external signals into a briefing with a recommended next action, dated evidence, and any source gaps. 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?

Authentication Model

Sign in with your own ZoomInfo credentials. Account Research uses the accounts, CRM relationships, and conversation history available to the signed-in user.

A shared login loses that personalization. Each colleague should sign in separately so results reflect their own customer access and relationships.

What's Next

PreviousZoomInfo MCPNext Clients