How to integrate Beaconchain MCP with Google ADK

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Beaconchain logo
Google ADK logo
divider

Introduction

This guide walks you through connecting Beaconchain to Google ADK using the Composio tool router. By the end, you'll have a working Beaconchain agent that can check if your ethereum node is syncing, get health status of the beacon chain node, fetch details for validator id 12345 through natural language commands.

This guide will help you understand how to give your Google ADK agent real control over a Beaconchain account through Composio's Beaconchain MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Beaconchain with

TL;DR

Here's what you'll learn:
  • Get a Beaconchain account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Beaconchain
  • Build an agent that connects to Beaconchain through MCP
  • Interact with Beaconchain using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

What is the Beaconchain MCP server, and what's possible with it?

The Beaconchain MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Beaconchain account. It provides structured and secure access to Ethereum 2.0 Beacon Chain analytics, so your agent can check validator status, monitor node health, analyze network performance, and surface real-time blockchain insights on your behalf.

  • Validator information lookup: Instantly retrieve in-depth details about any specific Ethereum 2.0 validator, including performance, status, and rewards.
  • Node health monitoring: Let your agent check the real-time health status of your node, including readiness, syncing state, and error conditions.
  • Network performance insights: Surface up-to-date statistics on the overall Beacon Chain network, empowering you to make informed decisions.
  • Automated health alerts: Have your agent proactively monitor node status and notify you if any issues or anomalies arise.

Supported Tools & Triggers

Tools
Get ChartRetrieve chart visualizations from beaconcha.
Get EpochRetrieve aggregate metrics and status for a beacon chain epoch.
Get ETH1 Deposits by Transaction HashRetrieve all beacon chain validator deposit events associated with a specific execution-layer transaction hash.
Get ETH.Store Daily AggregatesRetrieve ETH.
Get ERC-20 Token BalancesRetrieve a paginated list of ERC-20 token balances for a specific Ethereum address.
Get Execution BlockRetrieve one or more execution-layer blocks by block number from the Ethereum Beacon Chain.
Get Execution Produced BlocksRetrieve execution-layer blocks attributed to one or more producers.
Get Latest StateRetrieve the latest known Ethereum Beacon Chain network state.
Get Network PerformanceRetrieve aggregated network performance metrics for the Ethereum Beacon Chain.
Get Explorer HealthCheck the health status of the beaconcha.
Get Validator QueuesRetrieve current queue metrics for Ethereum Beacon Chain validators.
Get Rocket Pool ValidatorRetrieve Rocket Pool-specific metadata for validators including minipool status, node fee, smoothing pool status, and RPL stake metrics.
Get SlotRetrieve detailed information about an Ethereum Beacon Chain slot.
Get Slot AttestationsRetrieve all attestations included in the beacon block for a specific slot.
Get Slot Attester SlashingsRetrieve all attester slashing operations included in the beacon block for a specific slot.
Get Slot Proposer SlashingsRetrieve all proposer slashing operations included in the beacon block for a specific slot.
Get Slot Voluntary ExitsRetrieve all voluntary exit operations included in the beacon block for a specific slot.
Get Sync CommitteeRetrieve the sync committee membership for a given sync period.
Get ValidatorRetrieve detailed information about an Ethereum Beacon Chain validator.
Get Validator Attestation EfficiencyRetrieve normalized attestation inclusion effectiveness for one or more validators.
Get Validator AttestationsRetrieve attestations observed for one or more validators within a bounded epoch window.
Get Validator Balance HistoryRetrieve per-epoch balance history for one or more Ethereum Beacon Chain validators.
Get Validator BLS ChangesRetrieve on-chain BLS-to-execution credential change messages (EIP-4881) for validators.
Get Validator Consensus RewardsRetrieve consensus-layer rewards for one or more validators over multiple lookback windows.
Get Validator Daily StatsRetrieve per-day statistics for a single Ethereum Beacon Chain validator by index.
Get Validator DepositsRetrieve execution-layer deposit events for one or more validators.
Get Validator Execution RewardsRetrieve execution-layer rewards (priority fees and MEV payments) for one or more validators.
Get Validator Income HistoryRetrieve a per-epoch income breakdown for one or more validators.
Get Validator LeaderboardRetrieve the current top 100 validators ranked by 7-day consensus-layer rewards.
Get Validator ProposalsRetrieve beacon chain blocks proposed by one or more validators within a bounded epoch window.
Get Validators by Deposit AddressRetrieve validators that have made deposits from a specific execution-layer address.
Get Validators by Withdrawal CredentialsRetrieve validators whose withdrawal credentials match the provided value or execution-layer address.
Get Validators Proposal LuckRetrieve proposal luck statistics for one or more Ethereum Beacon Chain validators.
Get Validators QueueRetrieve current queue metrics for validators on the Ethereum Beacon Chain.
Get Validator WithdrawalsRetrieve withdrawal operations attributed to one or more validators within a bounded epoch window.
Post ValidatorsRetrieve validator information using a JSON request body for multiple validators.
Resolve ENS Name or AddressResolve ENS (Ethereum Name Service) names to addresses and vice versa.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Beaconchain via MCP
  • python-dotenv loads environment variables

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")
What's happening:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["beaconchain"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Beaconchain operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

Here's the complete code to get you started with Beaconchain and Google ADK:

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["beaconchain"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Beaconchain operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Beaconchain with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Beaconchain using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Beaconchain tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

How to build Beaconchain MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Beaconchain MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Beaconchain MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Beaconchain MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Beaconchain MCP with Claude Cowork

Codex logo

Codex

Use Beaconchain MCP with Codex

OpenClaw logo

OpenClaw

Use Beaconchain MCP with OpenClaw

Hermes logo

Hermes

Use Beaconchain MCP with Hermes

CLI logo

CLI

Use Beaconchain MCP with CLI

LangChain logo

LangChain

Use Beaconchain MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Beaconchain MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Beaconchain MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Beaconchain MCP with LlamaIndex

CrewAI logo

CrewAI

Use Beaconchain MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Beaconchain MCP?

With a standalone Beaconchain MCP server, the agents and LLMs can only access a fixed set of Beaconchain tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Beaconchain and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Google ADK?

Yes, you can. Google ADK 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 Beaconchain tools.

Can I manage the permissions and scopes for Beaconchain while using Tool Router?

Yes, absolutely. You can configure which Beaconchain 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 Beaconchain 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.

Get started for freeGet a demo↗