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 MCPWatchlist candidatexeroMCP100 Selected
Task fit
Best for
  • Dodo Payments users integrating or operating billing workflows through an MCP-capable coding agent, preferably in test mode first.
  • Accounting investigation and controlled bookkeeping workflows in Xero.
Not ideal for
  • Users who need a broadly proven, low-risk, fully mature Selected-grade integration today.
  • Teams outside the publisher ecosystem or without least-privilege credentials
Avoid when
  • Avoid high-impact or sensitive production use unless the documented authentication, permissions, rollback, and data handling match your environment.
  • The connected identity is broader than the task requires
  • Tool calls cannot be reviewed before consequential mutations
Provenance
Provenance details

First-party MCP

endpoint:https: · Publisher source ↗

First-party MCP

ecosystem:xero · Publisher source ↗

Maintenance
Maintenance details

Stale

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

Package downloads / 30 daysNo reliable download data

19,233

package downloads / 30 days · checked 2026-09-08

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.The official server uses Xero OAuth credentials and organization selection.
CostDodo Payments transaction/API/account pricing applies; MCP access does not make payment operations free.The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.
PermissionsHigh-impact financial/billing authority within the authorized Dodo account; use test mode and restrict production credentials.Xero organization permissions and OAuth scopes govern accounting data and mutations.
Data handlingPayment/customer/subscription data can transit Dodo Payments and the connected AI client/provider.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
  • Live payment/refund/subscription actions need stronger production safeguards and human-confirmation guidance for Selected.
  • Accounting records and invoices are financially consequential and may contain personal or tax information.
Risk contextLive payment/refund/subscription actions need stronger production safeguards and human-confirmation guidance for Selected.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-09-13T00:00:00Z2026-07-30
Candidate evidence2026-09-13T00:00:00Z2026-08-14T18:46:26.000Z

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

Read the evidence method →