# How to integrate Alchemy MCP with LangChain

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

## Introduction

This guide walks you through connecting Alchemy to LangChain using the Composio tool router. By the end, you'll have a working Alchemy agent that can show all nfts owned by this wallet, get recent sales for a specific nft collection, check erc20 token balances for your address through natural language commands.
This guide will help you understand how to give your LangChain agent real control over a Alchemy account through Composio's Alchemy MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Alchemy with

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

## TL;DR

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Connect your Alchemy project to Composio
- Create a Tool Router MCP session for Alchemy
- Initialize an MCP client and retrieve Alchemy tools
- Build a LangChain agent that can interact with Alchemy
- 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 Alchemy MCP server, and what's possible with it?

The Alchemy MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Alchemy account. It provides structured and secure access to your blockchain data, so your agent can perform actions like fetching NFT metadata, tracking token balances, analyzing transaction history, and managing Ethereum assets on your behalf.
- Retrieve NFT contract and token metadata: Instantly access detailed information about any NFT collection or token, including name, symbol, supply, and contract deployer.
- Analyze NFT sales and ownership: Let your agent fetch historical NFT sales across marketplaces and list current owners for any ERC-721 or ERC-1155 token.
- Track token balances and portfolio: Effortlessly check ERC-20 token balances for any Ethereum address to monitor holdings or build portfolio analytics.
- List NFTs within a collection: Pull a complete list of NFTs under a specific contract to explore, display, or analyze full collections.
- Monitor transaction counts and activity: Quickly get the transaction count (nonce) for any Ethereum address to understand activity or prepare for new transactions.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `ALCHEMY_COMPUTE_RARITY_V3` | Compute NFT Rarity | Tool to compute the rarity of each attribute for a specific NFT based on its collection. Returns prevalence data for each trait, indicating how common or rare each attribute is compared to other NFTs in the same collection. Use when analyzing NFT rarity for trading decisions, collection analysis, or valuation purposes. |
| `ALCHEMY_GET_COLLECTION_METADATA` | Get NFT Collection Metadata | Tool to get metadata for an NFT collection using its marketplace slug (OpenSea, LooksRare, etc). Use when you need collection-level information such as name, description, social links, and floor price. This is useful for discovering collection details without needing the contract address. |
| `ALCHEMY_GET_COLLECTIONS_FOR_OWNER` | Get Collections for Owner | Tool to retrieve all NFT collections held by a specified owner address. Use when you need to get a comprehensive view of what NFT collections a wallet owns, including collection metadata, ownership counts, and spam classification. Only supported on Ethereum. Supports pagination for large collections and filtering options to include or exclude spam/airdrops. |
| `ALCHEMY_GET_CONTRACT_METADATA_BATCH_V3` | Get Contract Metadata Batch V3 | Tool to retrieve metadata for multiple NFT contracts in a single batch request. Use when you need to fetch contract information for several NFT collections at once to improve efficiency and reduce API calls. |
| `ALCHEMY_GET_CONTRACT_METADATA_V3` | Get Contract Metadata V3 | Tool to get the metadata for an NFT contract including name, symbol, total supply, and token type (ERC721/ERC1155). Use when you need to retrieve comprehensive contract information such as deployer address, deployment block, OpenSea metadata, and collection details. |
| `ALCHEMY_GET_CONTRACTS_FOR_OWNER_V3` | Get Contracts for Owner (NFT API v3) | Tool to get all NFT contracts owned by an address with contract metadata. Use when you need to retrieve a comprehensive list of NFT collections held by a specific wallet address, including detailed contract information such as token type, total supply, deployer info, spam classification, and OpenSea metadata. Supports pagination for addresses with large NFT holdings. |
| `ALCHEMY_GET_FLOOR_PRICE_V3` | Get NFT Floor Price | Tool to get the floor price for an NFT collection across multiple marketplaces (OpenSea, LooksRare, etc). Use when you need to check the current floor price of an NFT collection or compare prices across different marketplaces. Returns floor price data including price, currency, collection URL, and timestamp of when the price was retrieved. |
| `ALCHEMY_GET_HISTORICAL_PRICES` | Get Historical Token Prices | Retrieves historical price data for a token over a specified time range with configurable intervals. Identify the token either by symbol (e.g., ETH, BTC) or by network and contract address. Use this to build price charts, analyze price trends, calculate historical returns, or display historical price information in your application. Important: Provide either symbol OR both network and address (not both methods simultaneously). Time range is specified with start_time and end_time (Unix timestamps or ISO 8601 strings). The interval parameter controls data point granularity (5m, 1h, or 1d). |
| `ALCHEMY_GET_NFT_CONTRACTS_BY_ADDRESS` | Get NFT Contracts By Address | Tool to retrieve NFT contracts associated with one or more wallet addresses across multiple blockchain networks. Use when you need to discover which NFT collections a wallet owns tokens from, across networks like Ethereum, Base, Polygon, Arbitrum, and Optimism. Returns contract details including metadata, spam classification, and OpenSea data. |
| `ALCHEMY_GET_NFT_METADATA` | Get NFT Metadata | Tool to retrieve comprehensive metadata for a specific NFT, including contract details, media URLs, attributes, ownership info, and OpenSea data. Use when you need detailed information about a particular NFT token, such as its image, traits, description, or contract metadata. |
| `ALCHEMY_GET_NFT_METADATA_BATCH` | Get NFT Metadata Batch | Tool to retrieve metadata for multiple NFTs in a single request (up to 100 NFTs), including contract details, media URLs, attributes, and collection data. Use when you need detailed information about multiple NFT tokens efficiently. More efficient than making individual calls for each NFT. |
| `ALCHEMY_GET_NFT_SALES_V3` | Get NFT Sales V3 | Retrieves NFT sales that have occurred through on-chain marketplaces using Alchemy's v3 API. Supports Ethereum (Seaport, Wyvern, X2Y2, Blur, LooksRare, Cryptopunks), Polygon (Seaport), and Optimism (Seaport) mainnets. Use this to track NFT sales activity, analyze market trends, monitor specific collections or tokens, and gather comprehensive sales data including prices, fees, and transaction details. Supports flexible filtering by block range, marketplace, contract, token, buyer, seller, and taker role. |
| `ALCHEMY_GET_NF_TS_FOR_COLLECTION_V3` | Get NFTs for Collection V3 | Retrieves all NFTs in a collection using OpenSea collection slug or contract address. Use when you need to fetch NFTs by collection name rather than contract address. Similar to getNFTsForContract but uses collection slug for easier querying. Supports pagination for large collections. |
| `ALCHEMY_GET_NF_TS_FOR_CONTRACT` | Get NFTs for Contract | Retrieves all NFTs for a given NFT contract address. Supports both ERC721 and ERC1155 token standards. Returns detailed NFT data including token IDs, metadata, images, and attributes. Use this to analyze NFT collections, build marketplace features, track collection holdings, or create analytics dashboards. Supports pagination to handle large collections efficiently (returns up to 100 NFTs per request). |
| `ALCHEMY_GET_NF_TS_FOR_OWNER` | Get NFTs for Owner | Tool to get all NFTs currently owned by a given address. Supports ERC721 and ERC1155 tokens on Ethereum and L2s including Polygon, Arbitrum, Optimism, Base. Use when you need to retrieve NFT holdings for an address with optional metadata. |
| `ALCHEMY_GET_OWNERS_FOR_COLLECTION` | Get Owners for Collection | Tool to retrieve all owner addresses for a given NFT collection contract. Use when you need to analyze NFT ownership distribution, find all holders of a collection, or build ownership analytics for ERC721 and ERC1155 contracts. Optionally returns token balances per owner. |
| `ALCHEMY_GET_OWNERS_FOR_CONTRACT` | Get Owners for Contract | Tool to get all owners of NFTs in a contract with optional token balances. Use when you need to analyze NFT holder distribution, prepare airdrops, or identify token owners for specific collections. |
| `ALCHEMY_GET_OWNERS_FOR_NFTV3` | Get NFT Owners (v3) | Tool to retrieve all owners for a specific NFT using Alchemy's v3 API. For ERC-721 tokens returns single owner, for ERC-1155 tokens returns all owners with quantities. Use when you need to identify current ownership of an NFT token. |
| `ALCHEMY_GET_PORTFOLIO_NF_TS_BY_ADDRESS` | Get Portfolio NFTs By Address | Tool to fetch NFTs owned by multiple wallet addresses across different blockchain networks. Returns comprehensive NFT metadata including contract details, images, attributes, and ownership information. Use when you need to retrieve NFT portfolio data for wallets across multiple chains. |
| `ALCHEMY_GET_PRICES_BY_SYMBOL` | Get Token Prices By Symbol | Tool to get current token prices by symbol (e.g., ETH, USDC, BTC) using aggregated CEX and DEX data. Use when you need real-time cryptocurrency prices in USD or other currencies. Supports up to 25 symbols per request. Note: Response succeeds even if some tokens are missing - check the error field in each result item. |
| `ALCHEMY_GET_TOKEN_BALANCES` | Get Token Balances | This tool retrieves ERC20 token balances for a specified Ethereum address. It can either return balances for all tokens an address has ever interacted with or for a specific set of token contract addresses. It is useful for checking token balances for wallets, monitoring ERC20 token holdings, portfolio tracking, and DeFi applications. |
| `ALCHEMY_GET_TOKEN_BALANCES_BY_ADDRESS` | Get Token Balances By Address | Tool to get token balances for wallet addresses across multiple networks using Alchemy's Portfolio API. Use when you need lightweight balance checks for one or more addresses without full token metadata. Supports up to 3 address/network pairs per request with pagination for large result sets. |
| `ALCHEMY_GET_TOKEN_METADATA` | Get Token Metadata | Retrieves metadata for an ERC-20 token on Ethereum mainnet, including its name, symbol, decimals, and logo URL. This information is essential for displaying token details in user interfaces, calculating token amounts (using decimals), and showing token branding. Use this when you need to: - Display token information to users (name, symbol, logo) - Convert token amounts between human-readable and contract formats (requires decimals) - Build token listings or portfolio displays - Validate or enrich token data Note: Returns empty/null values for invalid or non-token contract addresses. |
| `ALCHEMY_GET_TOKEN_PRICES_BY_ADDRESS` | Get Token Prices By Address | Retrieves current token prices by contract address and network from decentralized exchanges (DEXes). Use when you need real-time token price data for specific contract addresses across multiple networks. Price data is aggregated from DEXes only (not CEXes) and weighted by total volume. Supports up to 25 addresses per request across maximum 3 different networks. Returns price in USD by default with timestamp. Response succeeds even if some prices are unavailable. |
| `ALCHEMY_GET_TOKENS_BY_ADDRESS` | Get Tokens By Address | Tool to fetch fungible tokens (native, ERC-20, SPL) for multiple wallet addresses across networks. Returns comprehensive token information including balances, metadata (name, symbol, decimals, logo), and current prices. Use when you need complete token portfolio data for wallets across multiple chains (Ethereum, Polygon, Arbitrum, Base, Optimism, Solana, and 30+ EVM chains). Supports up to 2 addresses with 5 networks each per request, with pagination for large result sets. |
| `ALCHEMY_GET_TRANSACTION_COUNT` | Get Transaction Count | This tool retrieves the number of transactions sent from a specific address (also known as the nonce). It uses the eth_getTransactionCount endpoint to return the transaction count for an address at a specified block tag (latest, pending, earliest, or a HEX block number), which is essential for determining the nonce for subsequent transactions. |
| `ALCHEMY_GET_TRANSACTIONS_HISTORY_BY_ADDRESS` | Get Transactions History By Address | Tool to get transaction history for wallet addresses across multiple networks using Alchemy's Data API. Use when you need to retrieve historical transactions with detailed metadata including logs and internal transactions. Supports pagination for large result sets with a maximum of 50 transactions per request. |
| `ALCHEMY_INVALIDATE_CONTRACT_V3` | Invalidate NFT Contract Cache | Tool to invalidate the cached metadata for an NFT contract. Use when you need to force a refresh of stale or outdated NFT metadata on the next request. This is useful after contract updates or when metadata changes are expected. |
| `ALCHEMY_IS_AIRDROP` | Check If NFT Is Airdrop | Tool to check if a specific NFT token is marked as an airdrop. Use when you need to determine whether an NFT was distributed via airdrop mechanism. Returns true if the token is identified as an airdrop, false otherwise. |
| `ALCHEMY_IS_AIRDROP_NFT` | Check If NFT Is Airdrop | Tool to determine whether an NFT was airdropped to the owner address. Use when you need to identify if a specific token was received as an airdrop rather than through a purchase or mint. |
| `ALCHEMY_IS_HOLDER_OF_COLLECTION` | Check Collection Ownership | Tool to check if a wallet address owns any token from a specific NFT collection. Use this when you need to verify collection ownership without retrieving full NFT details, supporting both ERC721 and ERC1155 standards. |
| `ALCHEMY_IS_HOLDER_OF_CONTRACT` | Check NFT Holder Status | Tool to check if a wallet address holds any NFTs from a specific contract. Use when you need to verify NFT ownership for access control, membership verification, or token-gating features. Supports both ERC721 and ERC1155 contracts. |
| `ALCHEMY_IS_SPAM_CONTRACT` | Check if Contract is Spam | Tool to check if an NFT contract is marked as spam by Alchemy. Use when you need to verify the legitimacy of an NFT contract before interacting with it or displaying its assets. Returns true if the contract is flagged as spam, false if it's valid or hasn't been evaluated yet. |
| `ALCHEMY_IS_SPAM_CONTRACT_V3` | Check if Contract is Spam (V3) | Tool to determine if a specific NFT contract is marked as spam by Alchemy. Use when you need to verify the legitimacy of an NFT contract address before interacting with it. Available on paid Alchemy tiers only. |
| `ALCHEMY_SEARCH_CONTRACT_METADATA_V3` | Search NFT Contract Metadata | Tool to search for keywords across metadata of all ERC-721 and ERC-1155 smart contracts. Use when you need to find NFT collections by name, symbol, or description keywords. Returns contract addresses, names, symbols, token types, deployer info, and OpenSea metadata for matching collections. |
| `ALCHEMY_SUMMARIZE_NFT_ATTRIBUTES` | Summarize NFT Attributes | Retrieves a comprehensive summary of all attributes and traits for NFTs in a collection, including trait counts and distribution statistics. Use this to analyze rarity, understand collection composition, or build trait filters for NFT marketplaces and analytics dashboards. |

