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 fieldPayPal MCPMCP100 SelectedxeroMCP100 Selected
Task fit
Best for
  • Querying invoices, orders, subscriptions, disputes, and shipment information
  • Sandbox prototyping of merchant workflows
  • Teams able to issue, scope, rotate, and monitor PayPal credentials
  • Accounting investigation and controlled bookkeeping workflows in Xero.
Not ideal for
  • Unattended production payment, refund, or invoice decisions
  • Users without PayPal developer credential management
  • Assistants that only need public PayPal documentation
  • Teams outside the publisher ecosystem or without least-privilege credentials
Avoid when
  • 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
  • The connected identity is broader than the task requires
  • Tool calls cannot be reviewed before consequential mutations
Provenance
Provenance details

First-party MCP

PayPal · Publisher source ↗

First-party MCP

ecosystem:xero · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Jun 5, 2026

Package: Not documented

Popularity evidence
GitHub starsNot documented

350

GitHub stars · checked 2026-08-14T18:46:26.000Z

External adoption evidenceNot documented
  • github: repository stars: 350Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
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
AuthenticationLocal 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.The official server uses Xero OAuth credentials and organization selection.
CostThe MCP package is publicly available. Normal PayPal account, transaction, product, API, and merchant-service fees or limits remain applicable.The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.
PermissionsCapabilities 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.Xero organization permissions and OAuth scopes govern accounting data and mutations.
Data handlingThe 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.Authorized 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.
Limitations
Tradeoffs
  • 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.
  • Accounting records and invoices are financially consequential and may contain personal or tax information.
Risk contextProduction 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.Accounting records and invoices are financially consequential and may contain personal or tax information. 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.
Evidence date
Editorial review2026-07-242026-07-30
Candidate evidence2026-07-29T20:58:26.000Z2026-08-14T18:46:26.000Z

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

Read the evidence method →