How to integrate Beaconchain MCP with Autogen

This guide walks you through connecting Beaconchain to AutoGen 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 AutoGen 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.

Get started for free Get a demo

Beaconchain

Api Key

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.

37 Tools

Managed auth

Connect Beaconchain without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Try for free

Introduction

This guide will help you understand how to give your AutoGen 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

OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

Get and set up your OpenAI and Composio API keys
Install the required dependencies for Autogen and Composio
Initialize Composio and create a Tool Router session for Beaconchain
Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams
Configure an Autogen AssistantAgent that can call Beaconchain tools
Run a live chat loop where you ask the agent to perform Beaconchain operations

What is AutoGen?

Autogen is a framework for building multi-agent conversational AI systems from Microsoft. It enables you to create agents that can collaborate, use tools, and maintain complex workflows.

Key features include:

Multi-Agent Systems: Build collaborative agent workflows
MCP Workbench: Native support for Model Context Protocol tools
Streaming HTTP: Connect to external services through streamable HTTP
AssistantAgent: Pre-built agent class for tool-using assistants

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.

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:

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

Step-by-step Guide

Step by step08 STEPS

Prerequisites

You will need:

A Composio API key
An OpenAI API key (used by Autogen's OpenAIChatCompletionClient)
A Beaconchain account you can connect to Composio
Some basic familiarity with Autogen and Python async

Getting API Keys for OpenAI and Composio

OpenAI API Key

Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
Keep the API key safe.

Composio API Key

Log in to the Composio dashboard.
Navigate to your API settings and generate a new API key.
Store this key securely as you'll need it for authentication.

Install dependencies

bash

pip install composio python-dotenv
pip install autogen-agentchat autogen-ext-openai autogen-ext-tools

Install Composio, Autogen extensions, and dotenv.

What's happening:

composio connects your agent to Beaconchain via MCP
autogen-agentchat provides the AssistantAgent class
autogen-ext-openai provides the OpenAI model client
autogen-ext-tools provides MCP workbench support

Set up environment variables

bash

COMPOSIO_API_KEY=your-composio-api-key
OPENAI_API_KEY=your-openai-api-key
USER_ID=your-user-identifier@example.com

Create a .env file in your project folder.

What's happening:

COMPOSIO_API_KEY is required to talk to Composio
OPENAI_API_KEY is used by Autogen's OpenAI client
USER_ID is how Composio identifies which user's Beaconchain connections to use

Import dependencies and create Tool Router session

python

import asyncio
import os
from dotenv import load_dotenv
from composio import Composio

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Beaconchain session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["beaconchain"]
    )
    url = session.mcp.url

What's happening:

load_dotenv() reads your .env file
Composio(api_key=...) initializes the SDK
create(...) creates a Tool Router session that exposes Beaconchain tools
session.mcp.url is the MCP endpoint that Autogen will connect to

Configure MCP parameters for Autogen

python

# Configure MCP server parameters for Streamable HTTP
server_params = StreamableHttpServerParams(
    url=url,
    timeout=30.0,
    sse_read_timeout=300.0,
    terminate_on_close=True,
    headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
)

Autogen expects parameters describing how to talk to the MCP server. That is what StreamableHttpServerParams is for.

What's happening:

url points to the Tool Router MCP endpoint from Composio
timeout is the HTTP timeout for requests
sse_read_timeout controls how long to wait when streaming responses
terminate_on_close=True cleans up the MCP server process when the workbench is closed

Create the model client and agent

python

# Create model client
model_client = OpenAIChatCompletionClient(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY")
)

# Use McpWorkbench as context manager
async with McpWorkbench(server_params) as workbench:
    # Create Beaconchain assistant agent with MCP tools
    agent = AssistantAgent(
        name="beaconchain_assistant",
        description="An AI assistant that helps with Beaconchain operations.",
        model_client=model_client,
        workbench=workbench,
        model_client_stream=True,
        max_tool_iterations=10
    )

What's happening:

OpenAIChatCompletionClient wraps the OpenAI model for Autogen
McpWorkbench connects the agent to the MCP tools
AssistantAgent is configured with the Beaconchain tools from the workbench

Run the interactive chat loop

python

print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Beaconchain related question or task to the agent.\n")

