# How to integrate Radar MCP with OpenAI Agents SDK

```json
{
  "title": "How to integrate Radar MCP with OpenAI Agents SDK",
  "toolkit": "Radar",
  "toolkit_slug": "radar",
  "framework": "OpenAI Agents SDK",
  "framework_slug": "open-ai-agents-sdk",
  "url": "https://composio.dev/toolkits/radar/framework/open-ai-agents-sdk",
  "markdown_url": "https://composio.dev/toolkits/radar/framework/open-ai-agents-sdk.md",
  "updated_at": "2026-05-12T10:23:13.738Z"
}
```

## Introduction

This guide walks you through connecting Radar to the OpenAI Agents SDK 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 OpenAI Agents SDK 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

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

## TL;DR

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Install the necessary dependencies
- Initialize Composio and create a Tool Router session for Radar
- Configure an AI agent that can use Radar as a tool
- Run a live chat session where you can ask the agent to perform Radar operations

## What is OpenAI Agents SDK?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.
Key features include:
- Hosted MCP Tools: Connect to external services through hosted MCP endpoints
- SQLite Sessions: Persist conversation history across interactions
- Simple API: Clean interface with Agent, Runner, and tool configuration
- Streaming Support: Real-time response streaming for interactive applications

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

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `RADAR_AUTOCOMPLETE_ADDRESS_OR_PLACE` | Autocomplete Address or Place | Tool to autocomplete partial addresses and place names based on relevance and proximity. Use after a user inputs a partial address/place to get suggestions, optionally biased by location. |
| `RADAR_CREATE_BEACON` | Create Beacon | Tool to create a new beacon in Radar. Use when you need to register a physical beacon device (iBeacon or Eddystone) for location tracking. |
| `RADAR_CREATE_TRIP` | Create Trip | Tool to create a new trip. Use after gathering origin and destination details to start tracking a trip. |
| `RADAR_DELETE_BEACON` | Delete Beacon | Tool to delete a beacon by its Radar ID. Use when supplying a beacon's unique identifier to remove it. |
| `RADAR_DELETE_GEOFENCE` | Delete Geofence | Tool to delete a geofence by ID. Use when supplying a geofence’s unique identifier to remove it. |
| `RADAR_DELETE_GEOFENCE_BY_TAG` | Delete Geofence By Tag | Tool to delete a geofence by tag and external ID. Use when you have both the tag and external identifier to remove a specific geofence. |
| `RADAR_DELETE_TRIP` | Delete Trip | Tool to delete a trip by its Radar ID or external ID. Use after confirming the trip exists. |
| `RADAR_DELETE_USER` | Delete User | Tool to delete a user by Radar _id, userId, or deviceId. Use after confirming the user identifier exists. |
| `RADAR_FORWARD_GEOCODE` | Forward Geocode | Tool to convert an address into geographic coordinates. Use when you have a full address string and need precise latitude/longitude before further location analysis. |
| `RADAR_GET_BEACON` | Get Beacon | Tool to retrieve a beacon by Radar _id. Use when you need to fetch full details of an existing beacon. |
| `RADAR_GET_BEACON_BY_TAG` | Get Beacon By Tag | Tool to get a specific beacon by tag and external ID. Use when you need to retrieve details of a beacon identified by its tag group and external ID. |
| `RADAR_GET_CONTEXT_FOR_LOCATION` | Get Context for Location | Tool to retrieve context for a given location. Use when you need geofences, place, and region information based on coordinates. Use after obtaining valid latitude and longitude. |
| `RADAR_GET_GEOFENCE` | Get Geofence | Tool to retrieve a geofence by Radar _id or tag/externalId. Use when you need to fetch full details of an existing geofence. |
| `RADAR_GET_PLACES_SETTINGS` | Get Places Settings | Tool to retrieve current Places settings for your Radar project. Use when you need to inspect chain detection, supported countries, external ID requirements, and other Places metadata. |
| `RADAR_GET_ROUTE_DIRECTIONS` | Get Route Directions | Tool to get turn-by-turn directions between multiple locations. Use when you need detailed navigation instructions with steps, distances, and durations for routing. |
| `RADAR_GET_ROUTE_MATRIX` | Get Route Matrix | Tool to calculate travel distance and duration between multiple origins and destinations for up to 625 routes. Use when you need to compute route metrics for multiple origin-destination pairs efficiently. |
| `RADAR_GET_TRIP` | Get Trip | Tool to retrieve a trip by ID or externalId. Use when you have a trip ID or externalId to fetch its details. |
| `RADAR_GET_USER` | Get User | Tool to get a user by Radar _id, userId, or deviceId. Returns the user with all location and context data including geofences, places, beacons, and trip information. |
| `RADAR_GET_USERS_IN_GEOFENCE` | Get Users in Geofence | Tool to retrieve users currently within a specific geofence. Use when you need to list all users inside a geofence by its tag and external ID. |
| `RADAR_IP_GEOCODE` | IP Geocode | Tool to geocode an IP address to city, state, and country. Use when you need location details based on an IP address. |
| `RADAR_LIST_EVENTS` | List Events | Tool to list events. Use when you need to retrieve a paginated list of events with optional filtering. |
| `RADAR_LIST_GEOFENCES` | List Geofences | Tool to list all geofences sorted by updated time. Use when you need an overview of all configured geofences. |
| `RADAR_LIST_TRIPS` | List Trips | Tool to list all trips, sorted by updated time. Use when you need to page through the latest trips. |
| `RADAR_LIST_USERS` | List Users | Tool to list Radar users sorted by update time. Use when you need to page through users in your project. |
| `RADAR_REVERSE_GEOCODE` | Reverse Geocode | Tool to convert geographic coordinates to structured addresses. Use when you have latitude/longitude and need a human-readable address. |
| `RADAR_ROUTE_DISTANCE` | Route Distance | Tool to compute distance and travel time between origins and destinations. Use when you need route metrics before optimizing or timing routes. |
| `RADAR_SEARCH_GEOFENCES_NEAR_LOCATION` | Search Geofences | Tool to search for geofences near a given location. Use when you need to find geofences within a radius of specified coordinates. |
| `RADAR_SEARCH_PLACES_NEAR_LOCATION` | Search Places Near Location | Tool to search for places near given coordinates. Use when you need to find points of interest around a location. |
| `RADAR_SEARCH_USERS_NEAR_LOCATION` | Search Users Near Location | Tool to search for users near a location. Use after obtaining coordinates when you need to retrieve users within a given radius. |
| `RADAR_TRACK_LOCATION_UPDATE` | Track Location Update | Tool to track a user's location update. Use when sending a location update for a user, creating or updating user and event data. |
| `RADAR_UPDATE_PLACES_SETTINGS` | Update Places Settings | Tool to update Places settings for your Radar project including chain metadata preferences. Use when you need to configure chain detection or other Places settings. |
| `RADAR_UPDATE_TRIP` | Update Trip | Tool to update a trip. Use when you need to modify mode, destination, schedule, or active status. |
| `RADAR_UPDATE_TRIP_BY_ID` | Update Trip By ID | Tool to update a trip status by Radar _id or external ID. Use when you need to change trip status to started, approaching, arrived, completed, or canceled. |
| `RADAR_UPSERT_BEACON_BY_ID` | Upsert Beacon by ID | Tool to create or update a beacon by Radar _id. Use when you need to ensure a beacon with a specific ID exists with updated properties. |
| `RADAR_UPSERT_BEACON_BY_TAG` | Upsert Beacon by Tag | Tool to create or update a beacon by tag and externalId. Use when you need to ensure a beacon exists or is updated with specific identifiers. |
| `RADAR_UPSERT_GEOFENCE` | Upsert Geofence | Tool to create or update a geofence by tag and externalId. Use when ensuring a geofence exists or is updated based on identifiers. |
| `RADAR_UPSERT_GEOFENCE_BY_ID` | Upsert Geofence By ID | Tool to create or update a geofence by Radar _id. Use when you need to upsert a geofence using its internal Radar identifier. |

