How to integrate Beaconchain MCP with Claude Code

Manage your Beaconchain directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

Beaconchain logoBeaconchain
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

Introduction

Manage your Beaconchain directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Beaconchain with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Beaconchain to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

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.

Connecting Beaconchain via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Beaconchain) for even more tool search precision. It's secure and reliable.

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

Step by step10 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Beaconchain account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['beaconchain'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http beaconchain-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Beaconchain. This URL will be used to connect Claude Code to Beaconchain.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Beaconchain
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Beaconchain MCP to Claude Code

bash
claude mcp add --transport http beaconchain-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (beaconchain-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Beaconchain MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your beaconchain-composio entry in the list
  • This confirms that Claude Code can now access Beaconchain tools

If everything is wired up, you should see your beaconchain-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Beaconchain

The first time you try to use Beaconchain tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Beaconchain
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Beaconchain authorization flow
  • Return to the terminal and start using Beaconchain through Claude Code

Once authenticated, you can ask Claude Code to perform Beaconchain operations in natural language. For example:

  • "Check if my Ethereum node is syncing"
  • "Get health status of the beacon chain node"
  • "Fetch details for validator ID 12345"

Complete Code

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

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['beaconchain'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http beaconchain-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Beaconchain with Claude Code using Composio's MCP server. Now you can interact with Beaconchain directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Beaconchain operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Beaconchain operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

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.

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. Claude Code 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