# How to integrate E2b MCP with Autogen ```json { "title": "How to integrate E2b MCP with Autogen", "toolkit": "E2b", "toolkit_slug": "e2b", "framework": "AutoGen", "framework_slug": "autogen", "url": "https://composio.dev/toolkits/e2b/framework/autogen", "markdown_url": "https://composio.dev/toolkits/e2b/framework/autogen.md", "updated_at": "2026-03-29T06:31:50.255Z" } ``` ## Introduction This guide walks you through connecting E2b to AutoGen using the Composio tool router. By the end, you'll have a working E2b agent that can run a python script to analyze csv data, execute javascript code to validate user input, start a sandbox and list installed packages through natural language commands. This guide will help you understand how to give your AutoGen agent real control over a E2b account through Composio's E2b MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate E2b with - [ChatGPT](https://composio.dev/toolkits/e2b/framework/chatgpt) - [Antigravity](https://composio.dev/toolkits/e2b/framework/antigravity) - [OpenAI Agents SDK](https://composio.dev/toolkits/e2b/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/e2b/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/e2b/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/e2b/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/e2b/framework/codex) - [Cursor](https://composio.dev/toolkits/e2b/framework/cursor) - [VS Code](https://composio.dev/toolkits/e2b/framework/vscode) - [OpenCode](https://composio.dev/toolkits/e2b/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/e2b/framework/openclaw) - [Hermes](https://composio.dev/toolkits/e2b/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/e2b/framework/cli) - [Google ADK](https://composio.dev/toolkits/e2b/framework/google-adk) - [LangChain](https://composio.dev/toolkits/e2b/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/e2b/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/e2b/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/e2b/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/e2b/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 E2b - Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams - Configure an Autogen AssistantAgent that can call E2b tools - Run a live chat loop where you ask the agent to perform E2b 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 E2b MCP server, and what's possible with it? The E2b MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your E2b account. It provides structured and secure access so your agent can perform E2b operations on your behalf. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `E2B_CONNECT_SANDBOX` | Connect to Sandbox | Tool to connect to an existing E2B sandbox and retrieve its details. Use when you need to reconnect to a sandbox from different environments or resume a paused sandbox. The TTL is extended upon connection. | | `E2B_CREATE_TEMPLATE` | Create Template | Tool to create a new E2B template with specified configuration. Use when you need to define a new sandbox template that can be used to spawn sandbox environments. | | `E2B_CREATE_WEBHOOK` | Create Webhook | Tool to register a new webhook to receive sandbox lifecycle events for the team. Use when you need to set up notifications for sandbox lifecycle events such as creation, updates, or termination. | | `E2B_DELETE_SANDBOXES` | Delete Sandbox | Tool to terminate and permanently delete a running E2B sandbox instance. Use when you need to kill a sandbox that is no longer needed. Once terminated, the sandbox cannot be resumed. | | `E2B_DELETE_WEBHOOK` | Delete Webhook | Tool to unregister a webhook and stop receiving lifecycle events. Use when you need to remove a webhook that is no longer needed or to clean up webhook registrations. | | `E2B_CHECK_API_HEALTH` | Check API Health | Tool to check the health status of the E2B API. Use when you need to verify that the API service is operational and accessible. | | `E2B_GET_SANDBOX` | Get Sandbox | Tool to retrieve detailed information about a specific sandbox by its ID. Use when you need to check sandbox status, metadata, or configuration details. | | `E2B_GET_SANDBOX_LOGS` | Get Sandbox Logs | Tool to retrieve logs from a specific E2B sandbox instance. Use when you need to debug or monitor sandbox execution by viewing its console output and system logs. | | `E2B_GET_SANDBOX_LIFECYCLE_EVENTS` | Get Sandbox Lifecycle Events | Tool to retrieve the latest lifecycle events for a particular sandbox instance. Use when you need to track state changes including creation, pausing, resuming, updates, and termination of a sandbox. | | `E2B_GET_SANDBOX_METRICS` | Get Sandbox Metrics | Tool to retrieve timestamped CPU, memory, and disk usage metrics for a sandbox. Use when you need to monitor resource usage of a running sandbox. Metrics are collected every 5 seconds; returns empty array if no metrics available yet. | | `E2B_GET_TEAM_METRICS` | Get Team Metrics | Tool to retrieve timestamped CPU, memory, and disk usage metrics for a team. Use when you need to monitor aggregated resource usage across all sandboxes belonging to a team. | | `E2B_GET_TEAM_MAXIMUM_METRICS` | Get Team Maximum Metrics | Tool to retrieve the maximum value for a specific team metric in a given interval. Use when you need to check team limits or peak usage, such as maximum concurrent sandboxes allowed or highest resource usage. | | `E2B_GET_TEMPLATE_BUILD_STATUS` | Get Template Build Status | Tool to get the status of a template build. Use when you need to check the build status of a template that was started asynchronously. Useful in polling loops to monitor template builds in progress. | | `E2B_GET_TEMPLATE_FILES` | Get Template Files | Tool to get an upload link for a tar file containing build layer files. Use when you need to retrieve or download template build layer files by their hash. | | `E2B_GET_WEBHOOK_CONFIGURATION` | Get Webhook Configuration | Tool to retrieve the current webhook configuration for a specific webhook. Use when you need to inspect webhook settings, verify configuration, or check webhook status. | | `E2B_LIST_ALL_SANDBOXES` | List All Sandboxes | Tool to list all running and paused sandboxes associated with your team. Use when you need to view active sandboxes, monitor sandbox state, or retrieve sandbox identifiers for further operations. Supports pagination and filtering by state or metadata. | | `E2B_LIST_SANDBOXES_METRICS` | List Sandboxes Metrics | Tool to retrieve timestamped CPU, memory, and disk usage metrics for multiple sandboxes. Use when you need to monitor resource usage across multiple sandboxes simultaneously. Metrics are collected every 5 seconds; returns empty array if no metrics available yet. | | `E2B_LIST_TEAM_SANDBOX_LIFECYCLE_EVENTS` | List Team Sandbox Lifecycle Events | Tool to retrieve the latest lifecycle events across all sandboxes associated with the team. Use when you need to monitor sandbox activity, track lifecycle changes, or audit sandbox operations. | | `E2B_LIST_ALL_TEMPLATES` | List All Templates | Tool to list all available E2B templates for your team. Use when you need to view available templates, retrieve template identifiers, or audit template configurations. | | `E2B_LIST_ALL_WEBHOOKS` | List All Webhooks | Tool to retrieve all registered webhooks for your team. Use when you need to view all webhook configurations, audit webhook settings, or manage multiple webhooks. | | `E2B_PAUSE_SANDBOX` | Pause Sandbox | Tool to pause a running E2B sandbox preserving its filesystem and memory state. Use when you need to temporarily suspend a sandbox while maintaining its state for later resumption. Takes approximately 4 seconds per 1 GiB of RAM to pause. Paused sandboxes can be stored for up to 30 days. | | `E2B_CREATE_SANDBOX` | Create Sandbox | Tool to create a new E2B sandbox from a template. Use when you need to launch a fresh sandbox environment for code execution, testing, or development purposes. | | `E2B_SET_SANDBOX_TIMEOUT` | Set Sandbox Timeout | Tool to set the timeout for an E2B sandbox. Use when you need to extend or reduce the sandbox lifetime. The timeout is measured from the current time, and calling this multiple times overwrites the previous TTL. | | `E2B_REFRESH_SANDBOX` | Refresh Sandbox | Tool to refresh an E2B sandbox and extend its time to live. Use when you need to keep a sandbox alive longer and prevent it from timing out. | | `E2B_START_TEMPLATE_BUILD` | Start Template Build | Tool to start a build for an E2B template. Use when you need to initiate the build process for a template with specific configuration. The build runs asynchronously and returns immediately with a 202 Accepted status. | | `E2B_UPDATE_TEMPLATE` | Update Template | Tool to update an E2B template configuration. Use when you need to modify template settings such as changing visibility (public/private status). | | `E2B_UPDATE_WEBHOOK_CONFIGURATION` | Update Webhook Configuration | Tool to update an existing webhook configuration including URL, enabled status, and subscribed events. Use when you need to modify webhook settings, change the destination URL, enable/disable a webhook, or update event subscriptions. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The E2b MCP server is an implementation of the Model Context Protocol that connects your AI agents and assistants directly to E2b. Instead of manually wiring E2b 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 E2b 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 E2b 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 E2b 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 E2b 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 E2b session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["e2b"] ) 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 E2b 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 E2b assistant agent with MCP tools agent = AssistantAgent( name="e2b_assistant", description="An AI assistant that helps with E2b 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 E2b 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 E2b 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 E2b session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["e2b"] ) 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 E2b assistant agent with MCP tools agent = AssistantAgent( name="e2b_assistant", description="An AI assistant that helps with E2b 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 E2b 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 E2b 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 E2b, you can reuse the same structure for other MCP-enabled apps with minimal code changes. ## How to build E2b MCP Agent with another framework - [ChatGPT](https://composio.dev/toolkits/e2b/framework/chatgpt) - [Antigravity](https://composio.dev/toolkits/e2b/framework/antigravity) - [OpenAI Agents SDK](https://composio.dev/toolkits/e2b/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/e2b/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/e2b/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/e2b/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/e2b/framework/codex) - [Cursor](https://composio.dev/toolkits/e2b/framework/cursor) - [VS Code](https://composio.dev/toolkits/e2b/framework/vscode) - [OpenCode](https://composio.dev/toolkits/e2b/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/e2b/framework/openclaw) - [Hermes](https://composio.dev/toolkits/e2b/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/e2b/framework/cli) - [Google ADK](https://composio.dev/toolkits/e2b/framework/google-adk) - [LangChain](https://composio.dev/toolkits/e2b/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/e2b/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/e2b/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/e2b/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/e2b/framework/crew-ai) ## Related Toolkits - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [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. - [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms. - [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place. - [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. - [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences. - [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses. - [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. - [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure. - [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure. - [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. - [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction. - [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. - [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting. - [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. - [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and E2b MCP? With a standalone E2b MCP server, the agents and LLMs can only access a fixed set of E2b tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from E2b 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 E2b tools. ### Can I manage the permissions and scopes for E2b while using Tool Router? Yes, absolutely. You can configure which E2b 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 E2b data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)