## Supported Triggers

None listed.

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

The Radar MCP server is an implementation of the Model Context Protocol that connects your AI agent to Radar. It provides structured and secure access so your agent can perform Radar operations on your behalf through a secure, permission-based interface.
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

Before starting, make sure you have:
- Composio API Key and OpenAI API Key
- Primary know-how of OpenAI Agents SDK
- A live Radar project
- Some knowledge of Python or Typescript

### 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).
- Go to Settings and copy your API key.

### 2. Install dependencies

Install the Composio SDK and the OpenAI Agents SDK.
```python
pip install composio_openai_agents openai-agents python-dotenv
```

```typescript
npm install @composio/openai-agents @openai/agents dotenv
```

### 3. Set up environment variables

Create a .env file and add your OpenAI and Composio API keys.
```bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com
```

### 4. Import dependencies

What's happening:
- You're importing all necessary libraries.
- The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Radar.
```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';
```

### 5. Set up the Composio instance

No description provided.
```python
load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
```

```typescript
dotenv.config();

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});
```

### 6. Create a Tool Router session

What is happening:
- You give the Tool Router the user id and the toolkits you want available. Here, it is only radar.
- The router checks the user's Radar connection and prepares the MCP endpoint.
- The returned session.mcp.url is the MCP URL that your agent will use to access Radar.
- This approach keeps things lightweight and lets the agent request Radar tools only when needed during the conversation.
```python
# Create a Radar Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["radar"]
)

mcp_url = session.mcp.url
```

