Payment processor MCP servers compared
The official MCP servers from Stripe, Square, PayPal, Razorpay and Adyen compared on hosting, authentication, what they cover, licence and maturity, so you can wire an agent to the processor you already use.
Comparison
| Entry | Hosting | Auth | What it covers | Licence | Maturity |
|---|---|---|---|---|---|
| Stripe MCP Server | Hosted remote server at https://mcp.stripe.com | OAuth | Stripe API and Stripe documentation | MIT (stripe/ai repo) | Active, maintained by Stripe |
| Square MCP Server | Hosted remote server at https://mcp.squareup.com/mcp | OAuth with Square permission scopes; publishes RFC 9728 protected-resource metadata | Square seller data and APIs | unknown (hosted service) | Active, maintained by Block |
| PayPal Agent Toolkit and MCP Server | TypeScript toolkit you run yourself, plus documented remote endpoints (mcp.paypal.com/http and /sse; sandbox host available) | unknown (check PayPal's MCP docs) | PayPal APIs such as invoicing, for MCP and for OpenAI Agents SDK, LangChain and Vercel AI SDK | Apache-2.0 | Active; our unauthenticated probe of the remote /http endpoint returned 404 on 2026-10-02 |
| Razorpay MCP Server | Hosted remote server at https://mcp.razorpay.com/mcp, or local via Docker (razorpay/mcp) or Go source | Remote: Basic merchant token (base64 of key ID and secret). Local: key ID and secret | Payments, orders, payment links (incl. UPI), refunds, QR codes, settlements, payouts and saved tokens; a few write tools are local-only | MIT | Active; release v1.2.1 (Sep 2026) |
| Adyen MCP Server | Local only, via npx -y @adyen/mcp against TEST or LIVE | ADYEN_API_KEY from a dedicated webservice user | Checkout sessions, payment links, cancels and refunds; Management API for merchants, terminals, webhooks, users, API credentials | MIT | Alpha |
Verdict: Use the server from the processor you already have an account with; none of them replaces the processor. Stripe and Square are the simplest to connect because they are hosted with OAuth. Razorpay is the only one here with both a hosted and a self-run option, and the obvious pick for UPI and Indian merchants. Adyen is local and alpha, but it is the one that reaches point-of-sale terminals. For an agent that pays others per request, look at the protocols in the agent payment protocols comparison instead.
What these servers are for
A payment processor MCP server lets an agent act on your own merchant account: look up payments, create payment links or orders, issue refunds, check settlements. That is different from an agent paying for something itself, which is what x402 and the other protocols in the agent payment protocols comparison handle.
Hosted with OAuth: Stripe and Square
Stripe and Square run remote servers you add by URL, and the user signs in with OAuth, so no long-lived secret sits in the agent's config. Square also publishes RFC 9728 protected-resource metadata, so a compliant client can discover which scopes it needs. If you want a broader Stripe integration in agent frameworks, see the Stripe agent toolkit.
Hosted or local: Razorpay
The Razorpay MCP Server has the widest documented tool list here: payments (including capture and OTP flows), orders, standard and UPI payment links, refunds, QR codes, settlements, instant settlements, payouts and saved-payment tokens. The hosted server at mcp.razorpay.com/mcp takes a Basic merchant token, which is a base64 of your key ID and secret, so treat it like the secret itself. Some write tools, such as create_refund, close_qr_code and create_instant_settlement, are marked as not available on the remote server, so run it locally (Docker or Go) if you need them.
Local and alpha: Adyen
The Adyen MCP Server runs only on your machine through npx and is labelled alpha. Besides Checkout (sessions, payment links, cancels, refunds) it exposes a large slice of the Management API, including point-of-sale terminals, terminal settings and webhooks. Adyen's advice is sound for all five servers: create a dedicated API user, give it only the roles for the tools you enable, and limit the tool set with --tools=.
PayPal
The PayPal Agent Toolkit is a TypeScript library that exposes PayPal APIs such as invoicing to several agent frameworks and to MCP. PayPal's docs also list hosted endpoints; when we last probed the HTTP endpoint without credentials (2026-10-02) it returned 404, so check the current docs before relying on it.
Safety checklist
- Start in test or sandbox mode; Adyen (
--env=TEST) and PayPal (sandbox host) make this explicit. - Expose read tools first and add refunds or payouts only when you need them; these move real money.
- Keep a human approval step for refunds, payouts and anything that charges a customer.
- Don't run unknown community MCP servers in the same client session as a payments server, since a prompt injection in one tool's output can trigger another server's tools.
Directory entries in this comparison
- Stripe MCP Server: Stripe's hosted remote MCP server giving agents OAuth-secured access to the Stripe API and documentation.
- Square MCP Server: Square's hosted MCP server that lets AI assistants work with Square seller data and APIs, authorized via OAuth with Square permission scopes.
- PayPal Agent Toolkit and MCP Server: PayPal toolkit (TypeScript) exposing PayPal APIs such as invoicing to OpenAI Agents SDK, LangChain, Vercel AI SDK and MCP, plus a hosted remote MCP server.
- Razorpay MCP Server: Official Razorpay MCP server for payments, orders, payment links, refunds, QR codes, settlements and payouts; remote or local.
- Adyen MCP Server: Official alpha MCP server for Adyen Checkout and Management APIs: sessions, payment links, refunds, terminals and webhooks.
- Stripe for Agents (Stripe AI): Stripe's agent toolkit: plugins, remote MCP, agent skills and SDKs for usage-based billing, agentic commerce and machine payments.
- RFC 9728: OAuth 2.0 Protected Resource Metadata: IETF Proposed Standard defining a metadata document a protected resource publishes (at /.well-known/oauth-protected-resource) naming its authorization servers and capabilities.
- x402: Open standard for internet-native payments built on HTTP 402, letting APIs and agents pay per request across crypto and fiat networks.
Related
- Agent payment protocols compared (Comparison)
- Agent identity and MCP authorization platforms (Comparison)
Sources
- Stripe MCP docs, accessed
- stripe/ai repository, accessed
- Square MCP docs, accessed
- Square MCP protected-resource metadata, accessed
- PayPal MCP server docs, accessed
- paypal/agent-toolkit repository, accessed
- razorpay/razorpay-mcp-server repository, accessed
- Razorpay MCP server docs, accessed
- Adyen/adyen-mcp repository, accessed
- Adyen MCP server docs, accessed