# Conversation loop
while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    print("\nAgent is thinking...\n")

    # Run the agent with streaming
    try:
        response_text = ""
        async for message in agent.run_stream(task=user_input):
            if hasattr(message, "content") and message.content:
                response_text = message.content

        # Print the final response
        if response_text:
            print(f"Agent: {response_text}\n")
        else:
            print("Agent: I encountered an issue processing your request.\n")

    except Exception as e:
        print(f"Agent: Sorry, I encountered an error: {str(e)}\n")

What's happening:

The script prompts you in a loop with You:
Autogen passes your input to the model, which decides which Beaconchain tools to call via MCP
agent.run_stream(...) yields streaming messages as the agent thinks and calls tools
Typing exit, quit, or bye ends the loop

Complete Code

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

python

import asyncio
import os
from dotenv import load_dotenv
from composio import Composio

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Beaconchain session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["beaconchain"]
    )
    url = session.mcp.url

    # Configure MCP server parameters for Streamable HTTP
    server_params = StreamableHttpServerParams(
        url=url,
        timeout=30.0,
        sse_read_timeout=300.0,
        terminate_on_close=True,
        headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
    )

    # Create model client
    model_client = OpenAIChatCompletionClient(
        model="gpt-5",
        api_key=os.getenv("OPENAI_API_KEY")
    )

    # Use McpWorkbench as context manager
    async with McpWorkbench(server_params) as workbench:
        # Create Beaconchain assistant agent with MCP tools
        agent = AssistantAgent(
            name="beaconchain_assistant",
            description="An AI assistant that helps with Beaconchain operations.",
            model_client=model_client,
            workbench=workbench,
            model_client_stream=True,
            max_tool_iterations=10
        )

        print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
        print("Ask any Beaconchain related question or task to the agent.\n")

        # Conversation loop
        while True:
            user_input = input("You: ").strip()

            if user_input.lower() in ['exit', 'quit', 'bye']:
                print("\nGoodbye!")
                break

            if not user_input:
                continue

            print("\nAgent is thinking...\n")

            # Run the agent with streaming
            try:
                response_text = ""
                async for message in agent.run_stream(task=user_input):
                    if hasattr(message, 'content') and message.content:
                        response_text = message.content

                # Print the final response
                if response_text:
                    print(f"Agent: {response_text}\n")
                else:
                    print("Agent: I encountered an issue processing your request.\n")

            except Exception as e:
                print(f"Agent: Sorry, I encountered an error: {str(e)}\n")

if __name__ == "__main__":
    asyncio.run(main())

Conclusion

You now have an Autogen assistant wired into Beaconchain through Composio's Tool Router and MCP. From here you can:

Add more toolkits to the toolkits list, for example notion or hubspot
Refine the agent description to point it at specific workflows
Wrap this script behind a UI, Slack bot, or internal tool

Once the pattern is clear for Beaconchain, you can reuse the same structure for other MCP-enabled apps with minimal code changes.

TOOLS

Supported Tools

Every Beaconchain action and event your agent gets out of the box.

Get Chart

Retrieve chart visualizations from beaconcha.

Get Epoch

Retrieve aggregate metrics and status for a beacon chain epoch.

Get ETH1 Deposits by Transaction Hash

Retrieve all beacon chain validator deposit events associated with a specific execution-layer transaction hash.

Get ETH.Store Daily Aggregates

Retrieve ETH.

Get ERC-20 Token Balances

Retrieve a paginated list of ERC-20 token balances for a specific Ethereum address.

Get Execution Block

Retrieve one or more execution-layer blocks by block number from the Ethereum Beacon Chain.

Get Execution Produced Blocks

Retrieve execution-layer blocks attributed to one or more producers.

Get Latest State

Retrieve the latest known Ethereum Beacon Chain network state.

Get Network Performance

Retrieve aggregated network performance metrics for the Ethereum Beacon Chain.

Get Explorer Health

Check the health status of the beaconcha.

Get Validator Queues

Retrieve current queue metrics for Ethereum Beacon Chain validators.

Get Rocket Pool Validator

Retrieve Rocket Pool-specific metadata for validators including minipool status, node fee, smoothing pool status, and RPL stake metrics.

Get Slot

Retrieve detailed information about an Ethereum Beacon Chain slot.

Get Slot Attestations

Retrieve all attestations included in the beacon block for a specific slot.

Get Slot Attester Slashings

Retrieve all attester slashing operations included in the beacon block for a specific slot.

Get Slot Proposer Slashings

