How to Use the Fireblocks MCP in LlamaIndex

Q: How does LlamaIndex store the transaction history retrieved from the Fireblocks MCP server?

LlamaIndex takes the JSON payloads from Fireblocks listtransactions and converts them into document nodes. These nodes are then embedded and stored in your vector database for fast semantic retrieval.

Q: Can a LlamaIndex agent update Fireblocks vault names in my vector store?

Yes. When the LlamaIndex agent executes updatevaultaccount, it triggers an index refresh to ensure your local vector database matches the updated Fireblocks vault name instantly.

Q: How are my Fireblocks deposit addresses secured within LlamaIndex?

Fireblocks deposit addresses retrieved from listvaultaccountassetaddresses are stored only in your local LlamaIndex vector index. No raw private keys are ever exposed, as the Fireblocks MCP server only retrieves public address strings and metadata.

Index your on-chain balances and transaction history directly into LlamaIndex using this Fireblocks MCP server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Fireblocks MCP to LlamaIndex

Create your Vinkius account to connect Fireblocks to LlamaIndex and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Fireblocks with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Semantic search over transaction history

Turn your raw Fireblocks transaction logs retrieved via `list_transactions` into a searchable LlamaIndex knowledge base. Instead of writing complex SQL queries to find a specific Fireblocks transfer, ask your LlamaIndex agent when a payment went through.

Context-aware treasury queries with MCP Server tools

Ground your LlamaIndex agent's financial decisions in actual live Fireblocks vault data pulled from `list_vault_accounts` rather than static training information. When you ask LlamaIndex for a portfolio update, the system queries your vector index for historical balances and updates it with a live Fireblocks call to `get_vault_account_asset`.

Indexing whitelists and contract configurations

Keep your compliance data organized and searchable by indexing whitelisted addresses from `list_contracts` directly into LlamaIndex. If you need to check if an address is authorized, the LlamaIndex agent cross-references the vector index before querying Fireblocks with `get_contract_asset`.

Setup guide

Set up Fireblocks MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Fireblocks MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Fireblocks tools.",
)
response = await agent.run("List recent Fireblocks data")

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Fireblocks. 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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Fireblocks now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Fireblocks MCP in LlamaIndex

LlamaIndex takes the JSON payloads from Fireblocks `list_transactions` and converts them into document nodes. These nodes are then embedded and stored in your vector database for fast semantic retrieval.

Yes. The LlamaIndex agent can fetch historical Fireblocks gas data via `get_gas_station` and index it alongside live network fee estimates from `estimate_network_fee` to help you analyze fee trends over time.

You configure the LlamaIndex agent to run a live lookup. The agent first searches the index for the Fireblocks vault ID, then executes `get_vault_account_asset` to retrieve the active, real-time balance.

Yes. When the LlamaIndex agent executes `update_vault_account`, it triggers an index refresh to ensure your local vector database matches the updated Fireblocks vault name instantly.

Fireblocks deposit addresses retrieved from `list_vault_account_asset_addresses` are stored only in your local LlamaIndex vector index. No raw private keys are ever exposed, as the Fireblocks MCP server only retrieves public address strings and metadata.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript