SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Openrouter MCP with LlamaIndex

Connect LlamaIndex to Openrouter MCP. Generate python code from this prompt, summarize this article using claude-3, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Openrouter logoOpenrouter
Api Key

OpenRouter is a unified API platform for accessing language models from various providers. It lets you easily integrate and switch between multiple LLMs with a single API.

122 Tools

Introduction

This guide walks you through connecting Openrouter to LlamaIndex using the Composio tool router. By the end, you'll have a working Openrouter agent that can chat with models from many providers, create embeddings, generate speech and video, rerank content, and check your credits through natural language commands.

This guide will help you understand how to give your LlamaIndex agent real control over a Openrouter account through Composio's Openrouter MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Openrouter with

Claude CodeCursorChatGPTClaude CoworkAntigravityOpenAI Agents SDKClaude Agent SDKCodexKimi CodeGrok BuildVS CodeOpenCodeOpenClawHermesAtomic AgentCLIGoogle ADKLangChainVercel AI SDKMastra AICrewAIPydantic AIAutoGen

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 Openrouter
  • Connect LlamaIndex to the Openrouter MCP server
  • Build a Openrouter-powered agent using LlamaIndex
  • Interact with Openrouter 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 Openrouter MCP server, and what's possible with it?

The Openrouter MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Openrouter account. It provides structured and secure access to a wide range of large language models, so your agent can generate completions, manage model access, check credits, and retrieve generation details seamlessly on your behalf.

  • Unified model completions: Let your agent generate chat-based or text completions using any model available through Openrouter, perfect for conversation or content creation tasks.
  • Model catalog and provider discovery: Ask your agent to list all available AI models and providers, helping you compare capabilities, endpoints, and pricing in real time.
  • Credit monitoring and usage tracking: Have your agent fetch your current API credit balance, so you always know your usage limits before starting new tasks.
  • Generation result retrieval: Direct your agent to pull detailed metadata for any previous generation, including token counts, costs, and latency for analysis or auditing.
  • Endpoint and configuration info: Empower your agent to fetch the latest model endpoints and supported parameters, making it easy to fine-tune routing and optimize performance.

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 Openrouter account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Openrouter

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 Openrouter 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 openrouter_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: ["openrouter"],
    },
  );

  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 Openrouter 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, openrouter)
  • 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 Openrouter 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 Openrouter
  • 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 Openrouter 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 Openrouter
10

Run the agent

npx ts-node llamaindex-agent.ts

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

Complete Code

Here's the complete code to get you started with Openrouter 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: ["openrouter"],
    },
  );

  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 Openrouter 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 Openrouter to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Openrouter 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 Openrouter action and event your agent gets out of the box.

Activate a validated private endpoint

Make a validated draft routable.

Bulk add members to a workspace

Add multiple organization members to a workspace.

Bulk assign keys to a guardrail

Assign multiple API keys to a specific guardrail.

Bulk assign members to a guardrail

Assign multiple organization members to a specific guardrail.

Bulk remove members from a workspace

Remove multiple members from a workspace.

Bulk unassign keys from a guardrail

Unassign multiple API keys from a specific guardrail.

Bulk unassign members from a guardrail

Unassign multiple organization members from a specific guardrail.

Create a new API key

Create a new API key for the authenticated user.

Create authorization code

Create an authorization code for the PKCE flow to generate a user-controlled API key

Create a batch

Creates a batch of requests that run asynchronously against a single endpoint (`/v1/chat/completions`, `/v1/responses`, `/v1/messages`, `/v1/embeddings`).

Create a BYOK provider credential

Create a new bring-your-own-key (BYOK) provider credential.

Create Chat Completion

Generate a chat-style completion from messages and a selected model, with function-call request options.

Create Coinbase Charge

Tool to create a Coinbase charge for crypto payment to add credits to your OpenRouter account.

Create Embeddings

Create vector embeddings for text, token, or multimodal inputs.

Create a guardrail

Create a new guardrail for the authenticated user.

Create Message (Anthropic Format)

Create a message using Anthropic Messages API format via OpenRouter, with text, image, PDF, tool, and extended-thinking request options.

Create an observability destination

Create a new observability destination.

Create a preset from a chat-completions request body

Creates a preset (or a new version of an existing one) from an inference request body.

Create a preset from a messages request body

Creates a preset (or a new version of an existing one) from an inference request body.

Create a preset from a responses request body

Creates a preset (or a new version of an existing one) from an inference request body.

Create a private endpoint

Create a private endpoint as a draft.

Create a SCIM group mapping

Create a SCIM group-to-workspace role mapping.

Start a SCIM directory sync

Start a SCIM directory sync.

Create Speech

Synthesize speech from text or multi-speaker turns.

