How to integrate RedCircle API MCP with Autogen

GET STARTED FOR FREE
Framework Integration Gradient
RedCircle API Logo
AutoGen Logo
divider

Introduction

This guide walks you through connecting RedCircle API to AutoGen using the Composio tool router. By the end, you'll have a working RedCircle API agent that can search target for nintendo switch bundles, get reviews for dyson vacuums at target, list top-rated target products in electronics through natural language commands.

This guide will help you understand how to give your AutoGen agent real control over a RedCircle API account through Composio's RedCircle API 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 RedCircle API
  • Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams
  • Configure an Autogen AssistantAgent that can call RedCircle API tools
  • Run a live chat loop where you ask the agent to perform RedCircle API 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 RedCircle API MCP server, and what's possible with it?

The RedCircle API MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your RedCircle API account. It provides structured and secure access so your agent can perform RedCircle API operations on your behalf.

Supported Tools & Triggers

Tools
Add ZipcodesTool to add zipcodes to your RedCircle API account for geolocation targeting.
Clear Collection RequestsTool to remove all requests from a specified collection.
Create CollectionTool to create a new collection for running up to 15,000 requests on a schedule.
Create DestinationTool to create a new destination for uploading Collection Result Sets to cloud storage.
Create RequestsTool to add up to 1,000 requests to an existing collection.
Delete CollectionTool to remove a collection from the system by ID.
Delete DestinationTool to remove a destination from your RedCircle API account.
Delete Request from CollectionTool to remove an individual request from a collection.
Delete Requests In BulkTool to delete multiple requests from a collection in bulk.
Delete ZipcodesTool to remove zipcodes from your RedCircle API account.
Get Account InformationTool to retrieve account information, usage metrics, and platform status.
Get CollectionTool to retrieve complete information about a specific collection.
Get Requests CSV LinksTool to retrieve CSV download links for all requests in a collection.
Get Requests JSON LinksTool to retrieve download links for all requests in a collection in JSON format.
Get Result Set CSVTool to retrieve a result set in CSV format with optional field filtering.
Get Result Set JSONTool to retrieve a result set in JSON format with download links.
Get Result Set JSON LinesTool to retrieve a result set in JSON Lines format with download links.
Get Target Product DataTool to retrieve Target data in real-time including search results, product information, reviews, or category listings.
List CategoriesTool to retrieve all top-level (root) categories or filter results using optional parameters.
List CollectionsTool to retrieve all collections configured on your RedCircle API account with filtering and pagination.
List DestinationsTool to retrieve all destinations configured on your RedCircle API account with pagination and filtering.
List Error LogsTool to list all error logs on your RedCircle API account.
List Requests by PageTool to retrieve requests for a collection in paginated format.
List Result SetsTool to list all result sets for a collection.
List ZipcodesTool to retrieve all zipcodes associated with your account with optional filtering.
Resend WebhookTool to resend a previously configured webhook POST request for a result set.
Start CollectionTool to initiate execution of a RedCircle API collection.
Stop All CollectionsTool to halt all currently active collections on your account.
Stop CollectionTool to halt an active collection in queued or running state.
Update CollectionTool to update an existing collection's configuration and settings.
Update DestinationTool to modify an existing destination configuration on your RedCircle API account.
Update RequestTool to modify a request within a collection.

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 RedCircle API 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 RedCircle API 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 RedCircle API 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 RedCircle API session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["redcircle_api"]
    )
    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 RedCircle API 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 RedCircle API assistant agent with MCP tools
    agent = AssistantAgent(
        name="redcircle_api_assistant",
        description="An AI assistant that helps with RedCircle API 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 RedCircle API 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 RedCircle API 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 RedCircle API 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 RedCircle API and AutoGen:

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

How to build RedCircle API MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use RedCircle API MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use RedCircle API MCP with Claude Agent SDK

Google ADK

Google ADK

Use RedCircle API MCP with Google ADK

LangChain

LangChain

Use RedCircle API MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use RedCircle API MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use RedCircle API MCP with Mastra AI

LlamaIndex

LlamaIndex

Use RedCircle API MCP with LlamaIndex

CrewAI

CrewAI

Use RedCircle API MCP with CrewAI

Claude Code

Claude Code

Use RedCircle API MCP with Claude Code

Codex

Codex

Use RedCircle API MCP with Codex

FAQ

What are the differences in Tool Router MCP and RedCircle API MCP?

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

Can I manage the permissions and scopes for RedCircle API while using Tool Router?

Yes, absolutely. You can configure which RedCircle API 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 RedCircle API 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.

Book a call↗Get started for free