Checkout MCP Server
Beta
Last updated: June 25, 2026
The Checkout Model Context Protocol (MCP) Server enables you to search through our knowledge base and manage payment operations directly from your AI-assisted integrated development environment (IDE).
The MCP server provides access to payment operations tools, and unified access to the integration content from:
- This technical documentation site
- The API reference
- The support site
It acts as a production-ready source of truth for AI tools such as Claude, GitHub Copilot, and Cursor, with the following benefits:
- Guided onboarding. Ask your AI agent to use the Guide tool to help you choose the best integration path for your use case and tech stack.
- In-app information. Search through the docs, browse API schemas, read integration guides, or troubleshoot issues directly from your code editor.
- Manage payment operations. Query payment statuses, issue refunds, void payments, and create and manage payment links.
- Reduce hallucinations. Your AI agent has direct and structured access to the latest versions of the API reference and integration guides.
- Optimized token usage. Our AI-optimized context results in faster responses and lower AI interaction costs.
Information
If you have issues or want to provide feedback for the Checkout MCP Server, contact your account manager or request support.
Information
You must have an active Dashboard account to authenticate with the Checkout MCP Server.
Add the MCP server to your IDE or AI tool's MCP configuration. The URL to connect varies depending on whether you want to connect to the production or sandbox MCP environment:
- Sandbox:
https://checkout.mcp.sbox.cko.tech - Production:
https://mcp.checkout.com
Once connected, your AI agent can query and access native guidance to answer natural-language questions directly from your IDE.
- Run the following command in the Claude Code terminal:
1claude mcp add --transport http checkout-mcp-sandbox https://checkout.mcp.sbox.cko.tech
- To trigger the MCP server's authentication flow, run the following command:
1claude /mcp
- Sign in using the credentials you use to access the Dashboard.
After you sign in successfully, you're redirected to Claude Code and your connection to the MCP server is enabled.
Information
If you're prompted to re-authenticate your connection to the MCP in a future session, run claude /mcp in the Claude Code terminal and follow the authentication flow steps again.
For more information, see Claude Code's MCP documentation.
Information
For guidance on how to enable the MCP in any other IDE or AI tool, refer to their platform's remote MCP server documentation.
The MCP provides the following tools to search through our knowledge base:
Guide- Get guidance on the best integration path for your use case.DocsSearch- Search through content on the technical documentation site.ApiSearch- Search through content on the API reference.SupportSearch- Search through content on the support site.ListOperations- Lists available API operations.GetOperation- Retrieves details for a specific API operation.GetSchema- Retrieves schema information.
You can chain tools together via a natural language prompt. For example, you can send a message to your AI agent to:
1Use the `Guide` and `ListOperations` tools to find which API operations and fields I need to create a payment request with PayPal.
The MCP provides the following tools to perform payment operations:
Create Payment Link- Generate a payment link.Get Payment Link- Retrieve a payment link.Get Payment Details- Query the status of a payment.List Entities- View your entities and change the active entity.Refunds- Initiate a refund for a payment.Voids- Void an authorized payment that has not been captured.
For example, you can send a message to your AI agent to:
1Refund the payment with the ID: pay_mbabizu24mvu3mela5njyhpit4
Information
You can only perform payment operations that your Dashboard user has permissions to action. For example, to refund a payment, you must have the Refund payments permission.
To disconnect from the MCP server, disable it from your IDE's MCP settings or remove it from the JSON configuration file.