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 RecommendedPayPal MCPMCP100 Recommended
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
  • 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
  • Unattended production payment administration
  • Workflows that require Stripe API operations not exposed by the current tool set
  • Unattended production payment, refund, or invoice decisions
  • Users without PayPal developer credential management
  • Assistants that only need public PayPal documentation
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
  • 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

Stripe · 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
GitHub starsNot documented

12

GitHub stars · checked 2026-09-24T18:01:37.627000Z

Package downloads / 30 days

56,858

package downloads / 30 days · checked 2026-09-24T18:01:10.986000Z

2,304

package downloads / 30 days · checked 2026-09-24T18:01:10.803000Z

Shared repository stars

1,831

Shared repository stars (not MCP-specific) · checked 2026-09-24T18:01:37.616000Z

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✓ 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
AuthenticationThe hosted https://mcp.stripe.com endpoint uses Stripe OAuth. Stripe also documents a local path using Stripe credentials; prefer Restricted API Keys with only the required permissions, and keep live versus sandbox context explicit. Do not infer Agent-Key or session-revocation behavior beyond current Stripe MCP documentation.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.
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.The MCP package is publicly available. Normal PayPal account, transaction, product, API, and merchant-service fees or limits 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.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 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.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 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 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 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.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-09-24T04:25:05.554391Z2026-09-24T04:25:05.554391Z

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

Read the evidence method →