Create Transcription

Transcribe audio into text using an OpenRouter speech-to-text model.

Create Video Generation

Submit an asynchronous video generation job to OpenRouter.

Create a workspace

Create a new workspace for the authenticated user.

Delete an API key

Delete one of the authenticated account's own API keys, revoking the selected key's access.

Delete a batch

Deletes a batch in a terminal status (`completed`, `failed`, `expired`, or `cancelled`) and its stored requests and results.

Delete a BYOK provider credential

Delete (soft-delete) a bring-your-own-key (BYOK) provider credential by its `id`.

Delete a file

Deletes a file owned by the requesting workspace.

Delete a guardrail

Delete an existing guardrail.

Delete an observability destination

Delete an existing observability destination.

Delete a private endpoint

Delete a private endpoint and stop routing to it.

Delete a SCIM group mapping

Delete a SCIM group-to-workspace mapping.

Delete a workspace

Delete an existing workspace.

Delete a workspace budget

Remove the budget for a given interval.

Disable a private endpoint

Stop routing to an active endpoint without deleting it.

Download Container File Content

Download raw file content from an OpenRouter container using its canonical container and file IDs.

Download File Content

Download raw content of a server-created file.

Enable a private endpoint

Resume routing to a disabled endpoint.

Exchange authorization code for API key

Exchange an authorization code from the PKCE flow for a user-controlled API key

Exchange a workload identity token

RFC 8693 token exchange.

Generate an image

Generates an image from a text prompt via the image generation router

Get available analytics metrics and dimensions

Returns the available metrics, dimensions, filter operators, and granularities for the analytics query endpoint.

Get a single API key

Get a single API key by hash.

Top apps by token usage

Returns the top public apps on OpenRouter ranked by token usage inside the requested date window, matching the public apps marketplace on openrouter.

Get a batch

Returns a batch with its status and request counts.

List Benchmarks

