How do I install Checkout.com?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Checkout.com need an API key?

No required environment variable is listed on this record.

What transport does Checkout.com use?

Checkout.com is reached over HTTP.

When was Checkout.com last checked?

Last checked 2026-11-09. Search Checkout.com docs and API reference, plus manage payments, refunds, and payment links.

Checkout.com MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://mcp.checkout.com

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

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

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.checkout-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://mcp.checkout.com"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 1.0.0
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

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

Environment	URL
Production	`https://mcp.checkout.com`
Sandbox	`https://checkout.mcp.sbox.cko.tech`

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 Desktop / Claude Code — add the server, then run /mcp to trigger the sign-in flow:

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

VS Code — open the Command Palette, run MCP: Open User Configuration, and add:

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

Save, then run MCP: List Servers, select the Checkout MCP, and choose Start to sign in.

Cursor — add to ~/.cursor/mcp.json, or your project's .cursor/mcp.json:

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

To disconnect, disable the server in your client's MCP settings or delete it from the config file.

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