# How to integrate Emelia MCP with Autogen

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

## Introduction

This guide walks you through connecting Emelia to AutoGen using the Composio tool router. By the end, you'll have a working Emelia agent that can find email address for john doe at acme corp, add jane.smith@email.com to new leads campaign, remove bob.jones@company.com from q2 outreach campaign through natural language commands.
This guide will help you understand how to give your AutoGen agent real control over a Emelia account through Composio's Emelia MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Emelia with

- [OpenAI Agents SDK](https://composio.dev/toolkits/emelia/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/emelia/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/emelia/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/emelia/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/emelia/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/emelia/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/emelia/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/emelia/framework/cli)
- [Google ADK](https://composio.dev/toolkits/emelia/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/emelia/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/emelia/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/emelia/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/emelia/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/emelia/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 Emelia
- Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams
- Configure an Autogen AssistantAgent that can call Emelia tools
- Run a live chat loop where you ask the agent to perform Emelia 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 Emelia MCP server, and what's possible with it?

The Emelia MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Emelia account. It provides structured and secure access to your B2B outreach operations, so your agent can perform actions like launching campaigns, managing contacts, finding prospect emails, and tracking outreach activities on your behalf.
- Automated campaign creation and management: Instruct your agent to create new email or LinkedIn campaigns, add contacts, or remove contacts from campaigns to keep your outreach efforts streamlined and organized.
- Prospect email discovery: Have your agent find verified email addresses for specific contacts using full name and company details, accelerating your lead generation process.
- Contact blacklisting and compliance: Direct your agent to add contacts to the blacklist, ensuring that no further emails are sent and helping you stay compliant with outreach best practices.
- Real-time campaign activity tracking: Retrieve detailed campaign activities and create webhooks to monitor engagement, so you’re always up to date on your outreach performance.
- Webhook automation for event-driven workflows: Let your agent create or delete webhooks to automate follow-ups and synchronize campaign updates across your sales stack.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `EMELIA_ADD_CONTACT_TO_BLACKLIST` | Add Contact to Blacklist | Tool to add a contact to the email blacklist. Use after confirming that no further emails should be sent to a specific address. Example: 'Add blocked_user@example.com to blacklist.' |
| `EMELIA_ADD_CONTACT_TO_CAMPAIGN` | Add Contact To Campaign | Tool to add a contact to an email campaign. Use when you have collected subscriber details and want to enroll them in a campaign. |
| `EMELIA_CREATE_CAMPAIGN` | Create Campaign | Tool to create a new email campaign. Use after you have finalized the campaign name. |
| `EMELIA_CREATE_LINKEDIN_CAMPAIGN` | Create LinkedIn Campaign | Tool to create a new LinkedIn campaign. Use when you need to launch a LinkedIn outreach sequence. |
| `EMELIA_CREATE_WEBHOOK` | Create Webhook | Tool to create a new webhook for campaign events. Use when you need to subscribe to activity updates after determining the campaign ID and desired events. |
| `EMELIA_DELETE_CONTACT_FROM_CAMPAIGN` | Delete Contact From Campaign | Tool to remove a contact from an email campaign. Use when you need to revoke a contact's subscription from a specific campaign. Note: this operation is irreversible. |
| `EMELIA_DELETE_CONTACT_FROM_LINKEDIN_CAMPAIGN` | Delete Contact From LinkedIn Campaign | Tool to delete a contact from a LinkedIn campaign. Use when you need to remove a contact by campaign ID and contact URL. Call after confirming the contact exists in the campaign. |
| `EMELIA_DELETE_WEBHOOK` | Delete Webhook | Tool to delete a specific webhook. Use when you need to remove an existing webhook by URL after identifying the campaign. |
| `EMELIA_FIND_EMAIL_SINGLE_CONTACT` | Find Email of Single Contact | Tool to initiate a job to find the email address of a specific contact. Use when you have the contact's full name and company details and want to retrieve their email address. |
| `EMELIA_GET_CAMPAIGN_ACTIVITIES` | Get Campaign Activities | Tool to retrieve activities for a specific email campaign. Use after obtaining the campaign ID. |
| `EMELIA_GET_FIND_EMAIL_RESULT` | Get Find Email Result | Tool to retrieve the result of a previously initiated email find job. Use after initiating a find-email job to check its status and outcome. |
| `EMELIA_GET_FIND_PHONE_RESULT` | Get Find Phone Result | Tool to retrieve the outcome of a previously initiated phone-find job. Use after starting a job to fetch its status and details by job ID. |
| `EMELIA_GET_LINKEDIN_CAMPAIGN_ACTIVITIES` | Get Campaign Activities | Tool to retrieve activities for a campaign. Use when you need to inspect engagement events for a specific campaign. |
| `EMELIA_GET_VERIFY_EMAIL_RESULT` | Get Verify Email Result | Tool to get the result of an email verification job. Use after initiating an email verification job to check its status and outcome. |
| `EMELIA_INITIATE_EMAIL_VERIFICATION_JOB` | Initiate Email Verification Job | Tool to initiate an asynchronous email verification job." |
| `EMELIA_INITIATE_PHONE_FIND_JOB` | Initiate Phone Find Job | Tool to initiate a phone-find job for a single contact. Use when you want to retrieve a contact's phone number based on their email address. |
| `EMELIA_LIST_CAMPAIGN_CONTACTS` | List Campaign Contacts | Tool to list contacts in a specific email campaign. Use when you need to retrieve campaign subscribers with optional pagination. |
| `EMELIA_LIST_CAMPAIGNS` | List Campaigns | Tool to retrieve all email campaigns. Use when you need to fetch the list of campaigns, with optional pagination or search filters. |
| `EMELIA_LIST_EMAIL_PROVIDERS` | List Email Providers | Tool to retrieve all configured email providers. Use after setting up your email providers to view them. |
| `EMELIA_LIST_LINKEDIN_CAMPAIGNS` | List LinkedIn Campaigns | Tool to list all LinkedIn campaigns. Use when you need an overview of your LinkedIn campaigns and want to paginate results. |
| `EMELIA_LIST_WEBHOOKS` | List webhooks | Tool to retrieve all webhooks. Use when you need to fetch every configured webhook in Emelia. |
| `EMELIA_REMOVE_CONTACT_FROM_BLACKLIST` | Remove Contact from Blacklist | Tool to remove a contact or domain from the email blacklist. Use after verifying that the address or domain should no longer be blocked. |

## Supported Triggers

None listed.

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

The Emelia MCP server is an implementation of the Model Context Protocol that connects your AI agents and assistants directly to Emelia. Instead of manually wiring Emelia 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 Emelia 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 Emelia 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 Emelia 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 Emelia 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 Emelia session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["emelia"]
    )
    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 Emelia 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 Emelia assistant agent with MCP tools
    agent = AssistantAgent(
        name="emelia_assistant",
        description="An AI assistant that helps with Emelia 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 Emelia 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 Emelia 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 Emelia session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["emelia"]
    )
    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 Emelia assistant agent with MCP tools
        agent = AssistantAgent(
            name="emelia_assistant",
            description="An AI assistant that helps with Emelia 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 Emelia 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 Emelia 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 Emelia, you can reuse the same structure for other MCP-enabled apps with minimal code changes.

## How to build Emelia MCP Agent with another framework

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

## Related Toolkits

- [Aeroleads](https://composio.dev/toolkits/aeroleads) - Aeroleads is a B2B lead generation platform for finding business emails and phone numbers. Grow your sales pipeline faster with powerful prospecting tools.
- [Autobound](https://composio.dev/toolkits/autobound) - Autobound is an AI-powered sales engagement platform that crafts hyper-personalized outreach and insights. It helps sales teams boost response rates and close more deals through tailored content and recommendations.
- [Better proposals](https://composio.dev/toolkits/better_proposals) - Better Proposals is a web-based tool for crafting and sending professional proposals. It helps teams impress clients and close deals faster with slick, easy-to-use templates.
- [Bidsketch](https://composio.dev/toolkits/bidsketch) - Bidsketch is a proposal software that helps businesses create professional proposals quickly and efficiently. It streamlines the proposal process, saving time while boosting client win rates.
- [Bolna](https://composio.dev/toolkits/bolna) - Bolna is an AI platform for building conversational voice agents. It helps businesses automate support and streamline interactions through natural, voice-powered conversations.
- [Botsonic](https://composio.dev/toolkits/botsonic) - Botsonic is a no-code AI chatbot builder for easily creating and deploying chatbots to your website. It empowers businesses to offer conversational experiences without writing code.
- [Botstar](https://composio.dev/toolkits/botstar) - BotStar is a comprehensive chatbot platform for designing, developing, and training chatbots visually on Messenger and websites. It helps businesses automate conversations and customer interactions without coding.
- [Callerapi](https://composio.dev/toolkits/callerapi) - CallerAPI is a white-label caller identification platform for branded caller ID and fraud prevention. It helps businesses boost customer trust while stopping spam, fraud, and robocalls.
- [Callingly](https://composio.dev/toolkits/callingly) - Callingly is a lead response management platform that automates immediate call and text follow-ups with new leads. It helps sales teams boost response speed and close more deals by connecting seamlessly with CRMs and lead sources.
- [Callpage](https://composio.dev/toolkits/callpage) - Callpage is a lead capture platform that lets businesses instantly connect with website visitors via callback. It boosts lead generation and increases your sales conversion rates.
- [Clearout](https://composio.dev/toolkits/clearout) - Clearout is an AI-powered service for verifying, finding, and enriching email addresses. It boosts deliverability and helps you discover high-quality leads effortlessly.
- [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time.
- [Convolo ai](https://composio.dev/toolkits/convolo_ai) - Convolo ai is an AI-powered communications platform for sales teams. It accelerates lead response and improves conversion rates by automating calls and integrating workflows.
- [Delighted](https://composio.dev/toolkits/delighted) - Delighted is a customer feedback platform based on the Net Promoter System®. It helps you quickly gather, track, and act on customer sentiment.
- [Docsbot ai](https://composio.dev/toolkits/docsbot_ai) - Docsbot ai is a platform that lets you build custom AI chatbots trained on your documentation. It automates customer support and content generation, saving time and improving response quality.
- [Findymail](https://composio.dev/toolkits/findymail) - Findymail is a B2B data provider offering verified email and phone contacts for sales prospecting. Enhance outreach with automated exports, email verification, and CRM enrichment.
- [Freshdesk](https://composio.dev/toolkits/freshdesk) - Freshdesk is customer support software with ticketing and automation tools. It helps teams streamline helpdesk operations for faster, better customer support.
- [Fullenrich](https://composio.dev/toolkits/fullenrich) - FullEnrich is a B2B contact enrichment platform that aggregates emails and phone numbers from 15+ data vendors. Instantly find and verify lead contact data to boost your outreach.
- [Gatherup](https://composio.dev/toolkits/gatherup) - GatherUp is a customer feedback and online review management platform. It helps businesses boost their reputation by streamlining how they collect and manage customer feedback.
- [Getprospect](https://composio.dev/toolkits/getprospect) - Getprospect is a business email discovery tool with LinkedIn integration. Use it to quickly find and verify professional email addresses.

## Frequently Asked Questions

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

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

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

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

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