How to integrate Benchmark email MCP with Autogen

Framework Integration Gradient
Benchmark email Logo
AutoGen Logo
divider

Introduction

This guide walks you through connecting Benchmark email to AutoGen using the Composio tool router. By the end, you'll have a working Benchmark email agent that can list all confirmed sender email addresses, get my benchmark account plan details, fetch company profile and contact limits, retrieve all current account settings through natural language commands.

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

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

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 Benchmark email
  • Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams
  • Configure an Autogen AssistantAgent that can call Benchmark email tools
  • Run a live chat loop where you ask the agent to perform Benchmark email 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 Benchmark email MCP server, and what's possible with it?

The Benchmark email MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Benchmark Email account. It provides structured and secure access to your email marketing data, so your agent can retrieve account info, manage contacts, handle lists, and automate campaign administration on your behalf.

  • Automated contact and list management: Effortlessly add, update, or delete contacts and lists, keeping your subscriber base organized and up to date.
  • Campaign cleanup and maintenance: Direct your agent to delete obsolete email campaigns or remove unneeded webhooks to keep your workspace tidy.
  • Account insights and configuration retrieval: Have the agent fetch client details, plan information, and account settings—perfect for reporting or reviewing your workspace setup.
  • Confirmed email address retrieval: Quickly pull all verified sender email addresses for compliance and seamless campaign sending.
  • Agency account and webhook control: Manage linked agency accounts and webhooks by deleting or updating them when no longer needed for more secure integrations.

Supported Tools & Triggers

Tools
Delete Contact From ListTool to delete a contact from a specific list by contactid.
Delete Contact ListTool to delete a contact list.
Delete Email CampaignTool to delete an email campaign.
Delete Linked Agency AccountTool to delete a linked agency account.
Delete WebhookTool to delete a webhook from a contact list by its id.
Get All Confirmed EmailsTool to retrieve all confirmed email addresses for the client account.
Get Client Account SettingsTool to get client account settings such as company, language, timezone, and sender info.
Get client detailsTool to get client details including profile data, contact count, and plan information.
Get Client Plan InformationTool to get client's plan information including addons, email plan, and total contacts.
Get client profile detailsTool to get client's profile details like business city, country, phone, and company.
Get Contact List DetailsTool to fetch detailed information for a contact list.
Get Contact ListsTool to retrieve all contact lists.
Get Filtered Contacts in ListTool to fetch filtered and paginated contacts from a list by listid.
Get Email Report ForwardsTool to get forwards report for an email campaign.
Get Unopens ReportTool to get unopens report for an email campaign by id.
Get Linked Agency Account DetailsTool to get details of a linked agency account.
Get Linked Agency AccountsTool to get list of linked agency accounts.
Get sub-account detailsTool to get details for a specific sub-account by id.
Get Sub-Account HistoryTool to get sub-account history.
Get Sub-AccountsTool to retrieve all sub-accounts for the client.
Get Sub-Accounts Plan ListTool to retrieve available plans for a sub-account.
Change PasswordTool to change the password for the client account.
Save Security PINTool to save a new security pin for the client account.
Send Reset EmailTool to send a reset email link to change the primary email address.
Patch Update Client SettingsTool to update client account settings.
Update Contact ListTool to update an existing contact list.
Update/Edit ProfileTool to update or edit profile information such as first name, last name, and phone number.
Update WebhookTool to update a webhook for a contact list by webhook id.
Add Contact to ListTool to add a new contact to a specific list.
Change Security PINTool to change security pin for the client account.
Create Contact ListTool to create a new contact list.
Create WebhookTool to create a new webhook for a contact list.
Disable Security PINTool to disable security pin for the client account.
Save Website DomainTool to save a website domain for your benchmark email account.
Send Confirm Email VerificationTool to send confirm email verification.
Send PIN via EmailTool to send pin via email.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router 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 Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router 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

Prerequisites

You will need:

  • A Composio API key
  • An OpenAI API key (used by Autogen's OpenAIChatCompletionClient)
  • A Benchmark email account you can connect to Composio
  • Some basic familiarity with Autogen and Python async

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard 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.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

bash
pip install composio python-dotenv
pip install autogen-agentchat autogen-ext-openai autogen-ext-tools

Install Composio, Autogen extensions, and dotenv.

What's happening:

  • composio connects your agent to Benchmark email via MCP
  • autogen-agentchat provides the AssistantAgent class
  • autogen-ext-openai provides the OpenAI model client
  • autogen-ext-tools provides MCP workbench support

Set up environment variables

bash
COMPOSIO_API_KEY=your-composio-api-key
OPENAI_API_KEY=your-openai-api-key
USER_ID=your-user-identifier@example.com

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 Benchmark email connections to use

Import dependencies and create Tool Router session

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

Configure MCP parameters for Autogen

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

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

Create the model client and agent

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 Benchmark email assistant agent with MCP tools
    agent = AssistantAgent(
        name="benchmark_email_assistant",
        description="An AI assistant that helps with Benchmark email operations.",
        model_client=model_client,
        workbench=workbench,
        model_client_stream=True,
        max_tool_iterations=10
    )

What's happening:

  • OpenAIChatCompletionClient wraps the OpenAI model for Autogen
  • McpWorkbench connects the agent to the MCP tools
  • AssistantAgent is configured with the Benchmark email tools from the workbench

Run the interactive chat loop

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

Complete Code

Here's the complete code to get you started with Benchmark email and AutoGen:

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

How to build Benchmark email MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Benchmark email MCP?

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

Can I manage the permissions and scopes for Benchmark email while using Tool Router?

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

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.