Unified benchmark endpoint that aggregates scores from multiple benchmark sources (Artificial Analysis, Design Arena, and OpenRouter's own tau-bench, GPQA, and web-search evals).

Get a BYOK provider credential

Get a single bring-your-own-key (BYOK) provider credential by its `id`.

Retrieve a container file

Returns the metadata of a single file in a container.

Get Credits

Tool to get the current API credit balance for the authenticated user.

Get Current Key

Tool to get information about the currently authenticated API key.

Get file metadata

Retrieves metadata for a single file owned by the requesting workspace.

Get Generation

Tool to retrieve a generation result by its unique ID.

Get a guardrail

Get a single guardrail by ID.

Get a model by its slug

Returns full details for a single model identified by its author and slug (e.

Get Models Count

Tool to get the total count of available models on OpenRouter.

OpenRouter access token signing keys

RFC 7517 JWK Set containing the public keys OpenRouter signs access tokens with.

Get an observability destination

Fetch a single observability destination by its UUID.

Get organization settings

Get the settings of the organization associated with the authenticated management key.

Get a preset

Retrieves a preset by its slug with its currently designated version inline.

Get a specific version of a preset

Retrieves a specific version of a preset by its slug and version number.

Get a private endpoint

Get one private endpoint with its upstream configuration and current pricing.

Daily token totals for top 50 models

Returns the top 50 public models per day by total token usage on OpenRouter, plus a single aggregated `other` row per day that sums every model outside that top 50.

Get a SCIM group mapping

Get a SCIM group-to-workspace mapping.

Get SCIM directory sync status

Get SCIM directory sync status.

Cost per session by harness and model

Returns weekly refreshed, aggregated cost-per-session cells for the published harnesses.

Task classification market share

Returns the market-share breakdown of OpenRouter traffic by task classification (e.

Get a server tool

One server tool by canonical name or any accepted alias, with the models that run it natively.

Get user activity grouped by endpoint

Returns user activity data grouped by endpoint for the last 30 (completed) UTC days.

Get Video Content

Download one output from a completed OpenRouter video generation job.

Get Video Generation

Poll a video generation job for its status, outputs, and usage.

Get a workspace

Get a single workspace by ID or slug.

Get a workspace budget

Retrieve the budget for a given interval.

List API keys

List all API keys for the authenticated user.

List Available Models

List available OpenRouter models, optionally filtered by category.

List batches

Lists batches in the workspace of the authenticating API key, newest first.

List BYOK provider credentials

List the bring-your-own-key (BYOK) provider credentials for the authenticated entity's default workspace.

List container files

Lists the files in a container, in lexicographic path order.

List Embedding Models

List available OpenRouter embedding models with properties including architecture, pricing, and capabilities.

List files

Lists files belonging to the workspace of the authenticating API key.

Get stored prompt, completion, and error content for a generation

Get stored prompt, completion, and error content for a generation

List key assignments for a guardrail

List all API key assignments for a specific guardrail.

List member assignments for a guardrail

List all organization member assignments for a specific guardrail.

List guardrails

List all guardrails for the authenticated user.

List endpoints for an image model

Returns the full per-endpoint records for an image model: each endpoint's definitive supported parameters, pricing, and passthrough allowlist.

List image generation models

Lists every image generation model with its top-level supported-parameter superset and a URL to its full per-endpoint records.

List all key assignments

List all API key guardrail assignments for the authenticated user.

List all member assignments

List all organization member guardrail assignments for the authenticated user.

OpenRouter List Model Endpoints

Tool to list endpoints for a specific model.

List observability destinations

List the observability destinations configured for the authenticated entity's default workspace.

List organization members

List all members of the organization associated with the authenticated management key.

List presets

Lists all presets for the authenticated user, ordered by most recently updated first.

List versions of a preset

Lists all versions of a preset, ordered by version number ascending (oldest first).

List private endpoints

List the organization's private endpoints, including drafts.

OpenRouter List Providers

Tool to list all AI model providers available through the OpenRouter API.

List SCIM group mappings

List SCIM group-to-workspace mappings for the organization.

List SCIM groups

List SCIM groups for the organization.

List server tools

Lists every server tool OpenRouter can run on behalf of a model: accepted `tools[].

List User Models

List models filtered by user provider preferences, privacy settings, and guardrails.

List Video Models

List video generation models and their supported capabilities.

List workspace budgets

List all budgets configured for a workspace.

List workspace members

List all members of a workspace.

List workspaces

List all workspaces for the authenticated user.

OpenRouter List ZDR Endpoints

Tool to preview the impact of Zero Data Retention (ZDR) on the available endpoints.

Promote a container file into workspace documents

Copies a file from the container's sandbox prefix into the workspace's durable document storage, so it outlives the container.

Query analytics data

Execute an analytics query with specified metrics, dimensions, filters, and time range.

Rerank Content

Rank text or multimodal documents by relevance to a query.

Submit feedback for a generation

Submit structured feedback on a generation the authenticated user made.

Submit a System One request

Sends state and typed questions to a System One model such as Jev and returns its answers.

Update an API key

Update one of the authenticated account's own API keys.

Update a BYOK provider credential

Update an existing bring-your-own-key (BYOK) provider credential by its `id`.

Update a guardrail

Update an existing guardrail, or materialize an unconfigured workspace default guardrail.

Update an observability destination

Update an existing observability destination.

Update organization settings

Update the settings of the organization associated with the authenticated management key.

Update a private endpoint

Change any of the endpoint fields you own in one call; only the fields present change, and the response is the whole endpoint.

Update a SCIM group mapping

Update a SCIM group mapping role.

Update a workspace

Update an existing workspace by ID or slug.

Upload File

Upload a file for future API calls under the authenticating key's workspace.

Create or update a workspace budget

Create or update the budget for a given interval.

Validate a draft private endpoint

Send a live test request to the draft endpoint using the given workspace's BYOK credential for its provider.

FRAMEWORKS

How to build Openrouter MCP Agent with another framework

Claude Code logo

Claude Code

Use Openrouter MCP with Claude Code

Cursor logo

Cursor

Use Openrouter MCP with Cursor

ChatGPT logo

ChatGPT

Use Openrouter MCP with ChatGPT

Claude Cowork logo

Claude Cowork

Use Openrouter MCP with Claude Cowork

Antigravity logo

Antigravity

Use Openrouter MCP with Antigravity

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Openrouter MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Openrouter MCP with Claude Agent SDK

Codex logo

Codex

Use Openrouter MCP with Codex

Kimi Code logo

Kimi Code

Use Openrouter MCP with Kimi Code

Grok Build logo

Grok Build

Use Openrouter MCP with Grok Build

VS Code logo

VS Code

Use Openrouter MCP with VS Code

OpenCode logo

OpenCode

Use Openrouter MCP with OpenCode

OpenClaw logo

OpenClaw

Use Openrouter MCP with OpenClaw

Hermes logo

Hermes

Use Openrouter MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Openrouter MCP with Atomic Agent

CLI logo

CLI

Use Openrouter MCP with CLI

Google ADK logo

Google ADK

Use Openrouter MCP with Google ADK

LangChain logo

LangChain

Use Openrouter MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Openrouter MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Openrouter MCP with Mastra AI

CrewAI logo

CrewAI

Use Openrouter MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Openrouter MCP with Pydantic AI

AutoGen logo

AutoGen

Use Openrouter MCP with AutoGen

FAQ

Frequently asked questions

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

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

Start with Openrouter.It takes 30 seconds.

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

Start building