# How to integrate Openrouter MCP with Autogen

```json
{
  "title": "How to integrate Openrouter MCP with Autogen",
  "toolkit": "Openrouter",
  "toolkit_slug": "openrouter",
  "framework": "AutoGen",
  "framework_slug": "autogen",
  "url": "https://composio.dev/toolkits/openrouter/framework/autogen",
  "markdown_url": "https://composio.dev/toolkits/openrouter/framework/autogen.md",
  "updated_at": "2026-05-12T10:20:56.035Z"
}
```

## Introduction

This guide walks you through connecting Openrouter to AutoGen using the Composio tool router. By the end, you'll have a working Openrouter agent that can generate python code from this prompt, summarize this article using claude-3, list all available llama-3 model endpoints through natural language commands.
This guide will help you understand how to give your AutoGen 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

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

## 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 Openrouter
- Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams
- Configure an Autogen AssistantAgent that can call Openrouter tools
- Run a live chat loop where you ask the agent to perform Openrouter 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 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.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `OPENROUTER_CREATE_CHAT_COMPLETION` | Create Chat Completion | Tool to generate a chat-style completion. Use after assembling messages and selecting a model. Supports streaming and function calls. Response format varies across models; use explicit prompt instructions to standardize output. Provider-level rate limits and moderation policies differ per model. |
| `OPENROUTER_CREATE_COINBASE_CHARGE` | Create Coinbase Charge | Tool to create a Coinbase charge for crypto payment to add credits to your OpenRouter account. Use when you need to purchase credits using cryptocurrency. Returns calldata needed to fulfill the transaction on the specified blockchain. |
| `OPENROUTER_CREATE_MESSAGE` | Create Message (Anthropic Format) | Tool to create a message using Anthropic Messages API format via OpenRouter. Use when you need Claude-compatible chat completion with support for text, images, PDFs, tools, and extended thinking. |
| `OPENROUTER_GET_CREDITS` | Get Credits | Tool to get the current API credit balance for the authenticated user. Use before large or batch jobs to verify sufficient balance. A successful response may return total_credits=0, which confirms authentication but will cause all paid model generations to fail. Avoid polling this endpoint; call only as needed. |
| `OPENROUTER_GET_CURRENT_KEY` | Get Current Key | Tool to get information about the currently authenticated API key. Use to check usage limits, spending, and key metadata. |
| `OPENROUTER_GET_GENERATION` | Get Generation | Tool to retrieve a generation result by its unique ID. Use after a generation completes to fetch metadata like token counts, cost, and latency. |
| `OPENROUTER_GET_MODELS_COUNT` | Get Models Count | Tool to get the total count of available models on OpenRouter. Use when you need to know how many models are available without fetching the full list. |
| `OPENROUTER_LIST_AVAILABLE_MODELS` | List Available Models | Tool to list available models via OpenRouter API. Use after confirming authentication to fetch the model catalog. Use exact model IDs returned here in OPENROUTER_CREATE_CHAT_COMPLETION or OPENROUTER_CREATE_COMPLETION calls — hard-coded IDs may break when the catalog changes. Use exact author and slug values from this response as inputs to OPENROUTER_LIST_MODEL_ENDPOINTS. Models have varying capabilities (e.g., tools, reasoning); verify individual model capabilities before downstream use. Pricing and latency metadata may be null or approximate — handle missing values in routing logic. |
| `OPENROUTER_LIST_EMBEDDING_MODELS` | List Embedding Models | Tool to list all available embeddings models via OpenRouter API. Returns a list of embeddings models with their properties including architecture, pricing, and capabilities. |
| `OPENROUTER_LIST_MODEL_ENDPOINTS` | OpenRouter List Model Endpoints | Tool to list endpoints for a specific model. Use after specifying model author and slug to get endpoint details including pricing, context length, and supported parameters. Some metadata fields (e.g., latency, pricing) may be null or approximate; handle missing values in routing logic. |
| `OPENROUTER_LIST_PROVIDERS` | OpenRouter List Providers | Tool to list all AI model providers available through the OpenRouter API. Use after authentication to retrieve available provider options for routing configuration. Providers differ in latency, context window sizes, and rate limits — switching providers affects these constraints. Newly added providers may not appear immediately due to catalog propagation delays. |
| `OPENROUTER_LIST_USER_MODELS` | List User Models | Tool to list models filtered by user provider preferences, privacy settings, and guardrails. Use after authenticating to get models tailored to the user's configuration. |
| `OPENROUTER_LIST_ZDR_ENDPOINTS` | OpenRouter List ZDR Endpoints | Tool to preview the impact of Zero Data Retention (ZDR) on the available endpoints. Use to see which model endpoints remain accessible when ZDR is enabled. |

