# How to integrate Radar MCP with Claude Code

```json
{
  "title": "How to integrate Radar MCP with Claude Code",
  "toolkit": "Radar",
  "toolkit_slug": "radar",
  "framework": "Claude Code",
  "framework_slug": "claude-code",
  "url": "https://composio.dev/toolkits/radar/framework/claude-code",
  "markdown_url": "https://composio.dev/toolkits/radar/framework/claude-code.md",
  "updated_at": "2026-05-12T10:23:13.738Z"
}
```

## Introduction

Manage your Radar directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.
You can do this in two different ways:
- Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach
- Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control

## Also integrate Radar with

- [OpenAI Agents SDK](https://composio.dev/toolkits/radar/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/radar/framework/claude-agents-sdk)
- [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

- Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
- Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
- Handling Large tool responses out of LLM context to minimize context rot.
- Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

## Connect Radar to Claude Code

### Connecting Radar to Claude Code using Composio
1. Add the Composio MCP to Claude

```bash
claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp
```

## What is Claude Code?

Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working.
Key features include:
- Terminal-Native Experience: Work with Claude directly in your command line without switching contexts
- MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities
- Project Context: Claude understands your project structure and can read, write, and modify files
- Interactive Development: Ask questions, debug code, and get help in real-time while coding
- Multi-Platform: Works on macOS, Linux, WSL, and Windows

## 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 Claude Code (and other AI assistants like Claude and Cursor) directly to your Radar account. It provides structured and secure access so Claude can perform Radar operations on your behalf.
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:
- Claude Pro, Max, or API billing enabled Anthropic account
- Composio API Key
- A Radar account
- Basic knowledge of Python or TypeScript

### 1. Install Claude Code

To install Claude Code, use one of the following methods based on your operating system:
```bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd
```

### 2. Set up Claude Code

Open a terminal, go to your project folder, and start Claude Code:
- Claude Code will open in your terminal
- Follow the prompts to sign in with your Anthropic account
- Complete the authentication flow
- Once authenticated, you can start using Claude Code
```bash
cd your-project-folder
claude
```

### 3. Set up environment variables

Create a .env file in your project root with the following variables:
- COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code))
- USER_ID identifies the user for session management (use any unique identifier)
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
```

### 4. Install Composio library

No description provided.
```python
pip install composio-core python-dotenv
```

```typescript
npm install @composio/core dotenv
```

### 5. Generate Composio MCP URL

No description provided.
```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

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

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["radar"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http radar-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['radar'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http radar-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

### 6. Run the script and copy the MCP URL

No description provided.
```python
python generate_mcp_url.py
```

```typescript
node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts
```

### 7. Add Radar MCP to Claude Code

In your terminal, add the MCP server using the command from the previous step. The command format is:
- claude mcp add registers a new MCP server with Claude Code
- --transport http specifies that this is an HTTP-based MCP server
- The server name (radar-composio) is how you'll reference it
- The URL points to your Composio Tool Router session
- --headers includes your Composio API key for authentication
After running the command, close the current Claude Code session and start a new one for the changes to take effect.
```bash
claude mcp add --transport http radar-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude
```

### 8. Verify the installation

Check that your Radar MCP server is properly configured.
- This command lists all MCP servers registered with Claude Code
- You should see your radar-composio entry in the list
- This confirms that Claude Code can now access Radar tools
If everything is wired up, you should see your radar-composio entry listed:
```bash
claude mcp list
```

### 9. Authenticate Radar

The first time you try to use Radar tools, you'll be prompted to authenticate.
- Claude Code will detect that you need to authenticate with Radar
- It will show you an authentication link
- Open the link in your browser (or copy/paste it)
- Complete the Radar authorization flow
- Return to the terminal and start using Radar through Claude Code
Once authenticated, you can ask Claude Code to perform Radar operations in natural language. For example:
- "Autocomplete address based on partial input"
- "Get users currently inside geofence"
- "Convert address to latitude and longitude"

## Complete Code

```python
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

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

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["radar"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http radar-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['radar'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http radar-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);
```

## Conclusion

You've successfully integrated Radar with Claude Code using Composio's MCP server. Now you can interact with Radar directly from your terminal using natural language commands.
Key features of this setup:
- Terminal-native experience without switching contexts
- Natural language commands for Radar operations
- Secure authentication through Composio's managed MCP
- Tool Router for dynamic tool discovery and execution
Next steps:
- Try asking Claude Code to perform various Radar operations
- Add more toolkits to your Tool Router session for multi-app workflows
- Integrate this setup into your development workflow for increased productivity
You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

## How to build Radar MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/radar/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/radar/framework/claude-agents-sdk)
- [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 Claude Code?

Yes, you can. Claude Code 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)