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 fieldDodo Payments API MCPWatchlist candidateShopify Storefront MCPMCP100 Selected
Task fit
Best for
  • Dodo Payments users integrating or operating billing workflows through an MCP-capable coding agent, preferably in test mode first.
  • Searching and comparing products from a specific Shopify storefront
  • Answering store policy and FAQ questions
  • Using UCP Cart MCP for cart workflows before checkout.
Not ideal for
  • Users who need a broadly proven, low-risk, fully mature Selected-grade integration today.
  • Merchant administration, inventory editing, or back-office order management
  • Cross-store catalog aggregation without separate store endpoints
Avoid when
  • Avoid high-impact or sensitive production use unless the documented authentication, permissions, rollback, and data handling match your environment.
  • 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

endpoint:https: · Publisher source ↗

First-party MCP

Shopify · Publisher source ↗

Maintenance
Maintenance details

Stale

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
AuthenticationRemote API MCP uses browser OAuth by default; optional local server can use Dodo API credentials.Shopify documents no authentication requirement for the Storefront MCP endpoint. Some stores may restrict access. UCP catalog requests include an agent-profile reference.
CostDodo Payments transaction/API/account pricing applies; MCP access does not make payment operations free.Shopify documents no separate Storefront MCP fee. Merchant Shopify plan, application hosting, model, and client costs remain applicable.
PermissionsHigh-impact financial/billing authority within the authorized Dodo account; use test mode and restrict production credentials.The Storefront MCP exposes catalog and storefront policy/FAQ search. Cart workflows use the UCP Cart MCP endpoint at https://{shop-domain}/api/ucp/mcp. It does not grant Shopify Admin API access.
Data handlingPayment/customer/subscription data can transit Dodo Payments and the connected AI client/provider.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
  • Live payment/refund/subscription actions need stronger production safeguards and human-confirmation guidance for Selected.
  • 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.
  • Storefront cart tools were maintained only through 2026-08-31; use UCP Cart MCP for cart workflows.
Risk contextLive payment/refund/subscription actions need stronger production safeguards and human-confirmation guidance for Selected.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-09-13T00:00:00Z2026-09-05
Candidate evidence2026-09-13T00:00:00Z2026-09-05T00:00:00.000Z

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

Read the evidence method →