How to integrate Radar MCP with Autogen

This guide walks you through connecting Radar to AutoGen using the Composio tool router. By the end, you'll have a working Radar agent that can autocomplete address based on partial input, get users currently inside geofence, convert address to latitude and longitude through natural language commands. This guide will help you understand how to give your AutoGen agent real control over a Radar account through Composio's Radar MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Radar logoRadar
Api Key

Radar is a location infrastructure platform providing APIs and SDKs for geofencing, geocoding, and location tracking. It helps developers add precise, scalable location features to any app with minimal effort.

37 Tools

Introduction

This guide walks you through connecting Radar to AutoGen using the Composio tool router. By the end, you'll have a working Radar agent that can autocomplete address based on partial input, get users currently inside geofence, convert address to latitude and longitude through natural language commands.

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

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

Also integrate Radar with

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

The Radar MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Radar account. It provides structured and secure access to advanced location services, so your agent can perform actions like geocoding addresses, managing geofences, tracking trips, searching places, and retrieving location context on your behalf.

  • Address and place autocomplete: Instantly get relevant address or place suggestions based on partial user input, improving data quality and user experience.
  • Precise geocoding and location context: Convert full addresses to latitude/longitude and fetch rich context—including region, geofence, and place details—for any set of coordinates.
  • Geofence management: Retrieve, create, or delete geofences to define dynamic boundaries and monitor activity within specific areas automatically.
  • Trip creation and tracking: Start, fetch, or delete trips to enable real-time location tracking and trip management for devices or users.
  • Live user monitoring in geofences: Effortlessly list all users currently inside a defined geofence, supporting presence-based automation and analytics.

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

What is Composio SDK?

Composio's Composio SDK 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 Composio SDK

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

How the Composio SDK works

The Composio SDK 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

Step by step08 STEPS
1

Prerequisites

You will need:

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

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.
3

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 Radar via MCP
  • autogen-agentchat provides the AssistantAgent class
  • autogen-ext-openai provides the OpenAI model client
  • autogen-ext-tools provides MCP workbench support

4

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 Radar connections to use
5

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 Radar session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["radar"]
    )
    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 Radar tools
  • session.mcp.url is the MCP endpoint that Autogen will connect to
6

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
7

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 Radar assistant agent with MCP tools
    agent = AssistantAgent(
        name="radar_assistant",
        description="An AI assistant that helps with Radar 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 Radar tools from the workbench
8

Run the interactive chat loop

python
print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Radar 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 Radar 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 Radar 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 Radar session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["radar"]
    )
    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 Radar assistant agent with MCP tools
        agent = AssistantAgent(
            name="radar_assistant",
            description="An AI assistant that helps with Radar 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 Radar 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 Radar 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 Radar, you can reuse the same structure for other MCP-enabled apps with minimal code changes.
TOOLS

Supported Tools

Every Radar action and event your agent gets out of the box.

Autocomplete Address or Place

Tool to autocomplete partial addresses and place names based on relevance and proximity.

Create Beacon

Tool to create a new beacon in Radar.

Create Trip

Tool to create a new trip.

Delete Beacon

Tool to delete a beacon by its Radar ID.

Delete Geofence

Tool to delete a geofence by ID.

Delete Geofence By Tag

Tool to delete a geofence by tag and external ID.

Delete Trip

Tool to delete a trip by its Radar ID or external ID.

Delete User

Tool to delete a user by Radar _id, userId, or deviceId.

Forward Geocode

Tool to convert an address into geographic coordinates.

Get Beacon

Tool to retrieve a beacon by Radar _id.

Get Beacon By Tag

Tool to get a specific beacon by tag and external ID.

Get Context for Location

Tool to retrieve context for a given location.

Get Geofence

Tool to retrieve a geofence by Radar _id or tag/externalId.

Get Places Settings

Tool to retrieve current Places settings for your Radar project.

Get Route Directions

Tool to get turn-by-turn directions between multiple locations.

Get Route Matrix

Tool to calculate travel distance and duration between multiple origins and destinations for up to 625 routes.

Get Trip

Tool to retrieve a trip by ID or externalId.

Get User

Tool to get a user by Radar _id, userId, or deviceId.

Get Users in Geofence

Tool to retrieve users currently within a specific geofence.

IP Geocode

Tool to geocode an IP address to city, state, and country.

List Events

Tool to list events.

List Geofences

Tool to list all geofences sorted by updated time.

List Trips

Tool to list all trips, sorted by updated time.

List Users

Tool to list Radar users sorted by update time.

Reverse Geocode

Tool to convert geographic coordinates to structured addresses.

Route Distance

Tool to compute distance and travel time between origins and destinations.

Search Geofences

Tool to search for geofences near a given location.

Search Places Near Location

Tool to search for places near given coordinates.

Search Users Near Location

Tool to search for users near a location.

Track Location Update

Tool to track a user's location update.

Update Places Settings

Tool to update Places settings for your Radar project including chain metadata preferences.

Update Trip

Tool to update a trip.

Update Trip By ID

Tool to update a trip status by Radar _id or external ID.

Upsert Beacon by ID

Tool to create or update a beacon by Radar _id.

Upsert Beacon by Tag

Tool to create or update a beacon by tag and externalId.

Upsert Geofence

Tool to create or update a geofence by tag and externalId.

Upsert Geofence By ID

Tool to create or update a geofence by Radar _id.

FAQ

Frequently asked questions

With a standalone Radar MCP server, the agents and LLMs can only access a fixed set of Radar tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Radar and many other apps based on the task at hand, all through a single MCP endpoint.

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 Radar tools.

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

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

Start with Radar.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Radar tool your agent needs.Free to start.

Start building