How to integrate Radar MCP with Codex

GET STARTED FOR FREE
Radar logo
Codex logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Radar MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Also integrate Radar with

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Radar MCP in Codex

Run the setup command

Run this command in your terminal to add the Composio MCP server to Codex.

Terminal

It will initiate the authentication in a browser window, authorize Codex to access your Composio account.

Composio authentication page

(Optional) Authenticate with OAuth

To authenticate manually, run the login command to open a browser window and authorize Codex to access your Composio account.

bash
codex mcp login composio

Verify the connection

Run codex mcp list to confirm Composio appears as a registered MCP server.

bash
codex mcp list

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
  2. Fill the header and Key fields with { "x-consumer-api-key" = "ck_*******" }.
  3. The Key is the Composio API key, that you can find on connect.composio.dev
  4. Click on Authenticate and authorize Codex to your Composio account and you're all set.
Codex App MCP setup
  1. Restart and verify if it's there in .codex/config.toml
bash
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
http_headers = { "x-consumer-api-key" = "ck_*******" }

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 & Triggers

Tools
Autocomplete Address or PlaceTool to autocomplete partial addresses and place names based on relevance and proximity.
Create TripTool to create a new trip.
Delete GeofenceTool to delete a geofence by id.
Delete TripTool to delete a trip by its radar id or external id.
Forward GeocodeTool to convert an address into geographic coordinates.
Get Context for LocationTool to retrieve context for a given location.
Get GeofenceTool to retrieve a geofence by radar id or tag/externalid.
Get Places SettingsTool to retrieve current places settings for your radar project.
Get TripTool to retrieve a trip by id or externalid.
Get Users in GeofenceTool to retrieve users currently within a specific geofence.
IP GeocodeTool to geocode an ip address to city, state, and country.
List BeaconsTool to list all beacons sorted by creation date.
List EventsTool to list events.
List GeofencesTool to list all geofences sorted by updated time.
List TripsTool to list all trips, sorted by updated time.
List UsersTool to list radar users sorted by update time.
Reverse GeocodeTool to convert geographic coordinates to structured addresses.
Route DistanceTool to compute distance and travel time between origins and destinations.
Search GeofencesTool to search for geofences near a given location.
Search Places Near LocationTool to search for places near given coordinates.
Search Users Near LocationTool to search for users near a location.
Track Location UpdateTool to track a user's location update.
Update TripTool to update a trip.
Upsert GeofenceTool to create or update a geofence by tag and externalid.

Conclusion

You've successfully integrated Radar with Codex using Composio's MCP server. Now you can interact with Radar directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Radar operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Radar operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Radar MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Radar MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Radar MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Radar MCP with Claude Code

OpenClaw logo

OpenClaw

Use Radar MCP with OpenClaw

CLI logo

CLI

Use Radar MCP with CLI

Google ADK logo

Google ADK

Use Radar MCP with Google ADK

LangChain logo

LangChain

Use Radar MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Radar MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Radar MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Radar MCP with LlamaIndex

CrewAI logo

CrewAI

Use Radar MCP with CrewAI

FAQ

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 Codex?

Yes, you can. Codex 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.

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