## Supported Triggers

None listed.

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

The Openrouter MCP server is an implementation of the Model Context Protocol that connects your AI agents and assistants directly to Openrouter. Instead of manually wiring Openrouter APIs, OAuth, and scopes yourself, you get a structured, tool-based interface that an LLM can call safely.
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

You will need:
- A Composio API key
- An OpenAI API key (used by Autogen's OpenAIChatCompletionClient)
- A Openrouter account you can connect to Composio
- Some basic familiarity with Autogen and Python async

### 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

Install Composio, Autogen extensions, and dotenv.
What's happening:
- composio connects your agent to Openrouter via MCP
- autogen-agentchat provides the AssistantAgent class
- autogen-ext-openai provides the OpenAI model client
- autogen-ext-tools provides MCP workbench support
```bash
pip install composio python-dotenv
pip install autogen-agentchat autogen-ext-openai autogen-ext-tools
```

### 3. Set up environment variables

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 Openrouter connections to use
```bash
COMPOSIO_API_KEY=your-composio-api-key
OPENAI_API_KEY=your-openai-api-key
USER_ID=your-user-identifier@example.com
```

### 4. Import dependencies and create Tool Router session

What's happening:
- load_dotenv() reads your .env file
- Composio(api_key=...) initializes the SDK
- create(...) creates a Tool Router session that exposes Openrouter tools
- session.mcp.url is the MCP endpoint that Autogen will connect to
```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 Openrouter session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["openrouter"]
    )
    url = session.mcp.url
```

### 5. Configure MCP parameters for Autogen

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
```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")}
)
```

### 6. Create the model client and agent

What's happening:
- OpenAIChatCompletionClient wraps the OpenAI model for Autogen
- McpWorkbench connects the agent to the MCP tools
- AssistantAgent is configured with the Openrouter tools from the workbench
```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 Openrouter assistant agent with MCP tools
    agent = AssistantAgent(
        name="openrouter_assistant",
        description="An AI assistant that helps with Openrouter operations.",
        model_client=model_client,
        workbench=workbench,
        model_client_stream=True,
        max_tool_iterations=10
    )
```

### 7. Run the interactive chat loop

What's happening:
- The script prompts you in a loop with You:
- Autogen passes your input to the model, which decides which Openrouter 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
```python
print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Openrouter 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")
```

## Complete Code

```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 Openrouter session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["openrouter"]
    )
    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 Openrouter assistant agent with MCP tools
        agent = AssistantAgent(
            name="openrouter_assistant",
            description="An AI assistant that helps with Openrouter 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 Openrouter 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 Openrouter 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 Openrouter, you can reuse the same structure for other MCP-enabled apps with minimal code changes.

## How to build Openrouter MCP Agent with another framework

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

## Related Toolkits

- [Composio](https://composio.dev/toolkits/composio) - Composio is an integration platform that connects AI agents with hundreds of business tools. It streamlines authentication and lets you trigger actions across services—no custom code needed.
- [Composio search](https://composio.dev/toolkits/composio_search) - Composio search is a unified web search toolkit spanning travel, e-commerce, news, financial markets, images, and more. It lets you and your apps tap into up-to-date web data from a single, easy-to-integrate service.
- [Perplexityai](https://composio.dev/toolkits/perplexityai) - Perplexityai delivers natural, conversational AI models for generating human-like text. Instantly get context-aware, high-quality responses for chat, search, or complex workflows.
- [Browser tool](https://composio.dev/toolkits/browser_tool) - Browser tool is a virtual browser integration that lets AI agents interact with the web programmatically. It enables automated browsing, scraping, and action-taking from any AI workflow.
- [Ai ml api](https://composio.dev/toolkits/ai_ml_api) - Ai ml api is a suite of AI/ML models for natural language and image tasks. It provides fast, scalable access to advanced AI capabilities for your apps and workflows.
- [Aivoov](https://composio.dev/toolkits/aivoov) - Aivoov is an AI-powered text-to-speech platform offering 1,000+ voices in over 150 languages. Instantly turn written content into natural, human-like audio for any application.
- [All images ai](https://composio.dev/toolkits/all_images_ai) - All-Images.ai is an AI-powered image generation and management platform. It helps you create, search, and organize images effortlessly with advanced AI capabilities.
- [Anthropic administrator](https://composio.dev/toolkits/anthropic_administrator) - Anthropic administrator is an API for managing Anthropic organizational resources like members, workspaces, and API keys. It helps you automate admin tasks and streamline resource management across your Anthropic organization.
- [Api labz](https://composio.dev/toolkits/api_labz) - Api labz is a platform offering a suite of AI-driven APIs and workflow tools. It helps developers automate tasks and build smarter, more efficient applications.
- [Apipie ai](https://composio.dev/toolkits/apipie_ai) - Apipie ai is an AI model aggregator offering a single API for accessing top AI models from multiple providers. It helps developers build cost-efficient, latency-optimized AI solutions without juggling multiple integrations.
- [Astica ai](https://composio.dev/toolkits/astica_ai) - Astica ai provides APIs for computer vision, NLP, and voice synthesis. Integrate advanced AI features into your app with a single API key.
- [Bigml](https://composio.dev/toolkits/bigml) - BigML is a machine learning platform that lets you build, train, and deploy predictive models from your data. Its intuitive interface and robust API make machine learning accessible and efficient.
- [Botbaba](https://composio.dev/toolkits/botbaba) - Botbaba is a platform for building, managing, and deploying conversational AI chatbots across messaging channels. It streamlines chatbot automation, making it easier to integrate AI into customer interactions.
- [Botpress](https://composio.dev/toolkits/botpress) - Botpress is an open-source platform for building, deploying, and managing chatbots. It helps teams automate conversations and deliver rich, interactive messaging experiences.
- [Chatbotkit](https://composio.dev/toolkits/chatbotkit) - Chatbotkit is a platform for building and managing AI-powered chatbots using robust APIs and SDKs. It lets you easily add conversational AI to your apps for better user engagement.
- [Cody](https://composio.dev/toolkits/cody) - Cody is an AI assistant built for businesses, trained on your company's knowledge and data. It delivers instant answers and insights, tailored for your team.
- [Context7 MCP](https://composio.dev/toolkits/context7_mcp) - Context7 MCP delivers live, version-specific code docs and examples right from the source. It helps developers and AI agents instantly retrieve authoritative programming info—no more out-of-date docs.
- [Customgpt](https://composio.dev/toolkits/customgpt) - CustomGPT.ai lets you build and deploy chatbots tailored to your own data and business needs. Get precise and context-aware AI conversations without writing code.
- [Datarobot](https://composio.dev/toolkits/datarobot) - Datarobot is a machine learning platform that automates model development, deployment, and monitoring. It empowers organizations to quickly gain predictive insights from large datasets.
- [Deepgram](https://composio.dev/toolkits/deepgram) - Deepgram is an AI-powered speech recognition platform for accurate audio transcription and understanding. It enables fast, scalable speech-to-text with advanced audio intelligence features.

## Frequently Asked Questions

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

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.

### 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 Openrouter tools.

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

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.

### 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 Openrouter data and credentials are handled as safely as possible.

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