Bolt MCP. Manage Payments, Refunds, and Orders Conversationaly
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 manages your entire checkout and payment lifecycle directly from any AI client. Track transactions, initiate one-click payments, void pending charges, and process refunds without logging into a merchant dashboard.
It handles every step of the money movement, letting you control payments through natural conversation.
What your AI agents can do
Capture transaction
Finalizes an authorized payment by capturing the funds to complete the sale.
Create order token
Generates a unique, secure token needed to initiate a one-click checkout flow for a customer.
Get account details
Retrieves high-level information about your current merchant account setup.
Creates secure, temporary order tokens needed to start a one-click checkout session.
Lists all recent transactions and retrieves full details for specific past payments.
Captures authorized funds or voids pending charges that haven't settled yet.
Issues partial or full refunds against completed, captured transactions.
Checks the current status and configuration of your core merchant account.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Bolt: 10 Payment Management Tools
These ten tools give you granular control over the entire transaction lifecycle, letting your agent track everything from initial authorization to final refund.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Bolt on Vinkius019d7560capture transaction
Finalizes an authorized payment by capturing the funds to complete the sale.
019d7560create order token
Generates a unique, secure token needed to initiate a one-click checkout flow for a customer.
019d7560get account details
Retrieves high-level information about your current merchant account setup.
019d7560get merchant status
Checks the active operational status and configuration of your main merchant account.
019d7560get order details
Fetches specific details for a particular order ID.
019d7560get transaction
Retrieves all metadata for one specific, known transaction reference number.
019d7560list transactions
Lists the most recent transactions processed through your Bolt account.
019d7560list webhooks
Displays and audits all webhooks currently configured on your merchant account.
019d7560refund transaction
Sends money back to a customer for an already completed transaction.
019d7560void transaction
Cancels payments that were authorized but never fully captured or settled.
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,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ 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
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.
Manually tracking payments is a nightmare of tabs and dashboards.
Today, when a refund request comes in, you're stuck. You open the merchant portal, search by customer name or order number, find the correct transaction ID, confirm it was paid, figure out if it can be refunded, then manually click the 'Refund' button and wait for confirmation numbers to copy into an email. It takes five minutes and three different systems.
With this MCP, you tell your agent: 'Refund $45.00 for order XYZ-123.' The agent handles the entire sequence. It finds the transaction record, confirms its status, and executes the refund call—all in one go. You get immediate confirmation of the action taken.
Using `void_transaction` gives you control over pending money.
If a customer authorizes payment, but your system crashes before you can capture it—the funds are technically reserved. The manual process involves logging in and hoping the charge hasn't expired or settled yet. You’re gambling with their money.
Now, if that transaction is stuck, you tell your agent to `void_transaction`. It immediately cancels those pending authorizations for good. This gives you clean control over the payment state machine without ever touching a web dashboard.
What you can do with this MCP connector
Manage all e-commerce payments through your agent's conversational flow. Instead of opening up a web portal, you instruct your AI client to handle complex financial tasks—from initiating a secure checkout session using an order token, to listing every transaction in the last quarter. You can check if a payment needs capturing after authorization, or immediately issue partial refunds for returns.
The system manages payments across various states: authorizing funds, capturing them, voiding them, and refunding them all. Because this involves real money movement, data integrity is everything; that's why every tool call executes inside its own V8 isolate sandbox with 34+ security rules enforced by Vinkius, guaranteeing a tamper-proof audit trail for compliance review.
You simply connect your private API key once and gain full visibility into the payment flow.
019d7560-a1c6-7329-9341-1680d032e20a 
How Bolt MCP Works
- 1 Subscribe to this MCP and provide your Bolt Private API Key and environment (api or api-sandbox).
- 2 Connect your single AI client instance. The agent now has full access to all payment tools.
- 3 Instruct your agent to perform a task, like listing transactions or creating an order token, using natural language.
The bottom line is that you manage complex financial actions by speaking to your agent, which handles the API calls and state changes for you.
Who Is Bolt MCP For?
E-commerce operations managers, customer support leads, and developers who spend too much time clicking through merchant dashboards to solve a payment problem. If money movement is part of your job, this MCP saves hours.
Retrieves specific transaction details or order history for a customer during a call, allowing them to confirm payments and process refunds immediately.
Quickly checks merchant account status or processes mass refunds without needing developer help or manual dashboard logins.
Verifies complex API integrations, such as order token generation and webhooks monitoring, directly from a conversational prompt.
What Changes When You Connect
- Instant payment visibility: Use
list_transactionsto see recent payments right away, eliminating the need to navigate transaction logs. - Full refund control: Execute a partial or full return immediately with
refund_transaction, telling your agent exactly what amount and reference to use. - Secure checkout initiation: Generate one-time payment links using
create_order_tokenfor secure, friction-free customer checkouts. - State management confidence: If a payment was authorized but fails later, you can void it precisely with
void_transaction, preventing incorrect charges. - Deep auditing capability: By running
get_merchant_statusand checking configured webhooks vialist_webhooks, your team maintains continuous compliance visibility.
Real-World Use Cases
Handling a Failed Order
A customer calls support. Instead of manually searching, the agent asks the AI client to use get_transaction and find the specific reference ID for the disputed charge. The agent confirms the details and then uses refund_transaction to resolve it instantly.
Daily Reconciliation
The operations team needs a quick financial overview. They ask the AI client to run list_transactions, which provides all recent payments, allowing them to confirm daily sales totals without exporting CSV files.
Pre-Checkout Verification
A developer needs to verify if their API setup is correct for new clients. They instruct the agent to use get_merchant_status and check that the account is 'Active' before writing any checkout code.
Batch Voiding Payments
The team realizes a batch of payments were authorized but never captured due to a system error. They prompt the client to use void_transaction, clearing all pending funds in one go, which is faster than logging into the dashboard for each payment.
The Tradeoffs
Treating it like simple data lookup
The user only asks the agent to run get_order_details when they actually need to process a refund. They assume reading the order is enough.
→
If you need to send money back, always use refund_transaction. If you just need the customer's name and items, then get_order_details is fine.
Forgetting transaction state
The user runs a refund command without checking if the payment was first captured. The system throws an error because refunds can only happen on completed sales.
→
Always check the payment status with get_transaction before attempting to run refund_transaction. This confirms the sale is complete.
Over-relying on manual webhooks
The team assumes that because they set up webhooks, the AI agent won't need direct access. They are wrong if a payment fails outside of the webhook flow.
→
For immediate action or status checks, rely on the list_webhooks tool to verify setup, but use the transaction tools like get_transaction for real-time data.
When It Fits, When It Doesn't
Use this MCP if your workflow involves any state change that requires money to move: authorizing funds, capturing funds, refunding funds, or canceling charges. You need it when you're building automation around the payment lifecycle itself. Don't use it if you just need to read a static piece of data; for example, listing webhooks with list_webhooks is purely informational. However, if your process requires combining multiple steps—say, checking the merchant status (get_merchant_status) and then creating an order token (create_order_token)—this MCP lets your agent coordinate those calls automatically.
Common Questions About Bolt MCP
How do I check recent sales using list_transactions? +
You simply ask your agent to run list_transactions. It pulls up a formatted list of all payments processed through Bolt, letting you see the dates, amounts, and references immediately.
Can get_merchant_status tell me if I'm ready to accept payments? +
Yes. Running get_merchant_status checks your account configuration against current rules. It confirms if your publishable keys are set up correctly and if the overall merchant status is 'Active'.
What's the difference between void_transaction and refund_transaction? +
Voiding (void_transaction) cancels money that was only authorized but never captured. Refunding (refund_transaction) sends money back for a transaction that was already fully captured and settled.
Do I need to use create_order_token before capturing funds? +
Yes. For secure, one-click checkouts, you must first run create_order_token. This generates the safe link or token needed for the customer to complete the purchase, which can then be captured.
How can I use get_transaction if I need specific details on an older payment? +
You must provide a unique transaction reference ID. This tool fetches all metadata for one specific payment, going beyond what the general list of transactions shows.
What does list_webhooks do and how do I monitor my live data syncs? +
It lists every webhook URL configured on your merchant account. This is essential for auditing and ensuring that external systems receive real-time updates from Bolt.
If I authorize funds but can't capture them immediately, how do I use capture_transaction? +
You must pass the ID of the authorized transaction into this tool. It executes the final step, converting a pending authorization into actual settled funds.
When should I run get_account_details to check my credentials or setup? +
Run this first when connecting your AI agent to verify all account details are present. It confirms key information and ensures you're using the correct environment.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.