The GTM MCP Directory
Directory / Vendors / ZoomInfo

ZoomInfo

2 products in the directory 1 official MCP server 1 live handshake Data baked 2026-09-27

Vendor domain: zoominfo.com · vendor page id zoominfo-com

The rollup
Products
2, facts checked by hand 2026-09-02, 2026-09-03
Official MCP servers
1 of 2, as recorded on 2026-09-02, 2026-09-03
Community MCP servers
1 of 2
Live handshake
1 of 2 answered an MCP initialize, 2 probed, 2026-09-04
Repo local
1 of 2: a server you install and run yourself
Docs only
0 of 2: the recorded URL is a page about the server, not the server
Tools catalogued
56 named across 2 measured servers, harvested 2026-09-27
Bench tested
0 of 2 here, 1 of 1,252 across the directory
Ships a CLI
2 of 2 official, 0 community only, 0 none found, harvested 2026-09-27
GitHub organisation
github.com/Zoominfo, tied to the domain with evidence 2026-09-08

A live handshake means the URL answered an MCP initialize as a server on the probe date. It is liveness and nothing more: nobody has run its tools. A tool being catalogued means a server names it, by answering tools/list, in its own source, or in the vendor's documentation. None of them has been called. A tool count of 0 means not measured, never zero tools.

Products, 2

ZoomInfo

A B2B contact/company database and go-to-market platform (500M+ contacts, 100M+ companies) built from web crawling, public filings, and human researchers, used for prospecting, account research, and lead enrichment.

Endpoint probe
answered, asking for a key, 2026-09-04
Connect URL
Tools catalogued
17 named, harvested 2026-09-27, catalogue fixed
last_checked
2026-09-03

Chorus

Records, transcribes, and analyzes sales calls, meetings, and emails, and syncs the resulting insights into the CRM.

Endpoint probe
repo or package: install and run locally, 2026-09-04
Tools catalogued
39 named, harvested 2026-09-27, catalogue fixed
last_checked
2026-09-02
The gates, in plain words

1 of 2 free to start, a solo operator gets API access without talking to anyone. 1 of 2 enterprise only, API access needs a contract.

The gate is the api_gate field on each product entry, established by hand on the last_checked date shown above. It records whether a solo operator can get API access without a contract. Money is not tracked.

Jobs the vendor says its products do

12 distinct job labels, the union across 2 products, tagged 2026-08-25. A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Connect URLs

An endpoint is where an agent connects. A docs page is where a person reads about connecting. Both are published because both are what the probe found; an agent needs the first.

Command line

ZoomInfo gtm official CLI

npm install -g @zoominfo/gtm-ai-cli

quoted from https://gtm.ai/docs/cli on 2026-09-27, via npm

Login or key hint: gtm auth

2 more install commands, 8 subcommands seen, harvested 2026-09-27, all on the tool page.

A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it.

On GitHub

github.com/Zoominfo tied to the vendor by rule 1, account website https://www.zoominfo.com has the vendor's domain, confidence strong

Public repositories
8, forks excluded, as read on 2026-09-08
Mention MCP
1 of them
Look like CLIs
1 of them
Latest push
2026-09-03

The five most recently pushed, on 2026-09-08:

RepositoryKindDescriptionStarsPushedLatest release
zoominfo-mcp-pluginMCP serverZoomInfo MCP plugin72026-09-03
n8n-nodes-zoominfoplugin or integrationn8n community node for the ZoomInfo GTM API02026-09-02v1.0.0
gtm-ai-cliCLIA command-line tool for searching ZoomInfo's go-to-market data12026-08-30v1.1.0
homebrew-gtm-aiinfrastructureHomebrew tap for gtm-ai formulae02026-08-26
api-auth-java-clientSDKZoominfo API's Java Authentication Client22026-06-30

Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.

What this page does not claim

A job tag is a vendor claim: it means the vendor says the product does this, and it is not a test result. A listed tool has not been run: the catalogue says what an agent could try, not what works. 1 of 1,252 directory entries are bench tested, meaning somebody personally ran the tool on a stated date, and 0 of this vendor's 2 products are among them. There is no verdict here on whether this vendor is better than another.

Vendor pages group the directory's canonical product entries by vendor_domain. The vendor name is the product display name that matches the domain when several products share it; nothing on this page is typed by hand. Data baked 2026-09-27 by build_directory.py (phase 1).