```typescript
// Create Tool Router session for Radar
const session = await composio.create(userId as string, {
  toolkits: ['radar'],
});
const mcpUrl = session.mcp.url;
```

### 7. Configure the agent

No description provided.
```python
# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Radar. "
        "Help users perform Radar operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)
```

```typescript
// Configure agent with MCP tool
const agent = new Agent({
  name: 'Assistant',
  model: 'gpt-5',
  instructions:
    'You are a helpful assistant that can access Radar. Help users perform Radar operations through natural language.',
  tools: [
    hostedMcpTool({
      serverLabel: 'tool_router',
      serverUrl: mcpUrl,
      headers: { 'x-api-key': composioApiKey },
      requireApproval: 'never',
    }),
  ],
});
```

### 8. Start chat loop and handle conversation

No description provided.
```python
print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
// Keep conversation state across turns
const conversationSession = new OpenAIConversationsSession();

// Simple CLI
const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: 'You: ',
});

console.log('\nComposio Tool Router session created.');
console.log('\nChat started. Type your requests below.');
console.log("Commands: 'exit', 'quit', or 'q' to end\n");

try {
  const first = await run(agent, 'What can you help me with?', { session: conversationSession });
  console.log(`Assistant: ${first.finalOutput}\n`);
} catch (e) {
  console.error('Error:', e instanceof Error ? e.message : e, '\n');
}

rl.prompt();

rl.on('line', async (userInput) => {
  const text = userInput.trim();

  if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
    console.log('Goodbye!');
    rl.close();
    process.exit(0);
  }

  if (!text) {
    rl.prompt();
    return;
  }

  try {
    const result = await run(agent, text, { session: conversationSession });
    console.log(`\nAssistant: ${result.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();
});