## Supported Triggers

None listed.

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

The Alchemy MCP server is an implementation of the Model Context Protocol that connects your AI agent to Alchemy. It provides structured and secure access so your agent can perform Alchemy 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 Alchemy 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 Alchemy 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 Alchemy tools as needed
```python
# Create Tool Router session for Alchemy
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['alchemy']
)

url = session.mcp.url
```

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

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

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

No description provided.
```python
client = MultiServerMCPClient({
    "alchemy-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({
    "alchemy-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 Alchemy 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 Alchemy 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=['alchemy']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "alchemy-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 Alchemy 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: ['alchemy']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "alchemy-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 Alchemy 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 Alchemy 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 Alchemy MCP Agent with another framework

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

## Related Toolkits

- [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.
- [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.
- [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.
- [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences.
- [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses.
- [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure.
- [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction.
- [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting.
- [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache.
- [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence.
- [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place.
- [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines.
- [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure.
- [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code.
- [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows.
- [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights.
- [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews.
- [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease.
- [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data.
- [Bolt iot](https://composio.dev/toolkits/bolt_iot) - Bolt IoT is a platform for building and managing IoT projects with cloud-based device control and monitoring. It makes connecting sensors and actuators to the internet seamless for automation and data insights.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Alchemy MCP?

With a standalone Alchemy MCP server, the agents and LLMs can only access a fixed set of Alchemy tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Alchemy 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 Alchemy tools.

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

Yes, absolutely. You can configure which Alchemy 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 Alchemy data and credentials are handled as safely as possible.

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