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 fieldAdyen MCPWatchlist candidatePayPal MCPMCP100 Selected
Task fit
Best for
  • Payment integration development and merchant-platform administration.
  • 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
  • Production use before the documented maturity gaps are resolved
  • Unattended production payment, refund, or invoice decisions
  • Users without PayPal developer credential management
  • Assistants that only need public PayPal documentation
Avoid when
  • The connected identity is broader than the task requires
  • Tool calls cannot be reviewed before consequential mutations
  • 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

Adyen · 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✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
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 package uses publisher-documented Adyen 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.
CostThe MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.The MCP package is publicly available. Normal PayPal account, transaction, product, API, and merchant-service fees or limits remain applicable.
PermissionsAdyen API credentials, roles, merchant accounts, and API permissions govern available tools.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 handlingAuthorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive finance & payments information.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
  • Adyen labels the server alpha and pilot-stage.
  • 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 contextAdyen labels the server alpha and pilot-stage. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review.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-302026-07-24
Candidate evidence2026-07-30T19:00:00.000Z2026-07-29T20:58:26.000Z

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

Read the evidence method →