# How to integrate Bitquery MCP with Mastra AI ```json { "title": "How to integrate Bitquery MCP with Mastra AI", "toolkit": "Bitquery", "toolkit_slug": "bitquery", "framework": "Mastra AI", "framework_slug": "mastra-ai", "url": "https://composio.dev/toolkits/bitquery/framework/mastra-ai", "markdown_url": "https://composio.dev/toolkits/bitquery/framework/mastra-ai.md", "updated_at": "2026-05-12T10:03:11.370Z" } ``` ## Introduction This guide walks you through connecting Bitquery to Mastra AI using the Composio tool router. By the end, you'll have a working Bitquery agent that can show real-time ethereum mempool transactions, count unique wallet addresses for solana, query historical bitcoin transactions from 2021 through natural language commands. This guide will help you understand how to give your Mastra AI agent real control over a Bitquery account through Composio's Bitquery MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Bitquery with - [OpenAI Agents SDK](https://composio.dev/toolkits/bitquery/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/bitquery/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/bitquery/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/bitquery/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/bitquery/framework/codex) - [OpenClaw](https://composio.dev/toolkits/bitquery/framework/openclaw) - [Hermes](https://composio.dev/toolkits/bitquery/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/bitquery/framework/cli) - [Google ADK](https://composio.dev/toolkits/bitquery/framework/google-adk) - [LangChain](https://composio.dev/toolkits/bitquery/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/bitquery/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/bitquery/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/bitquery/framework/crew-ai) ## TL;DR Here's what you'll learn: - Set up your environment so Mastra, OpenAI, and Composio work together - Create a Tool Router session in Composio that exposes Bitquery tools - Connect Mastra's MCP client to the Composio generated MCP URL - Fetch Bitquery tool definitions and attach them as a toolset - Build a Mastra agent that can reason, call tools, and return structured results - Run an interactive CLI where you can chat with your Bitquery agent ## What is Mastra AI? Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP. Key features include: - MCP Client: Built-in support for Model Context Protocol servers - Toolsets: Organize tools into logical groups - Step Callbacks: Monitor and debug agent execution - OpenAI Integration: Works with OpenAI models via @ai-sdk/openai ## What is the Bitquery MCP server, and what's possible with it? The Bitquery MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Bitquery account. It provides structured and secure access to blockchain datasets and real-time analytics, so your agent can perform actions like querying historical transactions, streaming mempool activity, selecting blockchain networks, and aggregating metrics across 40+ supported chains. - Seamless blockchain data querying: Let your agent run powerful queries on historical or real-time blockchain data across multiple networks using Bitquery's combined or archive databases. - Live mempool monitoring: Subscribe and stream pending transactions from EVM-compatible chains in real time, enabling instant insights into network activity as it happens. - On-demand network and database selection: Have your agent dynamically select blockchain networks and datasets—like Ethereum, BNB Chain, or others—to tailor queries for your specific use case. - Metric aggregation and analysis: Automate the aggregation of transaction counts, unique values, or conditional metrics, empowering your agent to analyze blockchain trends without manual intervention. - Advanced GraphQL customization: Use aliases and conditional snippets to refine data responses, ensuring clarity and precise control in complex blockchain analytics workflows. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `BITQUERY_ARCHIVE_DATABASE_QUERY` | Archive Database Query | Query the Bitquery Archive Database (V1 API) for historical blockchain data. The Archive Database provides complete historical blockchain data across 40+ blockchains including Bitcoin, Ethereum, BSC, Solana, and more. Data has a delay of tens of minutes to hours from real-time. For near-real-time data, use the Realtime Database Query instead. The V1 API uses blockchain-specific root types (bitcoin, ethereum, etc.) with fields like blocks, transactions, transfers, and trades. Queries support filtering, pagination with limit/offset, and sorting with orderBy. Example queries: - Bitcoin blocks: { bitcoin { blocks(limit: 5, orderBy: {descending: height}) { height } } } - Ethereum transactions: { ethereum { transactions(limit: 10) { hash value } } } | | `BITQUERY_COMBINED_DATABASE_QUERY` | Combined Database Query | Query Bitquery's Combined Database (v2 API) for blockchain data across 40+ networks. Use this tool to fetch real-time and historical blockchain data including: - Blocks, transactions, and events - Token transfers and balances - DEX trades and liquidity data - Smart contract interactions - NFT data and metadata Supported networks include: Ethereum (eth), BSC (bsc), Polygon (matic), Solana, Tron, and more. The v2 API uses a different schema than v1 - use EVM(network: eth) instead of ethereum root field. | | `BITQUERY_CONDITIONAL_METRICS` | Conditional Metrics Snippet | Generate a Bitquery GraphQL metric snippet with conditional logic using the 'if:' attribute. This tool builds metric aggregation snippets (count, sum, avg, min, max) that can be embedded in Bitquery GraphQL queries. The 'if:' filter allows applying conditions directly to metric calculations, enabling conditional aggregation like counting only successful transactions. Output format examples: - count(if: {Block: {GasUsed: {gt: "0"}}}) - sum(of: Block_GasUsed if: {Block: {Time: {after: "2024-01-01"}}}) - myAlias: avg(of: Transaction_Value if: {Transaction: {Success: true}}) | | `BITQUERY_DATABASE_SELECTION` | Database Selection | Tool to select the database (archive, realtime, combined) to query at the top level of a GraphQL request. Use after determining whether you need live, historical, or combined blockchain data. | | `BITQUERY_EARLY_ACCESS_PROGRAM_QUERY` | Early Access Program Query | Execute GraphQL queries against the Bitquery Early Access Program (EAP) Streaming API. This tool queries the EAP endpoint (streaming.bitquery.io/eap) for real-time blockchain data. The EAP provides access to streaming data across various blockchain networks including Solana, EVM chains (Ethereum, Polygon, etc.), and others for evaluation purposes. Key features: - Real-time blockchain data with minimal latency - Supports both queries and subscriptions - Networks: Solana, Ethereum, Polygon (Matic), and other EVM-compatible chains Note: EAP is limited to real-time data only. For historical data, use the Archive Database Query. Existing users can continue using EAP; new users should prefer the V2 endpoint for most use cases. Example queries: - Get latest ETH blocks: { EVM(network: eth) { Blocks(limit: {count: 5}) { Block { Number Time } } } } - Solana DEX trades: subscription { Solana { DEXTrades { Block { Time } Trade { Price } } } } | | `BITQUERY_NETWORK_SELECTION` | Network Selection | Tool to select the blockchain network for GraphQL queries. Use before constructing dataset or metric queries to ensure the correct chain is targeted. | | `BITQUERY_OPTIONS_QUERY` | Options Query | Tool to fetch GraphQL dataset options via schema introspection. Use when you need to discover root-level query fields and their arguments before building queries. Dataset and token availability varies by Bitquery environment; verify available fields here before constructing complex queries that depend on specific datasets. | | `BITQUERY_PRICE_ASYMMETRY_METRIC` | Price Asymmetry Metric | Tool to generate GraphQL PriceAsymmetry filter snippet. Use when you need to filter trades based on price asymmetry metric. | | `BITQUERY_REALTIME_DATABASE_QUERY` | Realtime Database Query | Query the Bitquery Streaming (V2) API for realtime blockchain data. This tool accesses the Bitquery Streaming API at streaming.bitquery.io/graphql which provides real-time blockchain data with minimal latency. Use this for recent data (within minutes). For historical data, use the Archive Database Query. Supported query formats: - V2 EVM queries: { EVM(network: eth) { Blocks(limit: {count: 5}) { Block { Number Time } } } } - V2 Bitcoin queries: { bitcoin(network: bitcoin) { blocks(limit: {count: 5}) { height timestamp { time } } } } Note: Requires an active Bitquery subscription for streaming API access. | | `BITQUERY_SELECT_BY_METRIC` | Select By Metric | Tool to generate a GraphQL metric snippet filtering by its value using selectWhere. Use when you need to include only metrics meeting specific value conditions (e.g., only positive sums). | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Bitquery MCP server is an implementation of the Model Context Protocol that connects your AI agent to Bitquery. It provides structured and secure access so your agent can perform Bitquery operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before starting, make sure you have: - Node.js 18 or higher - A Composio account with an active API key - An OpenAI API key - Basic familiarity with TypeScript ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. - You need credits or a connected billing setup to use the models. - Store the key somewhere safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Go to Settings and copy your API key. - This key lets your Mastra agent talk to Composio and reach Bitquery through MCP. ### 2. Install dependencies Install the required packages. What's happening: - @composio/core is the Composio SDK for creating MCP sessions - @mastra/core provides the Agent class - @mastra/mcp is Mastra's MCP client - @ai-sdk/openai is the model wrapper for OpenAI - dotenv loads environment variables from .env ```bash npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's happening: - COMPOSIO_API_KEY authenticates your requests to Composio - COMPOSIO_USER_ID tells Composio which user this session belongs to - OPENAI_API_KEY lets the Mastra agent call OpenAI models ```bash COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here OPENAI_API_KEY=your_openai_api_key_here ``` ### 4. Import libraries and validate environment What's happening: - dotenv/config auto loads your .env so process.env.* is available - openai gives you a Mastra compatible model wrapper - Agent is the Mastra agent that will call tools and produce answers - MCPClient connects Mastra to your Composio MCP server - Composio is used to create a Tool Router session ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Agent } from "@mastra/core/agent"; import { MCPClient } from "@mastra/mcp"; import { Composio } from "@composio/core"; import * as readline from "readline"; import type { AiMessageType } from "@mastra/core/agent"; const openaiAPIKey = process.env.OPENAI_API_KEY; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey as string, }); ``` ### 5. Create a Tool Router session for Bitquery What's happening: - create spins up a short-lived MCP HTTP endpoint for this user - The toolkits array contains "bitquery" for Bitquery access - session.mcp.url is the MCP URL that Mastra's MCPClient will connect to ```typescript async function main() { const session = await composio.create( composioUserID as string, { toolkits: ["bitquery"], }, ); const composioMCPUrl = session.mcp.url; console.log("Bitquery MCP URL:", composioMCPUrl); ``` ### 6. Configure Mastra MCP client and fetch tools What's happening: - MCPClient takes an id for this client and a list of MCP servers - The headers property includes the x-api-key for authentication - getTools fetches the tool definitions exposed by the Bitquery toolkit ```typescript const mcpClient = new MCPClient({ id: composioUserID as string, servers: { nasdaq: { url: new URL(composioMCPUrl), requestInit: { headers: session.mcp.headers, }, }, }, timeout: 30_000, }); console.log("Fetching MCP tools from Composio..."); const composioTools = await mcpClient.getTools(); console.log("Number of tools:", Object.keys(composioTools).length); ``` ### 7. Create the Mastra agent What's happening: - Agent is the core Mastra agent - name is just an identifier for logging and debugging - instructions guide the agent to use tools instead of only answering in natural language - model uses openai("gpt-5") to configure the underlying LLM ```typescript const agent = new Agent({ name: "bitquery-mastra-agent", instructions: "You are an AI agent with Bitquery tools via Composio.", model: "openai/gpt-5", }); ``` ### 8. Set up interactive chat interface What's happening: - messages keeps the full conversation history in Mastra's expected format - agent.generate runs the agent with conversation history and Bitquery toolsets - maxSteps limits how many tool calls the agent can take in a single run - onStepFinish is a hook that prints intermediate steps for debugging ```typescript let messages: AiMessageType[] = []; console.log("Chat started! Type 'exit' or 'quit' to end.\n"); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); rl.on("line", async (userInput: string) => { const trimmedInput = userInput.trim(); if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } messages.push({ id: crypto.randomUUID(), role: "user", content: trimmedInput, }); console.log("\nAgent is thinking...\n"); try { const response = await agent.generate(messages, { toolsets: { bitquery: composioTools, }, maxSteps: 8, }); const { text } = response; if (text && text.trim().length > 0) { console.log(`Agent: ${text}\n`); messages.push({ id: crypto.randomUUID(), role: "assistant", content: text, }); } } catch (error) { console.error("\nError:", error); } rl.prompt(); }); rl.on("close", async () => { console.log("\nSession ended."); await mcpClient.disconnect(); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Complete Code ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Agent } from "@mastra/core/agent"; import { MCPClient } from "@mastra/mcp"; import { Composio } from "@composio/core"; import * as readline from "readline"; import type { AiMessageType } from "@mastra/core/agent"; const openaiAPIKey = process.env.OPENAI_API_KEY; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey as string }); async function main() { const session = await composio.create(composioUserID as string, { toolkits: ["bitquery"], }); const composioMCPUrl = session.mcp.url; const mcpClient = new MCPClient({ id: composioUserID as string, servers: { bitquery: { url: new URL(composioMCPUrl), requestInit: { headers: session.mcp.headers, }, }, }, timeout: 30_000, }); const composioTools = await mcpClient.getTools(); const agent = new Agent({ name: "bitquery-mastra-agent", instructions: "You are an AI agent with Bitquery tools via Composio.", model: "openai/gpt-5", }); let messages: AiMessageType[] = []; const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); rl.on("line", async (input: string) => { const trimmed = input.trim(); if (["exit", "quit"].includes(trimmed.toLowerCase())) { rl.close(); return; } messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed }); const { text } = await agent.generate(messages, { toolsets: { bitquery: composioTools }, maxSteps: 8, }); if (text) { console.log(`Agent: ${text}\n`); messages.push({ id: crypto.randomUUID(), role: "assistant", content: text }); } rl.prompt(); }); rl.on("close", async () => { await mcpClient.disconnect(); process.exit(0); }); } main(); ``` ## Conclusion You've built a Mastra AI agent that can interact with Bitquery through Composio's Tool Router. You can extend this further by: - Adding other toolkits like Gmail, Slack, or GitHub - Building a web-based chat interface around this agent - Using multiple MCP endpoints to enable cross-app workflows ## How to build Bitquery MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/bitquery/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/bitquery/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/bitquery/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/bitquery/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/bitquery/framework/codex) - [OpenClaw](https://composio.dev/toolkits/bitquery/framework/openclaw) - [Hermes](https://composio.dev/toolkits/bitquery/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/bitquery/framework/cli) - [Google ADK](https://composio.dev/toolkits/bitquery/framework/google-adk) - [LangChain](https://composio.dev/toolkits/bitquery/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/bitquery/framework/ai-sdk) - [LlamaIndex](https://composio.dev/toolkits/bitquery/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/bitquery/framework/crew-ai) ## Related Toolkits - [Excel](https://composio.dev/toolkits/excel) - Microsoft Excel is a robust spreadsheet application for organizing, analyzing, and visualizing data. It's the go-to tool for calculations, reporting, and flexible data management. - [21risk](https://composio.dev/toolkits/_21risk) - 21RISK is a web app built for easy checklist, audit, and compliance management. It streamlines risk processes so teams can focus on what matters. - [Abstract](https://composio.dev/toolkits/abstract) - Abstract provides a suite of APIs for automating data validation and enrichment tasks. It helps developers streamline workflows and ensure data quality with minimal effort. - [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time. - [Agentql](https://composio.dev/toolkits/agentql) - Agentql is a toolkit that connects AI agents to the web using a specialized query language. It enables structured web interaction and data extraction for smarter automations. - [Agenty](https://composio.dev/toolkits/agenty) - Agenty is a web scraping and automation platform for extracting data and automating browser tasks—no coding needed. It streamlines data collection, monitoring, and repetitive online actions. - [Ambee](https://composio.dev/toolkits/ambee) - Ambee is an environmental data platform providing real-time, hyperlocal APIs for air quality, weather, and pollen. Get precise environmental insights to power smarter decisions in your apps and workflows. - [Ambient weather](https://composio.dev/toolkits/ambient_weather) - Ambient Weather is a platform for personal weather stations with a robust API for accessing local, real-time, and historical weather data. Get detailed environmental insights directly from your own sensors for smarter apps and automations. - [Anonyflow](https://composio.dev/toolkits/anonyflow) - Anonyflow is a service for encryption-based data anonymization and secure data sharing. It helps organizations meet GDPR, CCPA, and HIPAA data privacy compliance requirements. - [Api ninjas](https://composio.dev/toolkits/api_ninjas) - Api ninjas offers 120+ public APIs spanning categories like weather, finance, sports, and more. Developers use it to supercharge apps with real-time data and actionable endpoints. - [Api sports](https://composio.dev/toolkits/api_sports) - Api sports is a comprehensive sports data platform covering 2,000+ competitions with live scores and 15+ years of stats. Instantly access up-to-date sports information for analysis, apps, or chatbots. - [Apify](https://composio.dev/toolkits/apify) - Apify is a cloud platform for building, deploying, and managing web scraping and automation tools called Actors. It lets you automate data extraction and workflow tasks at scale—no infrastructure headaches. - [Autom](https://composio.dev/toolkits/autom) - Autom is a lightning-fast search engine results data platform for Google, Bing, and Brave. Developers use it to access fresh, low-latency SERP data on demand. - [Beaconchain](https://composio.dev/toolkits/beaconchain) - Beaconchain is a real-time analytics platform for Ethereum 2.0's Beacon Chain. It provides detailed insights into validators, blocks, and overall network performance. - [Big data cloud](https://composio.dev/toolkits/big_data_cloud) - BigDataCloud provides APIs for geolocation, reverse geocoding, and address validation. Instantly access reliable location intelligence to enhance your applications and workflows. - [Bigpicture io](https://composio.dev/toolkits/bigpicture_io) - BigPicture.io offers APIs for accessing detailed company and profile data. Instantly enrich your applications with up-to-date insights on 20M+ businesses. - [Brightdata](https://composio.dev/toolkits/brightdata) - Brightdata is a leading web data platform offering advanced scraping, SERP APIs, and anti-bot tools. It lets you collect public web data at scale, bypassing blocks and friction. - [Builtwith](https://composio.dev/toolkits/builtwith) - BuiltWith is a web technology profiler that uncovers the technologies powering any website. Gain actionable insights into analytics, hosting, and content management stacks for smarter research and lead generation. - [Byteforms](https://composio.dev/toolkits/byteforms) - Byteforms is an all-in-one platform for creating forms, managing submissions, and integrating data. It streamlines workflows by centralizing form data collection and automation. - [Cabinpanda](https://composio.dev/toolkits/cabinpanda) - Cabinpanda is a data collection platform for building and managing online forms. It helps streamline how you gather, organize, and analyze responses. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Bitquery MCP? With a standalone Bitquery MCP server, the agents and LLMs can only access a fixed set of Bitquery tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Bitquery and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Mastra AI? Yes, you can. Mastra AI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Bitquery tools. ### Can I manage the permissions and scopes for Bitquery while using Tool Router? Yes, absolutely. You can configure which Bitquery scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do. ### How safe is my data with Composio Tool Router? All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Bitquery data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)