Bolt MCP. Manage payments, refunds, and order tokens instantly.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Bolt MCP Server lets your AI agent manage your entire checkout and payment lifecycle. You can list transactions, retrieve order details, capture payments, void pending charges, and issue refunds—all through natural conversation.
It connects directly to your Bolt Merchant account for real-time payment operations.
What your AI agents can do
Capture transaction
Completes a payment by finalizing a previously authorized transaction.
Create order token
Generates a secure token needed to start a one-click checkout session.
Get account details
Retrieves the core details for your connected merchant account.
List recent payments and get detailed information on specific transactions or orders.
Generate checkout tokens, capture authorized charges, or void pending payments.
Issue partial or full refunds against completed transactions.
Retrieve the current status of your merchant account and pull core account details.
List and review all webhooks configured on your Bolt merchant account.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Bolt MCP Server: 10 Tools for Payments & Orders
Use these tools to manage the full payment lifecycle: create tokens, capture funds, list transactions, and issue refunds via natural language prompts.
019d7560capture transaction
Completes a payment by finalizing a previously authorized transaction.
019d7560create order token
Generates a secure token needed to start a one-click checkout session.
019d7560get account details
Retrieves the core details for your connected merchant account.
019d7560get merchant status
Checks and returns the current operational status and configuration of your merchant account.
019d7560get order details
Retrieves full information about a specific order ID.
019d7560get transaction
Gets all the data for a specific, known transaction reference.
019d7560list transactions
Fetches a list of recent transactions from your account history.
019d7560list webhooks
Lists all webhooks currently set up for real-time data synchronization.
019d7560refund transaction
Initiates a refund—full or partial—for a completed transaction.
019d7560void transaction
Cancels an authorized payment that hasn't been captured yet.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Bolt, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Bolt MCP Server lets your AI agent manage your whole checkout and payment cycle. You can list transactions, pull order info, capture payments, void pending charges, and issue refunds—all just by talking to it. It connects straight to your Bolt Merchant account for real-time payment stuff.
How Bolt MCP Works
- 1 Subscribe to the server and provide your Bolt Private API Key and desired environment (api or api-sandbox).
- 2 Your AI client connects to the server, authenticating the connection with your merchant credentials.
- 3 You ask your agent to perform an action (e.g., 'Refund $15.00 for transaction ABC-123'), and the agent calls the appropriate tool.
The bottom line is you manage payments and order flows by speaking to your AI agent, which executes the necessary API calls for you.
Who Is Bolt MCP For?
This is for e-commerce operations staff and customer support teams who deal with payments daily. If you spend time clicking through multiple dashboards—checking a payment status here, then manually initiating a refund there—this saves you time. It lets you handle complex money moves through simple chat.
Checks payment statuses, verifies order tokens, and processes refunds without leaving their dashboard.
Retrieves full transaction histories and order details for customers directly within their support workflow.
Tests API integrations, validates order token generation, and audits webhook configurations using natural language prompts.
What Changes When You Connect
- Process refunds and capture payments directly. You don't need to log into the Bolt dashboard to issue a partial refund using
refund_transaction. - Verify payment status quickly. Use
list_transactionsto see recent charges and useget_transactionfor deep dives on a single reference. - Maintain merchant health. Run
get_merchant_statusto confirm your account configuration is valid and active before running a payment workflow. - Handle checkout setup. Generating secure links or tokens is simple with
create_order_token, eliminating manual API calls for basic checkout setup. - Manage pending charges. If a customer changes their mind, use
void_transactionto cancel an authorized payment before you capture the funds. - Audit system connections. Use
list_webhooksto confirm that your real-time data feeds are still correctly configured.
Real-World Use Cases
Refund needed for a canceled order.
A customer calls support and needs a refund for a charge from two weeks ago. Instead of asking the agent to copy a reference number and paste it into a separate portal, the agent uses get_transaction to confirm the details, and then runs refund_transaction to process the credit immediately.
Checking a suspicious charge.
An operations team member gets an alert about a transaction they don't recognize. They ask their agent to run list_transactions. The agent shows the list, and the team member uses get_order_details on the relevant entry to understand what product or service was charged.
Setting up a new one-click checkout.
A developer needs to test the checkout flow. They simply ask the agent to create_order_token. The agent returns the necessary token, which the developer can immediately use in their code, skipping manual API calls and setup.
Verifying account setup.
A developer is building a new integration and needs to make sure the Bolt account is ready. They run get_merchant_status, and the agent confirms the status and key details, validating the setup before any money moves happen.
The Tradeoffs
Treating payments as manual steps
The agent needs to process a refund, but the user tries to manually calculate the amount or reference ID in a separate spreadsheet before asking the agent to run the tool.
→
Just tell the agent what you need. Ask it to run refund_transaction and provide the transaction reference and the desired amount. The agent handles the API call directly.
Ignoring the payment lifecycle
A user tries to capture funds for a transaction, but the payment was already voided or the order was never properly created.
→
First, check the status. Use get_order_details or get_transaction to confirm the payment is authorized and hasn't been voided. Only then should you call capture_transaction.
Over-relying on basic listing
The user just asks to 'see transactions' and accepts the list without verifying the full details, missing key metadata like the original order ID.
→
After using list_transactions, immediately follow up with get_transaction using the specific reference ID. This pulls the full, detailed metadata you need.
When It Fits, When It Doesn't
Use this if your workflow involves managing the full lifecycle of money: creating an order token, checking the merchant status, capturing a charge, or issuing a refund. You need a single source of truth for financial state transitions.
Don't use this if your goal is simple data retrieval without financial action (e.g., just viewing a list of emails). For those cases, a basic read-only API wrapper might suffice. If you only need to list webhooks, you only need list_webhooks.
If you need to build complex, multi-step state logic (e.g., 'If status is X, then void, otherwise capture'), you must write the orchestration code yourself, but the tools provide the atomic building blocks. Use get_order_details and get_account_details to gather initial context before any write operations.
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.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manually checking payment status and initiating refunds is a slow, painful process.
Today, checking a customer's payment status means jumping between the order management dashboard and the payment processor portal. You copy the transaction ID from one place, paste it into another, and click through three different confirmation screens. If the refund amount is partial, you often have to calculate it manually and then find the exact reference number.
With the Bolt MCP Server, you tell your agent what needs fixing. You ask, 'I need to refund $15 for the order placed yesterday.' The agent handles the context, calls `get_transaction` to confirm the ID, and runs `refund_transaction`—all without you leaving the chat window. It's just conversation.
Bolt MCP Server: Process payments and refunds with the `refund_transaction` tool.
Before, processing a refund required navigating to the 'Refunds' tab, searching by date range, manually finding the transaction, and then inputting the partial amount. This process is prone to human error and takes minutes of tedious clicking.
Now, you simply tell your agent to `refund_transaction`. You provide the transaction ID and the amount, and the agent sends the request. The entire payment cycle is managed in a single, direct conversation. It's faster, cleaner, and reliable.
Common Questions About Bolt MCP
How do I check my merchant account status using the Bolt MCP Server? +
You use get_merchant_status. This tool retrieves the current operational status of your Bolt merchant account, confirming if it's active and listing key configuration details.
What is the difference between `get_transaction` and `list_transactions`? +
list_transactions gives you a recent list of transactions, which is great for an overview. get_transaction requires a specific reference ID and returns the full, detailed metadata for only that one payment.
Can I void a transaction using the Bolt MCP Server? +
Yes, you use void_transaction. This tool cancels an authorized payment that hasn't been captured yet, preventing the funds from moving out of your account.
Do I need to run `get_order_details` before capturing a payment? +
It's best practice. Use get_order_details first. This ensures you have the complete context of the order, which validates the transaction before you call capture_transaction.
How do I start a one-click checkout session with Bolt MCP Server? +
You run create_order_token. This generates the secure token needed to initiate a checkout session, allowing the payment flow to start without manual API setup.
What should I use `refund_transaction` for if the original payment was only authorized? +
You must use void_transaction first. Voiding cancels the authorization, and then you can process a refund for the amount captured before the void.
How do I get a complete picture of my recent payments using `list_transactions`? +
The list_transactions tool returns a list of transactions, and you should follow up by calling get_transaction with the specific transaction ID to pull all associated metadata.
Does `create_order_token` require specific shopper data, and how do I get it? +
Yes, creating an order token requires shopper identifiers. Use the get_account_details tool first to retrieve the authenticated shopper's necessary account information.
Can I process a refund for a transaction using the agent? +
Yes! Use the refund_transaction tool with the Bolt reference ID and the amount in cents. Your agent will initiate the credit transaction in your Bolt account.
How do I check the status of a specific Bolt transaction? +
Simply ask the agent to get_transaction and provide the reference ID. It will retrieve the latest status, such as 'Authorized', 'Completed', or 'Failed', directly from Bolt.
Can I use this to generate a checkout session token? +
Yes. Use the create_order_token tool and provide the cart details in JSON format. This will return a token that can be used on your frontend to open the Bolt checkout modal.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Bold
Automate payments via Bold Colombia — manage terminals, process transactions, generate payment links, and track settlements from any AI agent.
Highnote
Automate card issuance and financial management via Highnote — manage account holders, cards, and transactions directly from any AI agent.
Braintree
Process and manage payments via Braintree GraphQL API — search transactions, manage customers, and issue refunds directly from any AI agent.
You might also like
ShadowBot
Orchestrate ShadowBot RPA — manage automation robots, handle execution tasks, and monitor bot performance directly from any AI agent.
Ada
AI-powered customer service automation — manage conversations, end users, and knowledge via AI.
NASA DONKI — Space Weather Intelligence
NASA's Space Weather Database: coronal mass ejections (CMEs), solar flares (C/M/X class), geomagnetic storms, interplanetary shocks, solar energetic particles, radiation belt events, and real-time notifications from the DONKI system.