4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Fireblocks MCP Server

Bring Digital Assets
to CrewAI

Learn how to connect Fireblocks to CrewAI and start using 40 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Add Asset To WalletAdd ContractCancel TransactionCreate External WalletCreate Internal WalletCreate TransactionCreate Vault AccountCreate Vault Account AssetCreate Vault Account Asset AddressCreate WebhookDrop TransactionEstimate FeeEstimate Network FeeGet Contract AssetGet Gas StationGet Public Key InfoGet Screening TransactionGet TransactionGet Vault AccountGet Vault Account AssetList AssetsList BlockchainsList ContractsList External WalletsList Internal WalletsList Owned NftsList Staking ChainsList Staking PositionsList TransactionsList VaspsList Vault Account Asset AddressesList Vault AccountsList Webhook NotificationsRefresh NftsRegister AssetResend WebhooksStake PositionUpdate Gas StationUpdate Vault AccountValidate Travel Rule

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Fireblocks

What is the Fireblocks MCP Server?

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

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.

How it works

  1. Subscribe to this server
  2. Enter your Fireblocks API Key and Private Key
  3. Start managing your digital asset infrastructure from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Treasury Managers — instantly check balances across hundreds of vaults and initiate transfers without manual dashboard navigation.
  • DevOps Engineers — automate the creation of vault accounts and deposit addresses during deployment workflows.
  • Compliance Officers — quickly retrieve screening results and validate travel rule data for specific transactions.

Built-in capabilities (40)

add_asset_to_wallet

Add an asset/address to a wallet

add_contract

Add a new contract to the whitelist

cancel_transaction

Cancel a pending transaction

create_external_wallet

Create a new external wallet container

create_internal_wallet

Create a new internal wallet container

create_transaction

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

create_vault_account

Create a new vault account

create_vault_account_asset

Create a new wallet for an asset in a vault

create_vault_account_asset_address

Generate a new deposit address

create_webhook

Create a new webhook subscription

drop_transaction

Drop an ETH/EVM transaction

estimate_fee

Estimate fees for a potential transaction

estimate_network_fee

Get current network fee estimates for an asset

get_contract_asset

Get details for a contract asset

get_gas_station

Retrieve gas station settings

get_public_key_info

Get the public key for a specific derivation path

get_screening_transaction

Get compliance screening results for a transaction

get_transaction

Get details of a specific transaction

get_vault_account

Retrieve details for a specific vault account

get_vault_account_asset

Get balance for a specific asset in a vault

list_assets

List all supported assets

list_blockchains

List all supported blockchains

list_contracts

List whitelisted contracts

list_external_wallets

List all external wallets

list_internal_wallets

List all internal wallets

list_owned_nfts

List all owned NFT tokens

list_staking_chains

List supported staking chains

list_staking_positions

List active staking positions

list_transactions

Retrieve transaction history with filters

list_vasps

List Virtual Asset Service Providers (VASPs)

list_vault_account_asset_addresses

List deposit addresses for an asset

list_vault_accounts

List vault accounts with pagination

list_webhook_notifications

List notifications sent to a webhook

refresh_nfts

Refresh NFT data for a vault account

register_asset

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

resend_webhooks

Resend failed webhooks

stake_position

Initiate a staking position

update_gas_station

Update auto-fueling thresholds

update_vault_account

Rename a vault account

validate_travel_rule

Validate a transaction against Travel Rule requirements

Why CrewAI?

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.

  • 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

See it in action

Fireblocks in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Fireblocks and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Fireblocks to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Fireblocks in CrewAI

The Fireblocks 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. All 40 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

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

The Vinkius Advantage

How Vinkius secures Fireblocks for CrewAI

Every tool call from CrewAI to the Fireblocks MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I check the balance of a specific asset in a vault account?

Yes. Use the get_vault_account_asset tool by providing the Vault Account ID and the Asset ID. The agent will return the available, total, and pending balances.

02

How do I estimate transaction fees before sending funds?

You can use the estimate_fee tool. Provide the transaction details, and the agent will return the estimated network fees for different priority levels.

03

Is it possible to list all supported blockchains in my workspace?

Yes, the list_blockchains tool retrieves a comprehensive list of all blockchain networks currently supported and configured in your Fireblocks environment.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

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

10

Agent not using tools

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

11

Timeout errors

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

12

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.

Explore More MCP Servers

View all →