Included as a hosted B2B intelligence and GTM-context surface: its MCP can find and enrich companies and contacts, retrieve buyer signals and audiences, synthesize account or contact research, and update structured organizational GTM context under plan, feature, OAuth, and credit constraints.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Companies and contacts; firmographic and full contact records; similar and recommended records; intent signals, scoops, and categorized news; GTM Studio audiences and row previews; user role and organizational GTM context; CRM and conversation inputs used by context agents; bulk-data credits, AI-action credits, record limits, and API quotas.
Search companies and contacts; look up valid filters; enrich up to 25 company or contact records; find similar or recommended records; search or enrich intent and scoops; enrich news; browse and preview audiences; retrieve user and organization GTM context; and generate account or contact research.
`Update GTM Context` creates or updates structured organizational GTM configuration by synthesizing unstructured content and is charged as an AI Action. The current catalog lists audience browse and get tools, but no audience-create, membership-write, CRM-export, record-delete, or contact/company mutation tool.
Connect to `https://mcp.zoominfo.com/mcp` with a Streamable HTTP and OAuth-capable client, then complete browser sign-in with ZoomInfo credentials or organizational SSO. Access requires a GTM.ai self-serve or Enterprise license, and account plan, feature availability, API limits, credits, and allowed actions continue to apply.
Separate free discovery, bulk-data enrichment, and AI-action operations; show the selected credit class and item count before paid work, require review before updating shared GTM context, and disable model training in the connected AI client as ZoomInfo requires.
MCP requires a GTM.ai self-serve or Enterprise license, an OAuth-capable Streamable HTTP client, available plan features and credits, and model training disabled. Company/contact enrichment is limited to 25 records per call; enrichment uses bulk-data credits, research and GTM-context updates use AI-action credits, and plan-specific API limits apply.
First-party access
Agent access
Support: Official MCP server
Read scope: Expose the documented free search, lookup, similarity, recommendation, audience-view, and GTM-context reads separately from bulk-data enrichment and AI-action research. Carry the subject count, filters, entitled fields, audience, context sources, and credit class into the result provenance.
Write scope: The current MCP catalog has one explicit mutation: `Update GTM Context`, which creates or updates structured GTM configuration from unstructured input. Audience tools are browse/get only; broader audience, audience-member, GTM-model, and GTM-config manage scopes in the API catalog do not establish additional MCP tools.
Authentication: OAuth through ZoomInfo’s hosted Streamable HTTP MCP endpoint, with one-time browser authentication using ZoomInfo credentials or organizational SSO. Supported marketplace and plugin routes initiate the same sign-in; custom clients must support OAuth and Streamable HTTP.
Approval boundary: Show the bulk-data credit class and candidate count before enrichment and the AI-action class before account/contact research. For `Update GTM Context`, preview the source content and resulting structured configuration, identify the organization and signed-in user, and require confirmation before commit; free searches still need sensitive-data and audience provenance.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that ZoomInfo ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
ZoomInfo documents a hosted endpoint for B2B company/contact data, enrichment, and API-assisted workflows.
Targeted first-party MCP/agent-role review; broader API inventory retained
First-party API reference or API overview recorded for this platform.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
