# How to integrate Beaconchain MCP with LangChain

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

## Introduction

This guide walks you through connecting Beaconchain to LangChain 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 LangChain 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](https://composio.dev/toolkits/beaconchain/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/beaconchain/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/beaconchain/framework/claude-code)
- [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)
- [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

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Connect your Beaconchain project to Composio
- Create a Tool Router MCP session for Beaconchain
- Initialize an MCP client and retrieve Beaconchain tools
- Build a LangChain agent that can interact with Beaconchain
- Set up an interactive chat interface for testing

## What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.
Key features include:
- Agent Framework: Build agents that can use tools and make decisions
- MCP Integration: Connect to external services through Model Context Protocol adapters
- Memory Management: Maintain conversation history across interactions
- Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

## 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 your AI agent to Beaconchain. It provides structured and secure access so your agent can perform Beaconchain operations on your behalf through a secure, permission-based interface.
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

No description provided.

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

No description provided.
```python
pip install composio-langchain langchain-mcp-adapters langchain python-dotenv
```

```typescript
npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates your requests to Composio's API
- COMPOSIO_USER_ID identifies the user for session management
- OPENAI_API_KEY enables access to OpenAI's language models
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import dependencies

No description provided.
```python
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()
```

```typescript
import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
```

### 5. Initialize Composio client

What's happening:
- We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
- Creating a Composio instance that will manage our connection to Beaconchain tools
- Validating that COMPOSIO_USER_ID is also set before proceeding
```python
async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))

    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
```

```typescript
const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
```

### 6. Create a Tool Router session

What's happening:
- We're creating a Tool Router session that gives your agent access to Beaconchain tools
- The create method takes the user ID and specifies which toolkits should be available
- The returned session.mcp.url is the MCP server URL that your agent will use
- This approach allows the agent to dynamically load and use Beaconchain tools as needed
```python
# Create Tool Router session for Beaconchain
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['beaconchain']
)

url = session.mcp.url
```

```typescript
const session = await composio.create(
    userId as string,
    {
        toolkits: ['beaconchain']
    }
);

const url = session.mcp.url;
```

### 7. Configure the agent with the MCP URL

No description provided.
```python
client = MultiServerMCPClient({
    "beaconchain-agent": {
        "transport": "streamable_http",
        "url": session.mcp.url,
        "headers": {
            "x-api-key": os.getenv("COMPOSIO_API_KEY")
        }
    }
})

tools = await client.get_tools()

agent = create_agent("gpt-5", tools)
```

```typescript
const client = new MultiServerMCPClient({
    "beaconchain-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
```

### 8. Set up interactive chat interface

No description provided.
```python
conversation_history = []

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

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

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

    if not user_input:
        continue

    conversation_history.append({"role": "user", "content": user_input})
    print("\nAgent is thinking...\n")

    response = await agent.ainvoke({"messages": conversation_history})
    conversation_history = response['messages']
    final_response = response['messages'][-1].content
    print(f"Agent: {final_response}\n")
```

```typescript
let conversationHistory: any[] = [];

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

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
```

### 9. Run the application

No description provided.
```python
if __name__ == "__main__":
    asyncio.run(main())
```

```typescript
main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
```

## Complete Code

```python
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    
    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
    
    session = composio.create(
        user_id=os.getenv("COMPOSIO_USER_ID"),
        toolkits=['beaconchain']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "beaconchain-agent": {
            "transport": "streamable_http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    })
    
    tools = await client.get_tools()
  
    agent = create_agent("gpt-5", tools)
    
    conversation_history = []
    
    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Ask any Beaconchain related question or task to the agent.\n")
    
    while True:
        user_input = input("You: ").strip()
        
        if user_input.lower() in ['exit', 'quit', 'bye']:
            print("\nGoodbye!")
            break
        
        if not user_input:
            continue
        
        conversation_history.append({"role": "user", "content": user_input})
        print("\nAgent is thinking...\n")
        
        response = await agent.ainvoke({"messages": conversation_history})
        conversation_history = response['messages']
        final_response = response['messages'][-1].content
        print(f"Agent: {final_response}\n")

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

```typescript
import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['beaconchain']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "beaconchain-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Beaconchain related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
```

## Conclusion

You've successfully built a LangChain agent that can interact with Beaconchain through Composio's Tool Router.
Key features of this implementation:
- Dynamic tool loading through Composio's Tool Router
- Conversation history maintenance for context-aware responses
- Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

## 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 Code](https://composio.dev/toolkits/beaconchain/framework/claude-code)
- [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)
- [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 LangChain?

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