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 fieldShopify Storefront MCPMCP100 SelectedPayPal MCPMCP100 Selected
Task fit
Best for
  • Searching and comparing products from a specific Shopify storefront
  • Answering store policy and FAQ questions
  • Creating and updating a shopper cart before checkout
  • Querying invoices, orders, subscriptions, disputes, and shipment information
  • Sandbox prototyping of merchant workflows
  • Teams able to issue, scope, rotate, and monitor PayPal credentials
Not ideal for
  • Merchant administration, inventory editing, or back-office order management
  • Cross-store catalog aggregation without separate store endpoints
  • Unattended production payment, refund, or invoice decisions
  • Users without PayPal developer credential management
  • Assistants that only need public PayPal documentation
Avoid when
  • 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
  • Production financial actions would execute without explicit confirmation
  • Access tokens must be embedded in committed configuration
  • Merchant-account activity cannot be monitored and credentials cannot be revoked quickly
Provenance
Provenance details

First-party MCP

Shopify · Publisher source ↗

First-party MCP

PayPal · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Not documented

Package: Not documented

Popularity evidence
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✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationShopify documents no authentication requirement for the Storefront MCP endpoint. Some stores may restrict access. UCP catalog requests include an agent-profile reference.Local mode uses PAYPAL_ACCESS_TOKEN and PAYPAL_ENVIRONMENT. Remote mode supports PayPal login and consent or token authorization; PayPal publishes separate Sandbox and Production endpoints.
CostShopify documents no separate Storefront MCP fee. Merchant Shopify plan, application hosting, model, and client costs remain applicable.The MCP package is publicly available. Normal PayPal account, transaction, product, API, and merchant-service fees or limits remain applicable.
PermissionsThe 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.Capabilities depend on enabled tools and the PayPal credential and can include reads and mutations across invoices, orders, subscriptions, disputes, shipments, transaction details, and related merchant resources.
Data handlingRequests 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.The local MCP process sends merchant, customer, payment, and task data to PayPal APIs and returns results to the MCP client. The hosted option processes requests through PayPal's remote MCP service.
Limitations
Tradeoffs
  • 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.
  • The local npm server is portable and publisher documented, but executes package code on the user's machine.
  • The documented `--tools=all` setup is convenient but exposes a broad commerce surface; narrower tool selection is safer where supported.
  • Sandbox reduces financial impact but does not replace production authorization and operational controls.
Risk contextKeep 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.Production access can create financial loss or customer-facing changes and can disclose transaction data. Start with Sandbox, keep credentials out of files and history, minimize tools, and require approval for every mutation.
Evidence date
Editorial review2026-07-242026-07-24
Candidate evidence2026-07-29T20:58:26.000Z2026-07-29T20:58:26.000Z

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

Read the evidence method →