ZoomInfo

What ZoomInfo MCP server does

The ZoomInfo MCP server gives compatible LLM clients access to ZoomInfo’s go-to-market intelligence through a hosted MCP endpoint. It supports research and workflow tasks involving companies, contacts, accounts, leads, buying committees, competitors, markets, buyer intent, and technology stacks.

The repository packages the server registration with client-specific plugin metadata and task-oriented skills. These skills guide agents toward structured outputs such as briefs, tables, scores, emails, account lists, contact lists, and market-sizing results rather than leaving every request as unstructured tool output.

Typical requests include finding companies that match firmographic and technology criteria, enriching an existing account or contact, identifying decision-makers, preparing for a sales meeting, prioritizing inbound leads, and personalizing outreach. The available workflows also cover lookalike searches, competitor analysis, account scoring, lead scoring, TAM sizing, and technology-stack summaries.

How it works

The repository registers ZoomInfo’s hosted MCP service at https://mcp.zoominfo.com/mcp. Clients connect to that endpoint over HTTP and complete authentication through ZoomInfo OAuth. The repository does not store API keys or provide a separate local data service.

A shared .mcp.json file contains the server registration. Additional metadata files support Codex/OpenAI, Claude, and Cursor plugin workflows. Clients that support the repository’s skills can invoke a skill by name, such as /account-research, or select one from a natural-language request.

Because the data comes from ZoomInfo, the account used to authenticate must have the required API access and product entitlements. The MCP client or agent environment must also support MCP and, where applicable, local plugin manifests or skills.

Setup and configuration

Start by cloning the repository if you want to use its local manifests or skills:

git clone https://github.com/Zoominfo/zoominfo-mcp-plugin.git

Then register the server according to the client’s MCP or plugin process. The shared registration uses the HTTP server URL and does not define an API-key environment variable. OAuth is completed by the client through the user’s ZoomInfo account.

For local development, point the client at the repository root or at the manifest path required by that client. The repository includes .mcp.json, Codex plugin metadata, Claude plugin and marketplace metadata, Cursor plugin and marketplace metadata, and a skills/ directory.

Tools and capabilities

The ZoomInfo MCP server supports these task areas:

• Find companies, contacts, buying-committee members, similar companies, similar contacts, and recommended contacts.
• Enrich company, account, lead, and contact records with business information.
• Build account or contact lists from natural-language criteria.
• Research accounts, competitors, markets, buyer intent, news, and technology stacks.
• Prepare meeting briefs and personalize outreach using account, contact, intent, and trigger context.
• Score accounts and leads using fit, intent, trigger signals, urgency, and available contact information.
• Size a market or territory and produce reusable ICP filter sets.

Available skills include account-research, build-list, buying-committee, competitor-analysis, enrich-company, enrich-contact, find-similar, meeting-prep, personalize-email, recommend-contacts, score-accounts, score-leads, tam-sizer, and tech-stack-snapshot.

Limitations and notes

Access depends on the authenticated ZoomInfo account’s permissions, API access, and product entitlements. The repository itself does not describe a local fallback or an offline dataset; it points clients to the hosted service. Client support also depends on whether the chosen environment can use MCP, plugin manifests, and the included skills. The repository is licensed under MIT.