# How to integrate Beaconchain MCP with Claude Code

```json
{
  "title": "How to integrate Beaconchain MCP with Claude Code",
  "toolkit": "Beaconchain",
  "toolkit_slug": "beaconchain",
  "framework": "Claude Code",
  "framework_slug": "claude-code",
  "url": "https://composio.dev/toolkits/beaconchain/framework/claude-code",
  "markdown_url": "https://composio.dev/toolkits/beaconchain/framework/claude-code.md",
  "updated_at": "2026-05-12T10:02:35.901Z"
}
```

## 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:
- Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach
- Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control

## Also integrate Beaconchain with

- [OpenAI Agents SDK](https://composio.dev/toolkits/beaconchain/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/beaconchain/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/beaconchain/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/beaconchain/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/beaconchain/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/beaconchain/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/beaconchain/framework/cli)
- [Google ADK](https://composio.dev/toolkits/beaconchain/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/beaconchain/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/beaconchain/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/beaconchain/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/beaconchain/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/beaconchain/framework/crew-ai)

## TL;DR

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

## Connect Beaconchain to Claude Code

### Connecting Beaconchain to Claude Code using Composio
1. Add the Composio MCP to Claude

```bash
claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp
```

## What is Claude Code?

Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working.
Key features include:
- Terminal-Native Experience: Work with Claude directly in your command line without switching contexts
- MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities
- Project Context: Claude understands your project structure and can read, write, and modify files
- Interactive Development: Ask questions, debug code, and get help in real-time while coding
- Multi-Platform: Works on macOS, Linux, WSL, and Windows

## 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

| Tool slug | Name | Description |
|---|---|---|
| `BEACONCHAIN_GET_CHART` | Get Chart | Retrieve chart visualizations from beaconcha.in as PNG images. Use when you need visual representations of Ethereum Beacon Chain data like validator counts, staked ether, network liveness, or block statistics. |
| `BEACONCHAIN_GET_EPOCH` | Get Epoch | Retrieve aggregate metrics and status for a beacon chain epoch. Use this tool to fetch epoch-level statistics including validator counts, balances, participation rates, block counts, and various operations (slashings, deposits, exits). Supports lookup by epoch number or keywords 'latest' or 'finalized'. |
| `BEACONCHAIN_GET_ETH1_DEPOSITS_BY_TX_HASH` | Get ETH1 Deposits by Transaction Hash | Retrieve all beacon chain validator deposit events associated with a specific execution-layer transaction hash. Use this tool to inspect deposit transactions and verify deposit parameters like amount, public key, and withdrawal credentials. Returns an empty array if the transaction contains no deposit events. |
| `BEACONCHAIN_GET_ETH_STORE_DAILY` | Get ETH.Store Daily Aggregates | Retrieve ETH.Store daily aggregate metrics for Ethereum validators. Use this to analyze the average financial return validators achieved over a specific 24-hour period, including APR metrics, consensus/execution layer rewards, and balance aggregates. |
| `BEACONCHAIN_GET_EXECUTION_ADDRESS_ERC20_TOKENS` | Get ERC-20 Token Balances | Retrieve a paginated list of ERC-20 token balances for a specific Ethereum address. Use offset and limit query parameters for pagination. Returns token contract address, balance in token units, and token symbol for each ERC-20 token held by the address. |
| `BEACONCHAIN_GET_EXECUTION_BLOCK` | Get Execution Block | Retrieve one or more execution-layer blocks by block number from the Ethereum Beacon Chain. Use this tool to look up execution block details including block hash, timestamp, rewards, gas usage, transaction counts, and consensus information. Supports querying up to 100 blocks in a single request by providing block numbers as a comma-separated list. Returns an array of execution block data. If a requested block number is not found, it will be omitted from the results. |
| `BEACONCHAIN_GET_EXECUTION_PRODUCED_BLOCKS` | Get Execution Produced Blocks | Retrieve execution-layer blocks attributed to one or more producers. Use this tool to query blocks produced by specific fee recipients, proposer indices, or validator public keys. Supports comma-separated lists to query multiple producers. Returns block details including gas usage, fees, transactions, and timestamps. |
| `BEACONCHAIN_GET_LATEST_STATE` | Get Latest State | Retrieve the latest known Ethereum Beacon Chain network state. Returns current slot, epoch numbers, finalized epoch, finality delay indicator, syncing status, and ETH/USD price along with multi-currency conversion rates. Use this to check current network status and get real-time ETH pricing data. |
| `BEACONCHAIN_GET_NETWORK_PERFORMANCE` | Get Network Performance | Retrieve aggregated network performance metrics for the Ethereum Beacon Chain. Use this to analyze validator performance across attestations, proposals, and sync committee duties over a specified time window. Returns beacon scores, duty statistics, and finality information. |
| `BEACONCHAIN_GET_NODE_HEALTH` | Get Explorer Health | Check the health status of the beaconcha.in explorer service. Returns status of monitoring modules including execution layer data, consensus layer data, services, Redis, app, and API modules. Use this to verify the beaconcha.in explorer is operational before making other API calls. |
| `BEACONCHAIN_GET_QUEUES` | Get Validator Queues | Retrieve current queue metrics for Ethereum Beacon Chain validators. Use this tool to check activation queue status, exit queue status, withdrawal sweep progress, and chain finality. Returns deposit queue count and balance, exit queue count and balance, estimated processing times, and churn limits. |
| `BEACONCHAIN_GET_ROCKETPOOL_VALIDATOR` | Get Rocket Pool Validator | Retrieve Rocket Pool-specific metadata for validators including minipool status, node fee, smoothing pool status, and RPL stake metrics. Use this to access Rocket Pool protocol data such as minipool addresses, node operator information, commission rates, and reward details. Returns empty data array if the validator is not a Rocket Pool validator. |
| `BEACONCHAIN_GET_SLOT` | Get Slot | Retrieve detailed information about an Ethereum Beacon Chain slot. Use this tool to look up slot details including attestations, slashing counts, block roots, execution payload data, validator proposer, graffiti, and sync aggregate information. Supports lookup by slot number, 'latest'/'head' keywords, or block root hash. Returns comprehensive slot data including: attestation count, block roots, epoch info, execution layer details (gas, fees, transactions), proposer info, and withdrawal count. |
| `BEACONCHAIN_GET_SLOT_ATTESTATIONS` | Get Slot Attestations | Retrieve all attestations included in the beacon block for a specific slot. Use this tool to get detailed attestation data including committee participation, checkpoint information, and validator indices for attestations in a given slot. |
| `BEACONCHAIN_GET_SLOT_ATTESTER_SLASHINGS` | Get Slot Attester Slashings | Retrieve all attester slashing operations included in the beacon block for a specific slot. Use this tool to check for attester slashings at a given slot number or the latest processed slot. |
| `BEACONCHAIN_GET_SLOT_PROPOSER_SLASHINGS` | Get Slot Proposer Slashings | Retrieve all proposer slashing operations included in the beacon block for a specific slot. Use this tool to check for proposer slashings at a given slot number or the latest processed slot. |
| `BEACONCHAIN_GET_SLOT_VOLUNTARY_EXITS` | Get Slot Voluntary Exits | Retrieve all voluntary exit operations included in the beacon block for a specific slot. Use when you need to examine which validators submitted exit requests in a given slot. Returns an empty array if the slot has no voluntary exits. |
| `BEACONCHAIN_GET_SYNC_COMMITTEE` | Get Sync Committee | Retrieve the sync committee membership for a given sync period. Returns a list of 512 validator indices that participate in light-client finality for the specified period. Each sync period spans 256 epochs. Use this to determine which validators have sync committee duties during a specific period. |
| `BEACONCHAIN_GET_VALIDATOR` | Get Validator | Retrieve detailed information about an Ethereum Beacon Chain validator. Use this tool to look up validator status, balance, activation epochs, slashing status, and other details. Supports lookup by validator index or BLS public key. Returns validator data including: current status (active_online, active_offline, pending, exiting, slashed, exited), balance in Gwei, activation/exit epochs, and withdrawal credentials. |
| `BEACONCHAIN_GET_VALIDATOR_ATTESTATION_EFFICIENCY` | Get Validator Attestation Efficiency | Retrieve normalized attestation inclusion effectiveness for one or more validators. Use this tool to measure how effectively validators are getting their attestations included in the Beacon Chain. A score of 1.0 indicates perfect effectiveness (100% inclusion), while higher scores indicate lower effectiveness (max 2.0 for 0% inclusion). Supports lookup by validator index, BLS public key, or a mix of both (comma-separated, maximum 100 validators per request by default). |
| `BEACONCHAIN_GET_VALIDATOR_ATTESTATIONS` | Get Validator Attestations | Retrieve attestations observed for one or more validators within a bounded epoch window. By default, returns data for the last 100 epochs. Use when you need to check validator attestation history, verify attestation performance, or analyze missed attestations. |
| `BEACONCHAIN_GET_VALIDATOR_BALANCE_HISTORY` | Get Validator Balance History | Retrieve per-epoch balance history for one or more Ethereum Beacon Chain validators. Use optional query parameters to control the time window (latest_epoch, offset, limit). Returns an array of balance snapshots showing how validator balances changed over time, including both total balance and effective balance. Useful for tracking validator performance and generating historical balance charts. |
| `BEACONCHAIN_GET_VALIDATOR_BLS_CHANGES` | Get Validator BLS Changes | Retrieve on-chain BLS-to-execution credential change messages (EIP-4881) for validators. Use this tool to check if validators have changed their withdrawal credentials from BLS (0x00) to execution-layer addresses (0x01). |
| `BEACONCHAIN_GET_VALIDATOR_CONSENSUS_REWARDS` | Get Validator Consensus Rewards | Retrieve consensus-layer rewards for one or more validators over multiple lookback windows. Returns reward totals for the last 1, 7, 31, and 365 days, plus cumulative totals when available. All amounts are returned in gwei. Supports lookup by validator index or BLS public key. |
| `BEACONCHAIN_GET_VALIDATOR_DAILY_STATS` | Get Validator Daily Stats | Retrieve per-day statistics for a single Ethereum Beacon Chain validator by index. Returns daily balance snapshots (start/end/min/max), duty counts (proposed/missed blocks, attestations), and deposit/withdrawal activity. Use this tool to analyze validator performance over time, track balance changes, and identify issues like missed duties or slashing events. Supports filtering by day range using `start_day` and `end_day` parameters. |
| `BEACONCHAIN_GET_VALIDATOR_DEPOSITS` | Get Validator Deposits | Retrieve execution-layer deposit events for one or more validators. Use when you need to check deposit history, verify deposit amounts, or audit withdrawal credentials for validators. |
| `BEACONCHAIN_GET_VALIDATOR_EXECUTION_REWARDS` | Get Validator Execution Rewards | Retrieve execution-layer rewards (priority fees and MEV payments) for one or more validators. Values are reported in wei and include reward totals for the last 1, 7, 31, and 365 days, plus cumulative rewards since genesis when available. Accepts up to 100 validator identifiers. |
| `BEACONCHAIN_GET_VALIDATOR_INCOME_HISTORY` | Get Validator Income History | Retrieve a per-epoch income breakdown for one or more validators. Returns consensus-layer rewards/penalties in gwei and execution-layer tips in wei. Use this to analyze validator earnings over time, including attestation rewards, proposer rewards, penalties, and MEV/tips. |
| `BEACONCHAIN_GET_VALIDATOR_LEADERBOARD` | Get Validator Leaderboard | Retrieve the current top 100 validators ranked by 7-day consensus-layer rewards. Returns performance metrics including 1-day, 7-day, 31-day, 365-day, and total rewards in Gwei for each validator. Use this to identify the highest-performing validators on the Ethereum Beacon Chain over the past week. |
| `BEACONCHAIN_GET_VALIDATOR_PROPOSALS` | Get Validator Proposals | Retrieve beacon chain blocks proposed by one or more validators within a bounded epoch window. By default, returns proposals from the last 100 epochs. Use this to get proposal history for validators by their indices or public keys. |
| `BEACONCHAIN_GET_VALIDATORS_BY_DEPOSIT_ADDRESS` | Get Validators by Deposit Address | Retrieve validators that have made deposits from a specific execution-layer address. Supports ENS names which are resolved server-side. Returns validator public keys, signature validity, and validator indices for all deposits from the address. |
| `BEACONCHAIN_GET_VALIDATORS_BY_WITHDRAWAL_CREDENTIALS` | Get Validators by Withdrawal Credentials | Retrieve validators whose withdrawal credentials match the provided value or execution-layer address. Use this tool to find all validators associated with a specific withdrawal credential (32-byte hex) or Ethereum address (20-byte hex). ENS names are supported for address lookups. Results are paginated using limit and offset parameters. |
| `BEACONCHAIN_GET_VALIDATORS_PROPOSAL_LUCK` | Get Validators Proposal Luck | Retrieve proposal luck statistics for one or more Ethereum Beacon Chain validators. Use this to analyze how lucky validators have been with block proposals compared to expected rates. |
| `BEACONCHAIN_GET_VALIDATORS_QUEUE` | Get Validators Queue | Retrieve current queue metrics for validators on the Ethereum Beacon Chain. Returns counts and total effective balances for validators awaiting activation and validators scheduled to exit. Use this to monitor validator queue status and network entry/exit activity. |
| `BEACONCHAIN_GET_VALIDATOR_WITHDRAWALS` | Get Validator Withdrawals | Retrieve withdrawal operations attributed to one or more validators within a bounded epoch window. Use this tool to fetch historical withdrawal data for validators on the Ethereum Beacon Chain. The API returns withdrawals from up to 100 epochs (defaulting to the most recent 100 epochs if no epoch is specified). |
| `BEACONCHAIN_POST_VALIDATORS` | Post Validators | Retrieve validator information using a JSON request body for multiple validators. Use this when the list of identifiers is too long for the GET path parameter (up to 100 identifiers). Supports lookup by validator indices or BLS public keys. Returns validator data including status, balance, activation/exit epochs, slashing status, and withdrawal credentials. |
| `BEACONCHAIN_RESOLVE_ENS` | Resolve ENS Name or Address | Resolve ENS (Ethereum Name Service) names to addresses and vice versa. Use this tool to perform bidirectional lookups between ENS domain names and Ethereum addresses. Accepts either an ENS name (e.g., 'vitalik.eth') or an Ethereum address and returns the corresponding mapping. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Beaconchain MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Beaconchain account. It provides structured and secure access so Claude can perform Beaconchain operations on your behalf.
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:
- Claude Pro, Max, or API billing enabled Anthropic account
- Composio API Key
- A Beaconchain account
- Basic knowledge of Python or TypeScript

### 1. Install Claude Code

To install Claude Code, use one of the following methods based on your operating system:
```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
```

### 2. Set up Claude Code

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
```bash
cd your-project-folder
claude
```

### 3. Set up environment variables

Create a .env file in your project root with the following variables:
- COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code))
- USER_ID identifies the user for session management (use any unique identifier)
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
```

### 4. Install Composio library

No description provided.
```python
pip install composio-core python-dotenv
```

```typescript
npm install @composio/core dotenv
```

### 5. Generate Composio MCP URL

No description provided.
```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

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

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http beaconchain-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
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}"`);
```

### 6. Run the script and copy the MCP URL

No description provided.
```python
python generate_mcp_url.py
```

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

### 7. Add Beaconchain MCP to Claude Code

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.
```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
```

### 8. Verify the installation

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:
```bash
claude mcp list
```

### 9. 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

```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

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

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http beaconchain-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
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.

## How to build Beaconchain MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/beaconchain/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/beaconchain/framework/claude-agents-sdk)
- [Claude Cowork](https://composio.dev/toolkits/beaconchain/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/beaconchain/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/beaconchain/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/beaconchain/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/beaconchain/framework/cli)
- [Google ADK](https://composio.dev/toolkits/beaconchain/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/beaconchain/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/beaconchain/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/beaconchain/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/beaconchain/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/beaconchain/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.
- [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.
- [Bitquery](https://composio.dev/toolkits/bitquery) - Bitquery is a blockchain data platform offering indexed, real-time, and historical data from 40+ blockchains via GraphQL APIs. Get unified, reliable access to complex on-chain data for analytics, trading, and research.
- [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 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 Claude Code?

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.

### 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.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)