Checkout.com

listing.by

Search Checkout.com API docs and guides, check payment status, and run refunds, voids and payment links.

state.auth.long (state.auth.title)Streamable HTTP

listing.connect

listing.explain.oauth

https://mcp.checkout.com

listing.note.oauth

listing.share.h

listing.share.p

mcp.tc/i/checkout-com

listing.about

Connects an AI assistant to Checkout.com. It reads the current technical docs, API reference and support knowledge base, recommends an integration path for a given use case and stack, and acts on payments in your own account: check a payment, refund it, void an authorization or create a payment link.

It is a hosted remote server using streamable HTTP at https://mcp.checkout.com, with a sandbox at https://checkout.mcp.sbox.cko.tech. Sign in through OAuth with a Checkout.com Dashboard account. No API keys are needed. The agent can only do what your Dashboard user is permitted to do. The server is in beta.

listing.can

  • Search Checkout.com docs, API reference and support knowledge base
  • Get a recommended integration path for your use case and stack
  • Check the status of a payment
  • Refund a payment
  • Void a payment authorization
  • Create payment links

listing.tools

listing.notools.oauth

listing.prompts

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

  • What's the status of payment pay_xxxxx?

  • Refund payment pay_xxxxx.

  • Create a payment link for a customer order.

listing.setup.h

listing.setup.oauth

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http checkout-com https://mcp.checkout.com
  1. Start Claude Code, type /mcp, pick checkout-com and choose Authenticate. A browser window opens for the Checkout.com sign-in.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Settings → Connectors and click Add custom connector.
  2. Name it Checkout.com and paste this URL:
https://mcp.checkout.com
  1. Click Add, then Connect, and sign in when Checkout.com asks.

Claude Desktop's JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://mcp.checkout.com and click Add.
  2. Click Connect and sign in when Checkout.com asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, open Settings → Security and login and turn on Developer mode.
  2. Go to chatgpt.com/plugins and click + to create an app for a remote MCP server.
  3. Paste https://mcp.checkout.com as the server URL and choose OAuth. ChatGPT sends you to Checkout.com to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

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

Cursor shows Needs login next to the server. Click it to sign in.

VS Code

Or from a terminal:

code --add-mcp '{"name":"checkout-com","type":"http","url":"https://mcp.checkout.com"}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "checkout-com": {
      "type": "http",
      "url": "https://mcp.checkout.com"
    }
  }
}

VS Code asks you to sign in the first time the server starts.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "checkout-com": {
      "serverUrl": "https://mcp.checkout.com"
    }
  }
}
  1. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add checkout-com --url https://mcp.checkout.com
codex mcp login checkout-com

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.checkout-com]
url = "https://mcp.checkout.com"

Gemini CLI

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

Then, inside Gemini CLI, run /mcp auth checkout-com to sign in.

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI's settings file.

{
  "mcpServers": {
    "checkout-com": {
      "type": "http",
      "url": "https://mcp.checkout.com"
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://mcp.checkout.com.

listing.faq

Can I paste mcp.tc/i/checkout-com into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://mcp.checkout.com, so your client talks to Checkout.com directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does Checkout.com need an API key or a sign-in?

Yes, you need a Checkout.com account. The first time your client connects, it opens Checkout.com's sign-in page. The token goes straight to the server's own URL, never through mcp.tc.

Is Checkout.com a remote or a local server?

Remote. Checkout.com hosts it at https://mcp.checkout.com, and it speaks Streamable HTTP. There's nothing to install.

What can Checkout.com do?

You can search Checkout.com docs, API reference and support knowledge base, get a recommended integration path for your use case and stack and check the status of a payment.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Who wrote this page?

mcp.tc's robot read Checkout.com's own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead listing.em.how

listing.em.badge

em.prev_lightem.prev_dark
Markdown
[![Checkout.com on mcp.tc](https://mcp.tc/i/checkout-com/badge.svg)](https://mcp.tc/i/checkout-com)
HTML
<a href="https://mcp.tc/i/checkout-com"><img src="https://mcp.tc/i/checkout-com/badge.svg" alt="Checkout.com on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML
<script src="https://mcp.tc/w/checkout-com.js" async></script>

listing.em.widget_note

iframe

HTML
<iframe src="https://mcp.tc/embed/checkout-com" title="Checkout.com on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json

https://mcp.tc/i/checkout-com.json

listing.em.fields

listing.disclaimer_checked