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.

Bolt MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Bolt
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Bolt through Vinkius, pass the Edge URL in the `mcps` parameter and every Bolt tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Bolt Specialist",
    goal="Help users interact with Bolt effectively",
    backstory=(
        "You are an expert at leveraging Bolt tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Bolt "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Bolt MCP Server

Connect your Bolt Merchant account to any AI agent and orchestrate your checkout and payment workflows through natural conversation.

When paired with CrewAI, Bolt becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Bolt tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Transaction Oversight — List recent Bolt transactions and retrieve detailed metadata for individual payments.
Payment Lifecycle Management — Capture authorized transactions, void pending ones, and issue full or partial refunds.
Order Token Generation — Create order tokens to initiate secure one-click checkout sessions.
Shopper Intelligence — Retrieve account details and order history for authenticated shoppers.
Webhook Monitoring — List and audit configured webhooks to ensure real-time data sync.
Merchant Health Check — Retrieve the current status and configuration of your merchant account.

The Bolt MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Bolt to CrewAI via MCP

Follow these steps to integrate the Bolt MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Bolt

Why Use CrewAI with the Bolt MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Bolt through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Bolt + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Bolt MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Bolt for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Bolt, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Bolt tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Bolt against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Bolt MCP Tools for CrewAI (10)

These 10 tools become available when you connect Bolt to CrewAI via MCP:

capture_transaction

Capture a previously authorized transaction

create_order_token

Create an order token to initiate checkout

get_account_details

Get current account details

get_merchant_status

Check the current merchant account status

get_order_details

Get details of a specific order

get_transaction

Get details of a specific transaction

list_transactions

List recent Bolt transactions

list_webhooks

List configured webhooks

refund_transaction

Issue a refund for a completed transaction

void_transaction

Void an authorized but uncaptured transaction

Example Prompts for Bolt in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Bolt immediately.

"List the last 5 transactions in my Bolt account."

"Refund $20.00 for transaction reference ABC-123."

"Check the status of my Bolt merchant account."

Troubleshooting Bolt MCP Server with CrewAI

Common issues when connecting Bolt to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Bolt + CrewAI FAQ

Common questions about integrating Bolt MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.