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

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

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldGoogle Maps MCPShortlist candidatewixMCP100 Recommended
Task fit
Best for
  • Grounded place search, weather and estimated route calculations
  • Use when an agent needs verified place identifiers and travel context.
  • Website and business operations across the Wix product ecosystem.
Not ideal for
  • Maps Grounding Lite is not a turn-by-turn navigation, live traffic, or routing-guidance replacement.
  • Teams outside the publisher ecosystem or without least-privilege credentials
Avoid when
  • Maps Grounding Lite is not a turn-by-turn navigation, live traffic, or routing-guidance replacement.
  • The connected identity is broader than the task requires
  • Tool calls cannot be reviewed before consequential mutations
Provenance
Provenance details

First-party MCP

Google · Publisher source ↗

First-party MCP

ecosystem:wix · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Not documented

Package: Not documented

Popularity evidence
Client coverage
Client coverage detailsNot documented
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationMaps Grounding Lite requires either a Google Maps Platform API key or OAuth credentials.Wix documents its hosted OAuth endpoint and official local package.
CostMaps Grounding Lite is pay-as-you-go and each request is a billing event. Some related resolution requests are billed at no charge under the cited SKU; quotas also apply.The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.
PermissionsUse is governed by Google Maps Platform Terms of Service. Google states that Maps content must not be cached, stored, or used to improve the LLM, and source attribution requirements apply.Wix account, site, app, and product permissions constrain tools and data.
Data handlingGoogle's Maps Grounding Lite guidance restricts caching/storage/reuse of Google Maps content and requires privacy/attribution compliance. Location/search inputs are sent to Google Maps Platform services to answer the request.Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive retail & e-commerce information.
Limitations
Tradeoffs
  • Explicitly not turn-by-turn navigation or live traffic
  • The cross-product surface includes customer, booking, commerce, and payment data plus consequential write actions.
Risk contextPrimary risks are location/privacy exposure, terms-compliance obligations, and usage charges. It is not a turn-by-turn navigation or live-routing safety system.The cross-product surface includes customer, booking, commerce, and payment data plus consequential write actions. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review.
Evidence date
Editorial review2026-10-192026-07-30
Candidate evidence2026-10-192026-09-24T04:25:05.554391Z

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

Read the evidence method →