How to Use the Bolt MCP in Cursor

Q: How do I configure the Bolt MCP Server in Cursor?

Create a .cursor/mcp.json file in your repository root and add the server configuration. Cursor will detect the new tools, allowing your agent to run checkout commands instantly.

Q: Can Cursor write unit tests for Bolt payment flows?

Yes. Cursor can call getorderdetails to see real order structures, then use that exact shape to write highly accurate mock tests for your test suite.

Q: Can I use Bolt to test merchant accounts in Cursor?

Yes, your agent can execute getmerchantstatus to check if your current API keys are pointing to a sandbox or production merchant account.

Code your ecommerce checkout with real Bolt transaction data injected directly into your Cursor editor.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Bolt MCP to Cursor

Create your Vinkius account to connect Bolt to Cursor 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 Bolt with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Write checkout code using real Bolt order tokens

Stop writing mock objects when building your Bolt shopping cart inside Cursor. In Cursor, your agent can call `create_order_token` to fetch a live session token and inject it directly into the React component you are editing. This lets you test the actual Bolt checkout overlay behavior inside Cursor using production-grade payloads. You see exactly how your frontend handles the Bolt response without leaving your Cursor workspace.

Debug payment webhooks using this Cursor MCP Server

When configuring your Bolt payment listener, you can ask Cursor to analyze your webhook payload. The MCP Server runs `list_webhooks` to match your local handler's URL against your registered Bolt endpoints. If a transaction fails, ask Cursor to run `get_transaction` on the failed ID. Cursor reads the Bolt error codes directly and highlights the exact line in your controller that needs a fix.

Manage refunds and voids while writing backend logic

Write your Bolt refund controller side-by-side with live API responses inside Cursor. Ask Cursor's Composer or Agent mode to draft a refund route, using `refund_transaction` to verify the required arguments. Cursor checks the schema of `void_transaction` to ensure your backend handles uncaptured Bolt authorization cancellations correctly. You get working, type-safe Bolt integration code inside Cursor on your first try.

Setup guide

Set up Bolt MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Bolt MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Bolt transactions." If the MCP tools are loaded correctly, Cursor will call the Bolt tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "bolt-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 Bolt. 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 Bolt 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 Bolt MCP in Cursor

Create a `.cursor/mcp.json` file in your repository root and add the server configuration. Cursor will detect the new tools, allowing your agent to run checkout commands instantly.

Yes. Cursor can call `get_order_details` to see real order structures, then use that exact shape to write highly accurate mock tests for your test suite.

Yes, when you ask the Cursor agent to check a payment status, it automatically selects `get_transaction` from its toolbelt to pull the status into your chat.

Yes, your agent can execute `get_merchant_status` to check if your current API keys are pointing to a sandbox or production merchant account.

Cursor interfaces directly with the secure Vinkius vault to fetch your merchant account data. Your active API keys and webhook secrets are encrypted in transit and never exposed to the LLM backend or stored locally in your workspace files.

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