Checkout.com MCP Server

Give your AI agent a working knowledge of Checkout.com — the current API reference, the
integration guides, and the ability to act on real payments, without leaving your editor.

Or, in Claude Code:

claude mcp add --transport http checkout-mcp https://mcp.checkout.com

Then sign in with your Checkout.com Dashboard account. It’s a remote server — nothing to install,
host, or keep updated, and no API keys to paste into a config file.

Why use it

Ask a general-purpose coding agent to integrate a payments API and it will improvise: invented
fields, endpoints that no longer exist, request bodies that look right and fail in testing. This
server replaces that guesswork with grounded answers.

• It reads our actual documentation. The technical docs, the complete API reference, and the
  support knowledge base — the live versions, not a stale snapshot from a training run.
• It recommends a real integration path. Describe your use case and stack, and get a route
  matched to it, rather than the one generic tutorial that happened to rank highest.
• It acts, not just advises. Check a payment, refund it, void an authorization, or create a
  payment link — from a plain-language request against your own account.
• It costs less per answer. Purpose-built, AI-optimized context instead of scraped HTML means
  fewer tokens burned and faster replies.

What you can ask

Your MCP client shows the full tool list the moment it connects.

Build and debug your integration

Which API operations and fields do I need to take a payment with PayPal?

Operate live payments

What’s the status of payment pay_xxxxx?

Refund payment pay_xxxxx.

Environments

Access and permissions

You need an active Checkout.com Dashboard account. Authentication
is OAuth 2.0: your client discovers the authorization server and opens a browser for you to sign in.
No API keys are involved.

The agent inherits your permissions and nothing more. It can only perform an operation your
Dashboard user is already allowed to perform — to refund a payment, for instance, your user needs
the Refund payments
permission.

claude mcp add --transport http checkout-mcp https://mcp.checkout.com

{
  "servers": {
    "checkout-mcp": {
      "url": "https://mcp.checkout.com"
    }
  }
}

{
  "mcpServers": {
    "checkout-mcp": {
      "url": "https://mcp.checkout.com",
      "auth": {
        "CLIENT_ID": "checkout-mcp"
      }
    }
  }
}

Documentation and support

• Setup guide
• Checkout.com documentation
• API reference
• Questions or feedback: talk to your account manager or contact support

_{This repository holds the server.json metadata that lists the server in the
official MCP Registry. The server itself is
hosted and operated by Checkout.com}