How to integrate Bitquery MCP with Hermes

Bitquery logo
Hermes logo
divider

Introduction

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows.

This guide explains the easiest and most robust way to connect your Bitquery account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.

Also integrate Bitquery with

What is Composio Connect?

Composio Connect is a consumer offering that lets anyone plug 1,000+ applications directly into their agent harness — including Hermes. It can:

  • Search and load tools from relevant toolkits on-demand, reducing context usage.
  • Chain multiple tools to accomplish complex workflows via a remote workbench, without excessive back-and-forth with the LLM.
  • Manage app authentication end-to-end with zero manual overhead.

Integrating Bitquery with Hermes

Using Composio Connect CLI

1. Install the Composio CLI

Run the install script directly, or paste https://composio.dev/hermes into your Hermes chat box to have it installed for you.

bash
curl -fsSL https://composio.dev/install | bash
Hermes authenticating with Composio

2. Authenticate

Once the CLI is installed, ask Hermes to authenticate with Composio.

3. Connect to Bitquery

Ask your agent to connect to Bitquery, or simply request any Bitquery-related task. Hermes will prompt you to authenticate and authorize access.

4. Done. You're all set with a new Bitquery connection.


Using Composio Connect MCP

1. Get your MCP URL and API Key

Go to dashboard.composio.dev and copy your Connect MCP URL and API key.

Copy MCP URL and API key from Composio dashboard

2. Open the Hermes config file

bash
nano ~/.hermes/config.yaml

3. Add the Composio Connect MCP server

bash
mcp_servers:
  composio:
    url: "https://connect.composio.dev/mcp"
    headers:
      x-consumer-api-key: "YOUR_COMPOSIO_API_KEY"
    connect_timeout: 60
    timeout: 180

Save with Ctrl + O, Enter, then exit with Ctrl + X.

4. Restart your Hermes agent

Once restarted, ask your agent to connect to Bitquery or request any Bitquery-related task. It will prompt you to authenticate and authorize access.

5. Done!

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 & Triggers

Tools
Aliases MetricTool to use graphql aliases to rename fields in the response for clarity and disambiguation.
Archive Database QueryTool to query the archive database.
Combined Database QueryTool to query the combined database, which merges archive and real-time databases.
Conditional Metrics SnippetTool to generate a graphql metric snippet with conditional logic.
Count Distinct MetricTool to use the count distinct metric to aggregate unique values for a field.
Count MetricTool to use the count metric to aggregate the number of records matching a graphql query.
Database SelectionTool to select the database (archive, realtime, combined) to query at the top level of a graphql request.
Early Access Program QueryTool to access streaming data across various blockchain networks for evaluation purposes.
Mempool SubscriptionTool to subscribe to real-time mempool updates for evm chains (ethereum, bnb, etc.
Network SelectionTool to select the blockchain network for graphql queries.
Options QueryTool to fetch graphql dataset options via schema introspection.
Price Asymmetry MetricTool to generate graphql priceasymmetry filter snippet.
Quantile MetricTool to calculate quantiles to understand the distribution of numerical data.
Realtime Database QueryRealtime database query
Select By MetricTool to generate a graphql metric snippet filtering by its value using selectwhere.
Statistics MetricTool to compute statistical metrics (mean, median, etc.
Sum MetricTool to calculate the sum of a specified field's values across defined dimensions.
Uniq MetricTool to estimate the count of unique values using the uniq metric.

Way Forward

With Bitquery connected, Hermes can now act on your behalf whenever it detects a relevant task or you ask it to.

From here, you can extend Hermes further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup. Each new integration compounds what Hermes can do for you.
  • Build workflows across tools: Once multiple apps are connected, Hermes can chain actions together — turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Let it learn your patterns: The more you use Hermes, the better it gets at anticipating how you'd handle recurring tasks. Give it feedback on drafts and decisions, and it will adapt.

If you run into trouble or want to share what you've built, join the community or check out the Docs for deeper configuration options.

How to build Bitquery MCP Agent with another framework

FAQ

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 Hermes?

Yes, you can. Hermes 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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.