4,000+ servers built on vurb.ts
Vinkius

Fireblocks MCP Server for CrewAIGive CrewAI instant access to 40 tools to Add Asset To Wallet, Add Contract, Cancel Transaction, and more

MCP Inspector GDPR Free for Subscribers

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

Ask AI about this MCP Server for CrewAI

The Fireblocks MCP Server for CrewAI is a standout in the Money Moves category — giving your AI agent 40 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Fireblocks Specialist",
    goal="Help users interact with Fireblocks effectively",
    backstory=(
        "You are an expert at leveraging Fireblocks 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 Fireblocks "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 40 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Fireblocks
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 Fireblocks MCP Server

Connect your Fireblocks workspace to any AI agent to orchestrate institutional-grade digital asset operations through natural language conversation.

When paired with CrewAI, Fireblocks becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Fireblocks 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

  • Vault Management — List, create, and inspect vault accounts and asset balances across your entire organization.
  • Transaction Orchestration — Create, estimate fees, and monitor transactions across multiple blockchains with full lifecycle control.
  • Wallet Connectivity — Manage internal and external wallets, and generate new deposit addresses for various assets.
  • Advanced Asset Support — Interact with NFTs, staking positions, and smart contracts directly from the console.
  • Compliance & Security — Validate travel rules, manage gas station settings, and retrieve screening information for transactions.

The Fireblocks MCP Server exposes 40 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 40 Fireblocks tools available for CrewAI

When CrewAI connects to Fireblocks through Vinkius, your AI agent gets direct access to every tool listed below — spanning digital-assets, vault-management, crypto-transactions, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

add

Add asset to wallet on Fireblocks

Add an asset/address to a wallet

add

Add contract on Fireblocks

Add a new contract to the whitelist

cancel

Cancel transaction on Fireblocks

Cancel a pending transaction

create

Create external wallet on Fireblocks

Create a new external wallet container

create

Create internal wallet on Fireblocks

Create a new internal wallet container

create

Create transaction on Fireblocks

Create a new transaction (Transfer, Mint, Burn, etc.)

create

Create vault account on Fireblocks

Create a new vault account

create

Create vault account asset on Fireblocks

Create a new wallet for an asset in a vault

create

Create vault account asset address on Fireblocks

Generate a new deposit address

create

Create webhook on Fireblocks

Create a new webhook subscription

drop

Drop transaction on Fireblocks

Drop an ETH/EVM transaction

estimate

Estimate fee on Fireblocks

Estimate fees for a potential transaction

estimate

Estimate network fee on Fireblocks

Get current network fee estimates for an asset

get

Get contract asset on Fireblocks

Get details for a contract asset

get

Get gas station on Fireblocks

Retrieve gas station settings

get

Get public key info on Fireblocks

Get the public key for a specific derivation path

get

Get screening transaction on Fireblocks

Get compliance screening results for a transaction

get

Get transaction on Fireblocks

Get details of a specific transaction

get

Get vault account on Fireblocks

Retrieve details for a specific vault account

get

Get vault account asset on Fireblocks

Get balance for a specific asset in a vault

list

List assets on Fireblocks

List all supported assets

list

List blockchains on Fireblocks

List all supported blockchains

list

List contracts on Fireblocks

List whitelisted contracts

list

List external wallets on Fireblocks

List all external wallets

list

List internal wallets on Fireblocks

List all internal wallets

list

List owned nfts on Fireblocks

List all owned NFT tokens

list

List staking chains on Fireblocks

List supported staking chains

list

List staking positions on Fireblocks

List active staking positions

list

List transactions on Fireblocks

Retrieve transaction history with filters

list

List vasps on Fireblocks

List Virtual Asset Service Providers (VASPs)

list

List vault account asset addresses on Fireblocks

List deposit addresses for an asset

list

List vault accounts on Fireblocks

List vault accounts with pagination

list

List webhook notifications on Fireblocks

List notifications sent to a webhook

refresh

Refresh nfts on Fireblocks

Refresh NFT data for a vault account

register

Register asset on Fireblocks

Register a custom asset (e.g., ERC-20)

resend

Resend webhooks on Fireblocks

Resend failed webhooks

stake

Stake position on Fireblocks

Initiate a staking position

update

Update gas station on Fireblocks

Update auto-fueling thresholds

update

Update vault account on Fireblocks

Rename a vault account

validate

Validate travel rule on Fireblocks

Validate a transaction against Travel Rule requirements

Connect Fireblocks to CrewAI via MCP

Follow these steps to wire Fireblocks into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

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

Customize the agent

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

Run the crew

Run python crew.py. CrewAI auto-discovers 40 tools from Fireblocks

Why Use CrewAI with the Fireblocks MCP Server

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

01

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

02

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

03

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

04

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

Fireblocks + CrewAI Use Cases

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

01

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

02

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

03

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

04

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

Example Prompts for Fireblocks in CrewAI

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

01

"List the first 10 vault accounts in my Fireblocks workspace."

02

"What is the BTC balance in vault account ID 0?"

03

"Create a transaction to send 0.1 ETH from vault 0 to external wallet 'Exchange-Wallet'."

Troubleshooting Fireblocks MCP Server with CrewAI

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

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

Fireblocks + CrewAI FAQ

Common questions about integrating Fireblocks MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Explore More MCP Servers

View all →