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 MCPShortlist candidatePayPal MCPMCP100 Recommended
Task fit
Best for
  • Dodo Payments users integrating or operating billing workflows through an MCP-capable coding agent, preferably in test mode first.
  • 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
  • Users who need a broadly proven, low-risk, fully mature Recommended-grade integration today.
  • Unattended production payment, refund, or invoice decisions
  • Users without PayPal developer credential management
  • Assistants that only need public PayPal documentation
Avoid when
  • Avoid high-impact or sensitive production use unless the documented authentication, permissions, rollback, and data handling match your environment.
  • 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

endpoint:https: · 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

3,724

package downloads / 30 days · checked 2026-10-21

2,304

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

Shared repository stars

54

Shared repository stars (not MCP-specific) · checked 2026-10-21

Not documented
Client coverage
Client coverage detailsNot documented
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
AuthenticationRemote API MCP uses browser OAuth by default; optional local server can use Dodo API credentials.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.
CostDodo Payments transaction/API/account pricing applies; MCP access does not make payment operations free.The MCP package is publicly available. Normal PayPal account, transaction, product, API, and merchant-service fees or limits remain applicable.
PermissionsHigh-impact financial/billing authority within the authorized Dodo account; use test mode and restrict production credentials.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 handlingPayment/customer/subscription data can transit Dodo Payments and the connected AI client/provider.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
  • Live payment/refund/subscription actions need stronger production safeguards and human-confirmation guidance for Recommended.
  • 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 contextLive payment/refund/subscription actions need stronger production safeguards and human-confirmation guidance for Recommended.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-10-212026-07-24
Candidate evidence2026-10-21T00:00:00Z2026-09-24T04:25:05.554391Z

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

Read the evidence method →