How to Use the Checkout.com MCP in VS Code Copilot

Q: How do we roll out the Checkout.com tools for VS Code Copilot to our team?

Create a .vscode/mcp.json file in your project's root directory and add the Vinkius MCP Server configuration. Commit this file to your Git repository. Any developer who pulls the repo and uses VS Code will automatically have the tools available to their Copilot agent.

Give your whole team access to Checkout.com in VS Code. Standardize payment ops with a shared config your Copilot agent can use.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Checkout.com MCP to VS Code Copilot

Create your Vinkius account to connect Checkout.com to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Checkout.com with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Standardize payment tools for your entire team

This MCP Server for Checkout.com brings payment operations directly into VS Code. By adding the server config to a `.vscode/mcp.json` file and committing it to your repo, every developer on the team gets the same set of tools for their Copilot agent. Now, when a developer needs to `request_payment` or `capture_payment`, their agent uses the same, pre-approved tool everyone else does. It eliminates one-off scripts and ensures your team interacts with the payment gateway consistently.

Manage customer instruments from your editor

Give your team's Copilot agents the power to manage vaulted payment methods. The server includes tools to `create_instrument`, `get_instrument`, and `delete_instrument` within your Checkout.com account. This is perfect for teams building subscription services or features that require saved cards. Because the configuration is shared, you control exactly how your team's agents interact with sensitive customer data. It provides a safe, auditable path for developers to build features without needing direct access to production keys or dashboards.

Inspect and debug payments with Copilot

When a payment issue comes up, a developer can ask their Copilot agent to investigate. The agent can use `get_payment_details` to pull the full properties of a transaction or `get_payment_actions` to see its history, right inside VS Code. This puts critical debugging information in the hands of your developers instantly. They don't have to switch contexts to a web dashboard or ask someone else to look up the data. The result is faster problem-solving and less downtime.

Setup guide

Set up Checkout.com MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Checkout.com MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Checkout.com tools listed. Try asking: "List my recent Checkout.com transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "checkoutcom-1-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Checkout.com. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Checkout.com now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Checkout.com MCP in VS Code Copilot

Create a `.vscode/mcp.json` file in your project's root directory and add the Vinkius MCP Server configuration. Commit this file to your Git repository. Any developer who pulls the repo and uses VS Code will automatically have the tools available to their Copilot agent.

It ensures consistency and governance. Every developer's Copilot agent uses the exact same tools to interact with Checkout.com, which is defined in a single, version-controlled file. This prevents fragmentation and gives you a single point of control for payment operations.

Yes. The Vinkius MCP Server connects to your existing Checkout.com account. You configure it with your credentials, which are stored securely on the Vinkius platform, not in your codebase. Your team's agents can then perform actions on your behalf.

Yes. The connection is managed through VS Code, which is widely used in enterprise environments, and the Vinkius platform is built on a zero-trust architecture. This setup is designed to work within SOC 2 compliant workflows, providing an auditable and secure way to extend Copilot.

This server is built to handle Checkout.com transaction data and vaulted instrument tokens. It does not access or store raw payment credentials. The Vinkius platform processes each tool call in a dedicated, single-use sandbox, and the `.vscode/mcp.json` file only contains a reference to the server, not your private keys.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript