Head to head · Invoicing · October 2026 research run

Metronome vs PayPal MCP server

Metronome scores 69.7 (B) on agent readiness against PayPal MCP server's 56.3 (C), and leads in 5 of 7 scored categories. PayPal MCP server leads on transparency & trust. Both do invoicing.

Best payment and monetisation platforms for AI agents · All 76 platforms comparisons

Which one, for what

Metronome B

Good for A company that meters usage and bills on contracts, credits and commits, with invoices delivered through Stripe, NetSuite or cloud marketplaces.

Ahead on

  • Reliability, 68 against 52
  • Schema & documentation, 88 against 70
  • Agent ergonomics, 75 against 66
  • Security & auth, 68 against 48
  • Maintenance & community, 82 against 64

Watch for

Errors are a single message string with no machine-readable code, and the API description documents a 4xx response on 87 of 142 operations

PayPal MCP server C

Good for A merchant already on PayPal who wants an assistant to draft and send invoices, look up orders and transactions, and manage subscriptions and disputes.

Ahead on

  • Transparency & trust, 78 against 65

Also in its favour

  • Runs on your own machine
  • Open source

Watch for

The quickstart gives /http for streamable HTTP. On 8 October 2026 it returned 404 on both hosts, and /mcp returned the OAuth challenge

Score by category

CategoryWeight this runMetronomePayPal MCP serverEdge
Reliability16%206852Metronome +16
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28870Metronome +18
Agent ergonomics13%16.27566Metronome +9
Security & auth14%17.56848Metronome +20
Payments & pricing10%12.53940PayPal MCP server +1
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88264Metronome +18
Transparency & trust7%8.86578PayPal MCP server +13
Negative events≤150-2
Total69.7 · B56.3 · C

Facts side by side

FactMetronomePayPal MCP server
KindHTTP APIMCP server
VendorMetronome (Stripe)PayPal
Hosted endpointhttps://api.metronome.comhttps://mcp.paypal.com/mcp
TransportsHTTPstdio, SSE (legacy), Streamable HTTP
AuthAPI keyOAuth or key
PricingPay per usePay per use
x402nono
LicenceProprietary service under the Stripe Services Agreement. The SDKs on GitHub are Apache-2.0Apache-2.0 for the local server and the agent toolkit. The hosted server is a closed service under the PayPal Developer Agreement
Tools exposednone28
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.paypal/paypal-mcp-server
Last release2026-09-292026-09-01
Terms last updated2026-09-282024-11-18
Privacy policy last updated2026-04-282026-09-28
Customer content may train modelsyesyes
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesyes
Popularity7 stars, 363k npm/wk995 npm/wk, 107 PyPI/wk

Verdicts

Metronome

Metronome's API carries an Idempotency-Key on every POST, a public OpenAPI description of 142 operations, and agentic tokens whose writes wait for a person's approval. Prices for the Startup plan are public. Errors return only a message string, token scopes are set through support, and the status feed lists 13 incidents since 22 July 2026.

PayPal MCP server

The hosted server uses OAuth with PKCE and dynamic client registration, and the local package defaults to the sandbox. No tool carries a read-only or destructive annotation, no confirmation step for refunds or captures was found, and the documented /http streamable HTTP path returned 404 on 8 October 2026 while /mcp answered.

Before you call either

Metronome

  1. Send an Idempotency-Key header on every POST and reuse it on retry. A cached error is returned for the same key, so use a new key after fixing the cause
  2. Give each usage event a stable transaction_id. Metronome ignores repeats for 34 days and accepts at most 100 events per /v1/ingest call
  3. On 429 read X-Metronome-Rate-Limit-Type (client or customer) and back off. Unlisted endpoints default to 8 requests a second
  4. With an agentic token, expect 403 AgenticMutationBlocked on writes. Post the original method, path and body to /v1/approval_requests and show the person the approval_url
  5. Use a sandbox token for testing. The token alone decides whether a call reaches sandbox or production data

PayPal MCP server

  1. Connect a remote client to https://mcp.paypal.com/mcp or /sse. The documented /http path returned 404 on 8 October 2026
  2. Set PAYPAL_ENVIRONMENT=PRODUCTION for live calls. Any other value, including the registry's LIVE, runs against the sandbox
  3. Refresh PAYPAL_ACCESS_TOKEN before it expires. The README gives expires_in 32400 seconds, and the local server takes no client ID or secret
  4. Pass --tools= with only the keys the task needs, such as invoices.list,orders.get. --tools=all loads 28 keys including refunds and captures
  5. Ask the user before create_refund, pay_order, cancel_subscription or accept_dispute_claim. The server applies them without a confirmation step

Questions

Which is better for AI agents, Metronome or PayPal MCP server?

Metronome scores 69.7 (B) on agent readiness against PayPal MCP server's 56.3 (C), and leads in 5 of 7 scored categories. PayPal MCP server leads on transparency & trust.

Do Metronome and PayPal MCP server need an API key?

Metronome needs an API key. PayPal MCP server takes an API key or an OAuth sign-in.

Can an agent call Metronome and PayPal MCP server without installing anything?

Yes. Metronome has a hosted endpoint at https://api.metronome.com and PayPal MCP server at https://mcp.paypal.com/mcp.

Are Metronome and PayPal MCP server open source?

No open-source release is listed for Metronome. PayPal MCP server is open source (Apache-2.0 for the local server and the agent toolkit. The hosted server is a closed service under the PayPal Developer Agreement).

Other comparisons with Metronome or PayPal MCP server

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.