Checkout.com
io.github.checkoutPublished by GitHub account checkoutv1.0.0Updated Oct 24, 2026
Search Checkout.com docs and API reference, plus manage payments, refunds, and payment links.
Overview
Remote Checkout.com MCP server that lets an assistant search live payment docs and API reference and act on real payments, refunds and payment links.
- What you can do
- Search Checkout.com technical docs, the full API reference and the support knowledge base
- Get an integration path matched to your use case and stack
- Check the status of a payment on your account
- Refund a payment or void an authorization
- Create payment links
- When to use it
- Useful when integrating Checkout.com payments into an application and you want grounded answers instead of guessed fields and endpoints, or when you want to look up and operate on live payments in your own account from a plain-language request.
- Requirements
- A remote streamable HTTP endpoint at mcp.checkout.com (sandbox endpoint also available); nothing to install. An active Checkout.com Dashboard account is required, and authentication is OAuth 2.0 with a browser sign-in; no API keys are used.
Installation
In SourceWeft
- Open Checkout.com in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.checkout%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"checkout-com": {
"type": "http",
"url": "https://mcp.checkout.com/"
}
}
}README
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.
[Install in VS Code] [Install in Cursor]
Or, in Claude Code:
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.
Manual setup
Claude Desktop / Claude Code — add the server, then run /mcp to trigger the sign-in flow:
VS Code — open the Command Palette, run MCP: Open User Configuration, and add:
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:
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
Source: README.md at commit 9a29c32
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.
