How to integrate Alchemy MCP with LlamaIndex

This guide walks you through connecting Alchemy to LlamaIndex 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 LlamaIndex 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.

Alchemy logoAlchemy
Api Key

Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure.

36 Tools

Introduction

This guide walks you through connecting Alchemy to LlamaIndex 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 LlamaIndex 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:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Alchemy
  • Connect LlamaIndex to the Alchemy MCP server
  • Build a Alchemy-powered agent using LlamaIndex
  • Interact with Alchemy through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

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.

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

Step by step10 STEPS
1

Prerequisites

Before you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Alchemy account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Alchemy

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Alchemy access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called alchemy_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["alchemy"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Alchemy actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, alchemy)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Alchemy tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Alchemy
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Alchemy tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Alchemy
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Alchemy, then start asking questions.

Complete Code

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

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["alchemy"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Alchemy actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Alchemy to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Alchemy tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
TOOLS

Supported Tools

Every Alchemy action and event your agent gets out of the box.

Compute NFT Rarity

Tool to compute the rarity of each attribute for a specific NFT based on its collection.

Get NFT Collection Metadata

Tool to get metadata for an NFT collection using its marketplace slug (OpenSea, LooksRare, etc).

Get Collections for Owner

Tool to retrieve all NFT collections held by a specified owner address.

Get Contract Metadata Batch V3

Tool to retrieve metadata for multiple NFT contracts in a single batch request.

Get Contract Metadata V3

Tool 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 Price

Tool to get the floor price for an NFT collection across multiple marketplaces (OpenSea, LooksRare, etc).

Get Historical Token Prices

Retrieves historical price data for a token over a specified time range with configurable intervals.

Get NFT Contracts By Address

Tool to retrieve NFT contracts associated with one or more wallet addresses across multiple blockchain networks.

Get NFT Metadata

Tool to retrieve comprehensive metadata for a specific NFT, including contract details, media URLs, attributes, ownership info, and OpenSea data.

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.

Get NFT Sales V3

Retrieves NFT sales that have occurred through on-chain marketplaces using Alchemy's v3 API.

Get NFTs for Collection V3

Retrieves all NFTs in a collection using OpenSea collection slug or contract address.

Get NFTs for Contract

Retrieves all NFTs for a given NFT contract address.

Get NFTs for Owner

Tool to get all NFTs currently owned by a given address.

Get Owners for Collection

Tool to retrieve all owner addresses for a given NFT collection contract.

Get Owners for Contract

Tool 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 Address

Tool to fetch NFTs owned by multiple wallet addresses across different blockchain networks.

Get Token Prices By Symbol

Tool to get current token prices by symbol (e.

Get Token Balances

This tool retrieves ERC20 token balances for a specified Ethereum address.

Get Token Balances By Address

Tool to get token balances for wallet addresses across multiple networks using Alchemy's Portfolio API.

Get Token Metadata

Retrieves metadata for an ERC-20 token on Ethereum mainnet, including its name, symbol, decimals, and logo URL.

Get Token Prices By Address

Retrieves current token prices by contract address and network from decentralized exchanges (DEXes).

Get Tokens By Address

Tool to fetch fungible tokens (native, ERC-20, SPL) for multiple wallet addresses across networks.

Get Transaction Count

This tool retrieves the number of transactions sent from a specific address (also known as the nonce).

Get Transactions History By Address

Tool to get transaction history for wallet addresses across multiple networks using Alchemy's Data API.

Invalidate NFT Contract Cache

Tool to invalidate the cached metadata for an NFT contract.

Check If NFT Is Airdrop

Tool to check if a specific NFT token is marked as an airdrop.

Check If NFT Is Airdrop

Tool to determine whether an NFT was airdropped to the owner address.

Check Collection Ownership

Tool to check if a wallet address owns any token from a specific NFT collection.

Check NFT Holder Status

Tool to check if a wallet address holds any NFTs from a specific contract.

Check if Contract is Spam

Tool 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 Metadata

Tool to search for keywords across metadata of all ERC-721 and ERC-1155 smart contracts.

Summarize NFT Attributes

Retrieves a comprehensive summary of all attributes and traits for NFTs in a collection, including trait counts and distribution statistics.

FAQ

Frequently asked questions

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.

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

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.

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.

Start with Alchemy.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Alchemy tool your agent needs.Free to start.

Start building