Retrieve all proposer slashing operations included in the beacon block for a specific slot.

Get Slot Voluntary Exits

Retrieve all voluntary exit operations included in the beacon block for a specific slot.

Get Sync Committee

Retrieve the sync committee membership for a given sync period.

Get Validator

Retrieve detailed information about an Ethereum Beacon Chain validator.

Get Validator Attestation Efficiency

Retrieve normalized attestation inclusion effectiveness for one or more validators.

Get Validator Attestations

Retrieve attestations observed for one or more validators within a bounded epoch window.

Get Validator Balance History

Retrieve per-epoch balance history for one or more Ethereum Beacon Chain validators.

Get Validator BLS Changes

Retrieve on-chain BLS-to-execution credential change messages (EIP-4881) for validators.

Get Validator Consensus Rewards

Retrieve consensus-layer rewards for one or more validators over multiple lookback windows.

Get Validator Daily Stats

Retrieve per-day statistics for a single Ethereum Beacon Chain validator by index.

Get Validator Deposits

Retrieve execution-layer deposit events for one or more validators.

Get Validator Execution Rewards

Retrieve execution-layer rewards (priority fees and MEV payments) for one or more validators.

Get Validator Income History

Retrieve a per-epoch income breakdown for one or more validators.

Get Validator Leaderboard

Retrieve the current top 100 validators ranked by 7-day consensus-layer rewards.

Get Validator Proposals

Retrieve beacon chain blocks proposed by one or more validators within a bounded epoch window.

Get Validators by Deposit Address

Retrieve validators that have made deposits from a specific execution-layer address.

Get Validators by Withdrawal Credentials

Retrieve validators whose withdrawal credentials match the provided value or execution-layer address.

Get Validators Proposal Luck

Retrieve proposal luck statistics for one or more Ethereum Beacon Chain validators.

Get Validators Queue

Retrieve current queue metrics for validators on the Ethereum Beacon Chain.

Get Validator Withdrawals

Retrieve withdrawal operations attributed to one or more validators within a bounded epoch window.

Post Validators

Retrieve validator information using a JSON request body for multiple validators.

Resolve ENS Name or Address

Resolve ENS (Ethereum Name Service) names to addresses and vice versa.

FRAMEWORKS

How to build Beaconchain MCP Agent with another framework

OpenAI Agents SDK

Use Beaconchain MCP with OpenAI Agents SDK

Claude Agent SDK

Use Beaconchain MCP with Claude Agent SDK

Claude Code

Use Beaconchain MCP with Claude Code

Claude Cowork

Use Beaconchain MCP with Claude Cowork

Codex

Use Beaconchain MCP with Codex

OpenClaw

Use Beaconchain MCP with OpenClaw

Hermes

Use Beaconchain MCP with Hermes

CLI

Use Beaconchain MCP with CLI

Google ADK

Use Beaconchain MCP with Google ADK

LangChain

Use Beaconchain MCP with LangChain

Vercel AI SDK

Use Beaconchain MCP with Vercel AI SDK

Mastra AI

Use Beaconchain MCP with Mastra AI

LlamaIndex

Use Beaconchain MCP with LlamaIndex

CrewAI

Use Beaconchain MCP with CrewAI

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Excel

Oauth2S2s Oauth2

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

Api Key

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

Api Key

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

Api Key

Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.

FAQ

Frequently asked questions

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.

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

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.

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.

Start with Beaconchain.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Beaconchain tool your agent needs.Free to start.

Start building

Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREE BOOK A DEMO

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati

Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya

Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave

CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu

Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola

Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche

Co-Founder, Ingram Technologies

How to integrate Beaconchain MCP with Autogen

Connect Beaconchain without auth hassles

Introduction

Also integrate Beaconchain with

TL;DR

What is AutoGen?

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

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install dependencies

Set up environment variables

Import dependencies and create Tool Router session

Configure MCP parameters for Autogen

Create the model client and agent

Run the interactive chat loop

Complete Code

Conclusion

Supported Tools

How to build Beaconchain MCP Agent with another framework

OpenAI Agents SDK

Claude Agent SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

LlamaIndex

CrewAI

Explore Other Toolkits

Excel

21risk

Abstract

Addressfinder

Frequently asked questions

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

Can I use Tool Router MCP with Autogen?+

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

How safe is my data with Composio Tool Router?+

Start with Beaconchain.It takes 30 seconds.

Teams ship real agents on Composio