rl.on('close', () => {
  console.log('\n👋 Session ended.');
  process.exit(0);
});
```

## Complete Code

```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["radar"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Radar. "
        "Help users perform Radar operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});

async function main() {
  // Create Tool Router session
  const session = await composio.create(userId as string, {
    toolkits: ['radar'],
  });
  const mcpUrl = session.mcp.url;

  // Configure agent with MCP tool
  const agent = new Agent({
    name: 'Assistant',
    model: 'gpt-5',
    instructions:
      'You are a helpful assistant that can access Radar. Help users perform Radar operations through natural language.',
    tools: [
      hostedMcpTool({
        serverLabel: 'tool_router',
        serverUrl: mcpUrl,
        headers: { 'x-api-key': composioApiKey },
        requireApproval: 'never',
      }),
    ],
  });

  // Keep conversation state across turns
  const conversationSession = new OpenAIConversationsSession();

  // Simple CLI
  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: ',
  });

  console.log('\nComposio Tool Router session created.');
  console.log('\nChat started. Type your requests below.');
  console.log("Commands: 'exit', 'quit', or 'q' to end\n");

  try {
    const first = await run(agent, 'What can you help me with?', { session: conversationSession });
    console.log(`Assistant: ${first.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();

  rl.on('line', async (userInput) => {
    const text = userInput.trim();

    if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
      console.log('Goodbye!');
      rl.close();
      process.exit(0);
    }

    if (!text) {
      rl.prompt();
      return;
    }

    try {
      const result = await run(agent, text, { session: conversationSession });
      console.log(`\nAssistant: ${result.finalOutput}\n`);
    } catch (e) {
      console.error('Error:', e instanceof Error ? e.message : e, '\n');
    }

    rl.prompt();
  });

  rl.on('close', () => {
    console.log('\nSession ended.');
    process.exit(0);
  });
}

main().catch((err) => {
  console.error('Fatal error:', err);
  process.exit(1);
});
```

## Conclusion

This was a starter code for integrating Radar MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Radar.
Key features:
- Hosted MCP tool integration through Composio's Tool Router
- SQLite session persistence for conversation history
- Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

## How to build Radar MCP Agent with another framework

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

## Related Toolkits

- [Excel](https://composio.dev/toolkits/excel) - Microsoft Excel is a robust spreadsheet application for organizing, analyzing, and visualizing data. It's the go-to tool for calculations, reporting, and flexible data management.
- [21risk](https://composio.dev/toolkits/_21risk) - 21RISK is a web app built for easy checklist, audit, and compliance management. It streamlines risk processes so teams can focus on what matters.
- [Abstract](https://composio.dev/toolkits/abstract) - Abstract provides a suite of APIs for automating data validation and enrichment tasks. It helps developers streamline workflows and ensure data quality with minimal effort.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agenty](https://composio.dev/toolkits/agenty) - Agenty is a web scraping and automation platform for extracting data and automating browser tasks—no coding needed. It streamlines data collection, monitoring, and repetitive online actions.
- [Ambee](https://composio.dev/toolkits/ambee) - Ambee is an environmental data platform providing real-time, hyperlocal APIs for air quality, weather, and pollen. Get precise environmental insights to power smarter decisions in your apps and workflows.
- [Ambient weather](https://composio.dev/toolkits/ambient_weather) - Ambient Weather is a platform for personal weather stations with a robust API for accessing local, real-time, and historical weather data. Get detailed environmental insights directly from your own sensors for smarter apps and automations.
- [Anonyflow](https://composio.dev/toolkits/anonyflow) - Anonyflow is a service for encryption-based data anonymization and secure data sharing. It helps organizations meet GDPR, CCPA, and HIPAA data privacy compliance requirements.
- [Api ninjas](https://composio.dev/toolkits/api_ninjas) - Api ninjas offers 120+ public APIs spanning categories like weather, finance, sports, and more. Developers use it to supercharge apps with real-time data and actionable endpoints.
- [Api sports](https://composio.dev/toolkits/api_sports) - Api sports is a comprehensive sports data platform covering 2,000+ competitions with live scores and 15+ years of stats. Instantly access up-to-date sports information for analysis, apps, or chatbots.
- [Apify](https://composio.dev/toolkits/apify) - Apify is a cloud platform for building, deploying, and managing web scraping and automation tools called Actors. It lets you automate data extraction and workflow tasks at scale—no infrastructure headaches.
- [Autom](https://composio.dev/toolkits/autom) - Autom is a lightning-fast search engine results data platform for Google, Bing, and Brave. Developers use it to access fresh, low-latency SERP data on demand.
- [Beaconchain](https://composio.dev/toolkits/beaconchain) - Beaconchain is a real-time analytics platform for Ethereum 2.0's Beacon Chain. It provides detailed insights into validators, blocks, and overall network performance.
- [Big data cloud](https://composio.dev/toolkits/big_data_cloud) - BigDataCloud provides APIs for geolocation, reverse geocoding, and address validation. Instantly access reliable location intelligence to enhance your applications and workflows.
- [Bigpicture io](https://composio.dev/toolkits/bigpicture_io) - BigPicture.io offers APIs for accessing detailed company and profile data. Instantly enrich your applications with up-to-date insights on 20M+ businesses.
- [Bitquery](https://composio.dev/toolkits/bitquery) - Bitquery is a blockchain data platform offering indexed, real-time, and historical data from 40+ blockchains via GraphQL APIs. Get unified, reliable access to complex on-chain data for analytics, trading, and research.
- [Brightdata](https://composio.dev/toolkits/brightdata) - Brightdata is a leading web data platform offering advanced scraping, SERP APIs, and anti-bot tools. It lets you collect public web data at scale, bypassing blocks and friction.
- [Builtwith](https://composio.dev/toolkits/builtwith) - BuiltWith is a web technology profiler that uncovers the technologies powering any website. Gain actionable insights into analytics, hosting, and content management stacks for smarter research and lead generation.
- [Byteforms](https://composio.dev/toolkits/byteforms) - Byteforms is an all-in-one platform for creating forms, managing submissions, and integrating data. It streamlines workflows by centralizing form data collection and automation.
- [Cabinpanda](https://composio.dev/toolkits/cabinpanda) - Cabinpanda is a data collection platform for building and managing online forms. It helps streamline how you gather, organize, and analyze responses.

## Frequently Asked Questions

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

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.

### Can I use Tool Router MCP with OpenAI Agents SDK?

Yes, you can. OpenAI Agents SDK 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.

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

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.

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

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