How to integrate Alchemy MCP with Claude Agent SDK

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Alchemy logo
Claude Agent SDK logo
divider

Introduction

This guide walks you through connecting Alchemy to the Claude Agent SDK 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 Claude Agent SDK 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

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Alchemy
  • Configure an AI agent that can use Alchemy as a tool
  • Run a live chat session where you can ask the agent to perform Alchemy operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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 & Triggers

Tools
Compute NFT RarityTool to compute the rarity of each attribute for a specific NFT based on its collection.
Get NFT Collection MetadataTool to get metadata for an NFT collection using its marketplace slug (OpenSea, LooksRare, etc).
Get Collections for OwnerTool to retrieve all NFT collections held by a specified owner address.
Get Contract Metadata Batch V3Tool to retrieve metadata for multiple NFT contracts in a single batch request.
Get Contract Metadata V3Tool to get the metadata for an NFT contract including name, symbol, total supply, and token type (ERC721/ERC1155).
Get Contracts for Owner (NFT API v3)Tool to get all NFT contracts owned by an address with contract metadata.
Get NFT Floor PriceTool to get the floor price for an NFT collection across multiple marketplaces (OpenSea, LooksRare, etc).
Get Historical Token PricesRetrieves historical price data for a token over a specified time range with configurable intervals.
Get NFT Contracts By AddressTool to retrieve NFT contracts associated with one or more wallet addresses across multiple blockchain networks.
Get NFT MetadataTool to retrieve comprehensive metadata for a specific NFT, including contract details, media URLs, attributes, ownership info, and OpenSea data.
Get NFT Metadata BatchTool to retrieve metadata for multiple NFTs in a single request (up to 100 NFTs), including contract details, media URLs, attributes, and collection data.
Get NFT Sales V3Retrieves NFT sales that have occurred through on-chain marketplaces using Alchemy's v3 API.
Get NFTs for Collection V3Retrieves all NFTs in a collection using OpenSea collection slug or contract address.
Get NFTs for ContractRetrieves all NFTs for a given NFT contract address.
Get NFTs for OwnerTool to get all NFTs currently owned by a given address.
Get Owners for CollectionTool to retrieve all owner addresses for a given NFT collection contract.
Get Owners for ContractTool to get all owners of NFTs in a contract with optional token balances.
Get NFT Owners (v3)Tool to retrieve all owners for a specific NFT using Alchemy's v3 API.
Get Portfolio NFTs By AddressTool to fetch NFTs owned by multiple wallet addresses across different blockchain networks.
Get Token Prices By SymbolTool to get current token prices by symbol (e.
Get Token BalancesThis tool retrieves ERC20 token balances for a specified Ethereum address.
Get Token Balances By AddressTool to get token balances for wallet addresses across multiple networks using Alchemy's Portfolio API.
Get Token MetadataRetrieves metadata for an ERC-20 token on Ethereum mainnet, including its name, symbol, decimals, and logo URL.
Get Token Prices By AddressRetrieves current token prices by contract address and network from decentralized exchanges (DEXes).
Get Tokens By AddressTool to fetch fungible tokens (native, ERC-20, SPL) for multiple wallet addresses across networks.
Get Transaction CountThis tool retrieves the number of transactions sent from a specific address (also known as the nonce).
Get Transactions History By AddressTool to get transaction history for wallet addresses across multiple networks using Alchemy's Data API.
Invalidate NFT Contract CacheTool to invalidate the cached metadata for an NFT contract.
Check If NFT Is AirdropTool to check if a specific NFT token is marked as an airdrop.
Check If NFT Is AirdropTool to determine whether an NFT was airdropped to the owner address.
Check Collection OwnershipTool to check if a wallet address owns any token from a specific NFT collection.
Check NFT Holder StatusTool to check if a wallet address holds any NFTs from a specific contract.
Check if Contract is SpamTool to check if an NFT contract is marked as spam by Alchemy.
Check if Contract is Spam (V3)Tool to determine if a specific NFT contract is marked as spam by Alchemy.
Search NFT Contract MetadataTool to search for keywords across metadata of all ERC-721 and ERC-1155 smart contracts.
Summarize NFT AttributesRetrieves a comprehensive summary of all attributes and traits for NFTs in a collection, including trait counts and distribution statistics.

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

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

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

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Alchemy account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Alchemy functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Alchemy
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["alchemy"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Alchemy
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Alchemy tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Alchemy
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Alchemy and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Alchemy
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["alchemy"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Alchemy tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

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

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Alchemy through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Alchemy MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Alchemy MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Alchemy MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Alchemy MCP with Claude Cowork

Codex logo

Codex

Use Alchemy MCP with Codex

OpenClaw logo

OpenClaw

Use Alchemy MCP with OpenClaw

Hermes logo

Hermes

Use Alchemy MCP with Hermes

CLI logo

CLI

Use Alchemy MCP with CLI

Google ADK logo

Google ADK

Use Alchemy MCP with Google ADK

LangChain logo

LangChain

Use Alchemy MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Alchemy MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Alchemy MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Alchemy MCP with LlamaIndex

CrewAI logo

CrewAI

Use Alchemy MCP with CrewAI

FAQ

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 Claude Agent SDK?

Yes, you can. Claude Agent SDK 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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