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 fieldStripe MCPMCP100 SelectedShopify Storefront MCPMCP100 Selected
Task fit
Best for
  • Searching Stripe documentation and support knowledge from an MCP client
  • Inspecting Stripe account, balance, customer, product, and payment data
  • Creating supported Stripe resources in a test account with human confirmation
  • 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
  • Unattended production payment administration
  • Workflows that require Stripe API operations not exposed by the current tool set
  • Merchant administration, inventory editing, or back-office order management
  • Cross-store catalog aggregation without separate store endpoints
Avoid when
  • The client cannot protect Stripe authorization tokens or secret keys
  • You cannot require confirmation for write-capable payment tools
  • Untrusted content can influence the same agent session without tool isolation
  • 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

Stripe · Publisher source ↗

First-party MCP

Shopify · Publisher source ↗

Maintenance
Maintenance details

Repo: Aug 14, 2026

Package: Not documented

Repo: Not documented

Package: Not documented

Popularity evidence
GitHub stars

1,743

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

Not documented
Shared repository stars

1,714

Shared repository stars (not MCP-specific) · checked 2026-08-14T18:46:26.000Z

Not documented
External adoption evidence
  • github: repository stars: 1,743Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Not documented
Client coverage
Client coverage details
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
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 hosted https://mcp.stripe.com endpoint uses Stripe OAuth. Stripe also documents a local npx option using STRIPE_SECRET_KEY; prefer restricted test-mode credentials when local-key authentication is necessary.Shopify documents no authentication requirement for the Storefront MCP endpoint. Some stores may restrict access. UCP catalog requests include an agent-profile reference.
CostStripe documents no separate MCP access fee. Normal Stripe product, transaction, account, and chosen AI-client charges still apply; ChatGPT custom connector availability also depends on an eligible ChatGPT plan.Shopify documents no separate Storefront MCP fee. Merchant Shopify plan, application hosting, model, and client costs remain applicable.
PermissionsThe hosted server receives OAuth access selected during Stripe authorization. The documented tool set includes read operations and write operations such as creating customers, products, prices, payment links, invoices, coupons, refunds, and disputes-related actions; actual access remains bounded by the authorized Stripe account and credential.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 handlingRequests and tool results pass between the MCP client, Stripe's hosted MCP endpoint, and the connected Stripe account. The server can return account and payment-related records plus Stripe knowledge-base content to the client. A local @stripe/mcp process receives the configured STRIPE_SECRET_KEY. Do not place live secret keys in shared configuration or logs.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
  • The hosted endpoint simplifies setup and uses OAuth, while the local package can use a secret key and therefore expands local credential-handling responsibility.
  • Stripe labels the MCP service a public preview, so tools and behavior can change.
  • Tool access is convenient but can create or modify payment-related resources within the granted Stripe account.
  • 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 contextThis is a write-capable financial integration. Use test mode for evaluation, least privilege, explicit confirmation for every mutation, separate untrusted web content from payment actions, and revoke MCP sessions promptly when no longer needed. This review relies on publisher documentation and does not claim MCP100 execution testing.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-242026-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 →