How to integrate Alchemy MCP with Autogen

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

30 min · no commitment · see it on your stack

Alchemy logo
AutoGen logo
divider

Introduction

This guide walks you through connecting Alchemy to AutoGen 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 AutoGen 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 OpenAI and Composio API keys
  • Install the required dependencies for Autogen and Composio
  • Initialize Composio and create a Tool Router session for Alchemy
  • Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams
  • Configure an Autogen AssistantAgent that can call Alchemy tools
  • Run a live chat loop where you ask the agent to perform Alchemy operations

What is AutoGen?

Autogen is a framework for building multi-agent conversational AI systems from Microsoft. It enables you to create agents that can collaborate, use tools, and maintain complex workflows.

Key features include:

  • Multi-Agent Systems: Build collaborative agent workflows
  • MCP Workbench: Native support for Model Context Protocol tools
  • Streaming HTTP: Connect to external services through streamable HTTP
  • AssistantAgent: Pre-built agent class for tool-using assistants

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

You will need:

  • A Composio API key
  • An OpenAI API key (used by Autogen's OpenAIChatCompletionClient)
  • A Alchemy account you can connect to Composio
  • Some basic familiarity with Autogen and Python async

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard 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.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

bash
pip install composio python-dotenv
pip install autogen-agentchat autogen-ext-openai autogen-ext-tools

Install Composio, Autogen extensions, and dotenv.

What's happening:

  • composio connects your agent to Alchemy via MCP
  • autogen-agentchat provides the AssistantAgent class
  • autogen-ext-openai provides the OpenAI model client
  • autogen-ext-tools provides MCP workbench support

Set up environment variables

bash
COMPOSIO_API_KEY=your-composio-api-key
OPENAI_API_KEY=your-openai-api-key
USER_ID=your-user-identifier@example.com

Create a .env file in your project folder.

What's happening:

  • COMPOSIO_API_KEY is required to talk to Composio
  • OPENAI_API_KEY is used by Autogen's OpenAI client
  • USER_ID is how Composio identifies which user's Alchemy connections to use

Import dependencies and create Tool Router session

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

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Alchemy session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["alchemy"]
    )
    url = session.mcp.url
What's happening:
  • load_dotenv() reads your .env file
  • Composio(api_key=...) initializes the SDK
  • create(...) creates a Tool Router session that exposes Alchemy tools
  • session.mcp.url is the MCP endpoint that Autogen will connect to

Configure MCP parameters for Autogen

python
# Configure MCP server parameters for Streamable HTTP
server_params = StreamableHttpServerParams(
    url=url,
    timeout=30.0,
    sse_read_timeout=300.0,
    terminate_on_close=True,
    headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
)

Autogen expects parameters describing how to talk to the MCP server. That is what StreamableHttpServerParams is for.

What's happening:

  • url points to the Tool Router MCP endpoint from Composio
  • timeout is the HTTP timeout for requests
  • sse_read_timeout controls how long to wait when streaming responses
  • terminate_on_close=True cleans up the MCP server process when the workbench is closed

Create the model client and agent

python
# Create model client
model_client = OpenAIChatCompletionClient(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY")
)

# Use McpWorkbench as context manager
async with McpWorkbench(server_params) as workbench:
    # Create Alchemy assistant agent with MCP tools
    agent = AssistantAgent(
        name="alchemy_assistant",
        description="An AI assistant that helps with Alchemy operations.",
        model_client=model_client,
        workbench=workbench,
        model_client_stream=True,
        max_tool_iterations=10
    )

What's happening:

  • OpenAIChatCompletionClient wraps the OpenAI model for Autogen
  • McpWorkbench connects the agent to the MCP tools
  • AssistantAgent is configured with the Alchemy tools from the workbench

Run the interactive chat loop

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

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

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

    if not user_input:
        continue

    print("\nAgent is thinking...\n")

    # Run the agent with streaming
    try:
        response_text = ""
        async for message in agent.run_stream(task=user_input):
            if hasattr(message, "content") and message.content:
                response_text = message.content

        # Print the final response
        if response_text:
            print(f"Agent: {response_text}\n")
        else:
            print("Agent: I encountered an issue processing your request.\n")

    except Exception as e:
        print(f"Agent: Sorry, I encountered an error: {str(e)}\n")
What's happening:
  • The script prompts you in a loop with You:
  • Autogen passes your input to the model, which decides which Alchemy tools to call via MCP
  • agent.run_stream(...) yields streaming messages as the agent thinks and calls tools
  • Typing exit, quit, or bye ends the loop

Complete Code

Here's the complete code to get you started with Alchemy and AutoGen:

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

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Alchemy session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["alchemy"]
    )
    url = session.mcp.url

    # Configure MCP server parameters for Streamable HTTP
    server_params = StreamableHttpServerParams(
        url=url,
        timeout=30.0,
        sse_read_timeout=300.0,
        terminate_on_close=True,
        headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
    )

    # Create model client
    model_client = OpenAIChatCompletionClient(
        model="gpt-5",
        api_key=os.getenv("OPENAI_API_KEY")
    )

    # Use McpWorkbench as context manager
    async with McpWorkbench(server_params) as workbench:
        # Create Alchemy assistant agent with MCP tools
        agent = AssistantAgent(
            name="alchemy_assistant",
            description="An AI assistant that helps with Alchemy operations.",
            model_client=model_client,
            workbench=workbench,
            model_client_stream=True,
            max_tool_iterations=10
        )

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

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

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

            if not user_input:
                continue

            print("\nAgent is thinking...\n")

            # Run the agent with streaming
            try:
                response_text = ""
                async for message in agent.run_stream(task=user_input):
                    if hasattr(message, 'content') and message.content:
                        response_text = message.content

                # Print the final response
                if response_text:
                    print(f"Agent: {response_text}\n")
                else:
                    print("Agent: I encountered an issue processing your request.\n")

            except Exception as e:
                print(f"Agent: Sorry, I encountered an error: {str(e)}\n")

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

Conclusion

You now have an Autogen assistant wired into Alchemy through Composio's Tool Router and MCP. From here you can:
  • Add more toolkits to the toolkits list, for example notion or hubspot
  • Refine the agent description to point it at specific workflows
  • Wrap this script behind a UI, Slack bot, or internal tool
Once the pattern is clear for Alchemy, you can reuse the same structure for other MCP-enabled apps with minimal code changes.

How to build Alchemy MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Alchemy MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Alchemy MCP with Claude Agent 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 Autogen?

Yes, you can. Autogen 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↗