What can you do with the Bolt integration?

LiveContext exposes 17 operations on Bolt, covering transaction, address, webhook and payment method. Common uses include shipping a fulfilled order, completing a Bolt SSO login and reconciling a webhook event.

Which OAuth scopes does Bolt require?

It depends on the operation: each one declares the scopes Bolt requires for it. The most common are bolt.account.manage (3 operations) and bolt.account.view (3 operations).

LiveContext

All integrations

Bolt integration

One-click checkout and payment processor for e-commerce. Generate order tokens, authorize and capture credit-card transactions, refund and void payments, manage Bolt Account customers, addresses and saved payment methods, register webhook subscriptions, and pull merchant order data. Used by retailers to remove checkout friction, fight fraud and offer a unified network checkout across stores.

17 toolsAPI keyAPI docs

Connect Bolt How integrations work

Common Bolt use cases

shipping a fulfilled order
completing a Bolt SSO login
reconciling a webhook event
processing a customer return
removing a stale callback URL
auditing webhook subscriptions
server-side checkout completion
cancelling an out-of-stock order
rendering the wallet at checkout
starting a Bolt checkout session

What you can do with Bolt

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Transaction, 6 operations

POSTauthorize_transaction
Authorize a credit-card payment on a Bolt cart, optionally auto-capturing or creating a Bolt Account.
POSTcapture_transaction
Capture funds (full or partial) on an authorized Bolt transaction.
GETget_transaction_details
Retrieve full details for a single Bolt transaction.
POSTrefund_transaction
Refund a captured Bolt transaction (full or partial).
POSTreview_transaction
Force-approve or force-reject a Bolt transaction held in fraud review.
POSTvoid_transaction
Cancel an authorized-but-not-captured Bolt transaction.

Address, 3 operations

POSTcreate_address
Add a new address to the Bolt Account address book.
DELETEdelete_address
Remove a saved address from the Bolt Account.
GETlist_addresses
List the Bolt Account's saved addresses.

Webhook, 3 operations

POSTcreate_webhook
Subscribe an HTTPS URL to a Bolt event type.
DELETEdelete_webhook
Remove a Bolt webhook subscription.
GETlist_webhooks
List the merchant's configured Bolt webhook subscriptions.

Payment method, 2 operations

DELETEdelete_payment_method
Remove a saved credit card from the Bolt Account.
GETlist_payment_methods
List the Bolt Account's saved credit cards.

Account, 1 operation

GETget_account
Retrieve the authenticated Bolt Account profile, addresses and saved cards.

Oauth token, 1 operation

POSTget_oauth_token
Exchange a Bolt authorization code (or refresh token) for OAuth2 access and refresh tokens.

Order token, 1 operation

POSTcreate_order_token
Generates a Bolt order token from a cart payload. Required first step before authorizing a payment.

OAuth scopes Bolt requires

Each operation declares the scopes Bolt requires for it.

bolt.account.manageneeded by create_address, delete_address, delete_payment_method
bolt.account.viewneeded by get_account, list_addresses, list_payment_methods

Use Bolt from Claude Code, Cursor or Codex

Connect Bolt in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Bolt operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Bolt

Create your workspace
Sign up free. Nothing to install.
Connect Bolt once
Add your Bolt connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Bolt integration FAQ

What can you do with the Bolt integration?: LiveContext exposes 17 operations on Bolt, covering transaction, address, webhook and payment method. Common uses include shipping a fulfilled order, completing a Bolt SSO login and reconciling a webhook event.
Which OAuth scopes does Bolt require?: It depends on the operation: each one declares the scopes Bolt requires for it. The most common are bolt.account.manage (3 operations) and bolt.account.view (3 operations).