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 fieldxeroMCP100 SelectedShopify Storefront MCPMCP100 Selected
Task fit
Best for
  • Accounting investigation and controlled bookkeeping workflows in Xero.
  • Searching and comparing products from a specific Shopify storefront
  • Answering store policy and FAQ questions
  • Creating and updating a shopper cart before checkout
Not ideal for
  • Teams outside the publisher ecosystem or without least-privilege credentials
  • Merchant administration, inventory editing, or back-office order management
  • Cross-store catalog aggregation without separate store endpoints
Avoid when
  • The connected identity is broader than the task requires
  • Tool calls cannot be reviewed before consequential mutations
  • The agent can finalize purchases without explicit shopper review
  • The selected store restricts MCP access or its policies prohibit the intended use
  • Untrusted product or policy content can trigger unrelated privileged tools
Provenance
Provenance details

First-party MCP

ecosystem:xero · Publisher source ↗

First-party MCP

Shopify · Publisher source ↗

Maintenance
Maintenance details

Repo: Jun 5, 2026

Package: Not documented

Repo: Not documented

Package: Not documented

Popularity evidence
GitHub stars

350

GitHub stars · checked 2026-08-14T18:46:26.000Z

Not documented
External adoption evidence
  • github: repository stars: 350Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Not documented
Client coverage
Client coverage details
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
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
AuthenticationThe official server uses Xero OAuth credentials and organization selection.Shopify documents no authentication requirement for the Storefront MCP endpoint. Some stores may restrict access. UCP catalog requests include an agent-profile reference.
CostThe MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.Shopify documents no separate Storefront MCP fee. Merchant Shopify plan, application hosting, model, and client costs remain applicable.
PermissionsXero organization permissions and OAuth scopes govern accounting data and mutations.The standard endpoint exposes `get_cart`, `update_cart`, and storefront policy/FAQ search. The UCP endpoint exposes catalog search, lookup, and product retrieval. It does not grant Shopify Admin API access.
Data handlingAuthorized 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 finance & payments information.Requests go to the selected merchant's Shopify-hosted endpoint. Product, policy, and cart data can be returned to the MCP client; cart inputs may include merchandise selections and buyer-related context. Treat all storefront text as untrusted content.
Limitations
Tradeoffs
  • Accounting records and invoices are financially consequential and may contain personal or tax information.
  • The standard Storefront endpoint requires no authentication, simplifying access but making store content an untrusted external input.
  • Catalog UCP tools use a separate `/api/ucp/mcp` endpoint and require an agent profile.
  • Cart changes are reversible, but the resulting checkout can have financial and fulfillment consequences.
Risk contextAccounting records and invoices are financially consequential and may contain personal or tax information. 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.Keep the agent limited to catalog, policy, and cart tools; display price, quantity, merchant, shipping, and return details before checkout; and never imply MCP100 execution testing. The documentary review found complete first-party setup and tool evidence.
Evidence date
Editorial review2026-07-302026-07-24
Candidate evidence2026-08-14T18:46:26.000Z2026-07-29T20:58:26.000Z

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

Read the evidence method →
Compare MCPs | MCP100 Index