boltcheckout

Model Context Protocol (MCP) Server for the boltcheckout API.

Summary

Bolt API Reference: Postman Collection:

About

A comprehensive Bolt API reference for interacting with Transactions, Orders, Product Catalog, Configuration, Testing, and much more.

Table of Contents

• boltcheckout
  • About
  • Installation
  • Development
  • Contributions

Installation

DXT (Desktop Extension)

Install the MCP server as a Desktop Extension using the pre-built mcp-server.dxt file:

Simply drag and drop the mcp-server.dxt file onto Claude Desktop to install the extension.

The DXT package includes the MCP server and all necessary configuration. Once installed, the server will be available without additional setup.

[!NOTE] DXT (Desktop Extensions) provide a streamlined way to package and distribute MCP servers. Learn more about Desktop Extensions.

Cursor

Or manually:

1. Open Cursor Settings
2. Select Tools and Integrations
3. Select New MCP Server
4. If the configuration file is empty paste the following JSON into the MCP Server Configuration:

{
  "mcpServers": {
    "Bolt": {
      "command": "npx",
      "args": [
        "boltcheckout",
        "start",
        "--server-index",
        "...",
        "--x-api-key",
        "...",
        "--o-auth",
        "..."
      ]
    }
  }
}

Claude Code CLI

claude mcp add boltcheckout npx boltcheckout start -- --server-index ... --x-api-key ... --o-auth ...

Windsurf

Refer to Official Windsurf documentation for latest information

1. Open Windsurf Settings
2. Select Cascade on left side menu
3. Click on Manage MCPs. (To Manage MCPs you should be signed in with a Windsurf Account)
4. Click on View raw config to open up the mcp configuration file.
5. If the configuration file is empty paste the full json

{
  "mcpServers": {
    "Bolt": {
      "command": "npx",
      "args": [
        "boltcheckout",
        "start",
        "--server-index",
        "...",
        "--x-api-key",
        "...",
        "--o-auth",
        "..."
      ]
    }
  }
}

VS Code

Refer to Official VS Code documentation for latest information

1. Open Command Palette
2. Search and open MCP: Open User Configuration. This should open mcp.json file
3. If the configuration file is empty paste the full json

{
  "mcpServers": {
    "Bolt": {
      "command": "npx",
      "args": [
        "boltcheckout",
        "start",
        "--server-index",
        "...",
        "--x-api-key",
        "...",
        "--o-auth",
        "..."
      ]
    }
  }
}

Claude Desktop

Claude Desktop doesn't yet support SSE/remote MCP servers.

You need to do the following

1. Open claude Desktop
2. Open left hand side pane, then click on your Username
3. Go to Settings
4. Go to Developer tab (on the left hand side)
5. Click on Edit Config Paste the following config in the configuration

{
  "mcpServers": {
    "Bolt": {
      "command": "npx",
      "args": [
        "boltcheckout",
        "start",
        "--server-index",
        "...",
        "--x-api-key",
        "...",
        "--o-auth",
        "..."
      ]
    }
  }
}

Stdio installation via npm

To start the MCP server, run:

npx boltcheckout start --server-index ... --x-api-key ... --o-auth ...

For a full list of server arguments, run:

npx boltcheckout --help

Development

Run locally without a published npm package:

1. Clone this repository
2. Run npm install
3. Run npm run build
4. Run node ./bin/mcp-server.js start --server-index ... --x-api-key ... --o-auth ... To use this local version with Cursor, Claude or other MCP Clients, you'll need to add the following config:

{
  "mcpServers": {
    "Bolt": {
      "command": "node",
      "args": [
        "./bin/mcp-server.js",
        "start",
        "--server-index",
        "...",
        "--x-api-key",
        "...",
        "--o-auth",
        "..."
      ]
    }
  }
}

Or to debug the MCP server locally, use the official MCP Inspector:

npx @modelcontextprotocol/inspector node ./bin/mcp-server.js start --server-index ... --x-api-key ... --o-auth ...

Contributions

While we value contributions to this MCP Server, the code is generated programmatically. Any manual changes added to internal files will be overwritten on the next generation. We look forward to hearing your feedback. Feel free to open a PR or an issue with a proof of concept and we'll do our best to include it in a future release.

MCP Server Created by Speakeasy