Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

ZoomInfo MCPGoogle Search Console MCP Server for SEOs

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Comparable alternatives

Playwright MCPMCP100 RecommendedtableauMCP100 RecommendedHugging Face MCPMCP100 RecommendedFramelink MCP for FigmaMCP100 RecommendedAsana MCPMCP100 RecommendedSalesforce Hosted MCPMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	ZoomInfo MCPShortlist candidate	Google Search Console MCP Server for SEOsMCP100 Recommended
Task fit
Best for	B2B company/contact lookup and account intelligence Use for authorized B2B sales and account research.	SEO analysis across Search Console properties, queries, pages, indexing status, and sitemaps
Not ideal for	Contact and enrichment records may be licensed or sensitive and subject to ZoomInfo terms.	General web analytics or SEO work that does not use Google Search Console data
Avoid when	Contact and enrichment records may be licensed or sensitive and subject to ZoomInfo terms.	You cannot grant the configured OAuth user or service account access to the relevant Search Console property
Provenance
Provenance details	First-party MCP ZoomInfo · Publisher source ↗	Community implementation github:aminforou · Publisher source ↗
Maintenance
Maintenance details	Repo: Not documented Package: Not documented	Repo: Sep 15, 2026 Package: Not documented
Popularity evidence
GitHub stars	Not documented	1,712 GitHub stars · checked 2026-09-24T04:14:16.248000Z
Shared repository stars	9 Shared repository stars (not MCP-specific) · checked 2026-10-20	Not documented
Client coverage
Client coverage details	Not documented	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	ZoomInfo's hosted MCP uses OAuth through the user's ZoomInfo account; no API keys are stored in the public plugin repository.	Uses Google OAuth client-secrets JSON and browser login, or a Google service-account JSON whose email has access to the Search Console property.
Cost	A ZoomInfo account with appropriate API access and product entitlements is required. The reviewed public MCP material does not state a separate MCP price.	The MIT-licensed server lists no MCP fee. Google Cloud or Search Console quota and billing implications are not documented.
Permissions	Use requires a ZoomInfo account with the appropriate API access and product entitlements. The MCP acts within the access provided by that account.	Lists Google Search Console properties and reads analytics, URL inspection, and sitemap data. Site and sitemap add/delete tools are disabled unless GSC_ALLOW_DESTRUCTIVE=true.
Data handling	Not documented in the reviewed sources. The reviewed MCP repository does not provide an MCP-specific retention/training statement. It exposes ZoomInfo company/contact/intent and related go-to-market data to the authenticated client.	Search Console properties, queries, pages, crawl and indexing results, and sitemap data are returned to the connected client. OAuth tokens are saved for reuse; service-account JSON is read from a configured path. Further retention is not documented.
Limitations
Tradeoffs	MCP hosted tool inventory needs account verification; prefer client-native OAuth	It reduces manual reporting work, but the assistant can see sensitive search-performance data and optional destructive site or sitemap operations require an explicit flag.
Risk context	The principal risk is disclosure or misuse of licensed business/contact data and intent/enrichment information. Account entitlements and contractual restrictions remain relevant.	Can expose private Search Console data and, when explicitly enabled, modify sites or sitemaps. Protect credential files, leave destructive tools disabled unless required, and restrict remote SSE deployments.
Evidence date
Editorial review	2026-10-19	2026-08-11
Candidate evidence	2026-10-19	2026-09-24T04:25:05.554391Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →