# Composio MCP server

> Connect an assistant to 1,000+ apps through one endpoint, with managed sign-in and cross-app tool execution.

- Listing: https://mcp.tc/i/composio
- Connect: use the server's own URL `https://connect.composio.dev/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Automation & Integrations](https://mcp.tc/c/automation)
- Vendor: Composio
- Homepage: <https://docs.composio.dev/docs/composio-connect>
- Repository: <https://github.com/ComposioHQ/composio>

## About

Composio gives an MCP client access to more than 1,000 third-party apps through a single connection. It exposes meta-tools that find the right app and tool at runtime, ask the user to authorize the app when needed, and then run the tool. This avoids loading hundreds of tool definitions into context.

It runs as a hosted streamable HTTP endpoint at connect.composio.dev. Users sign in with OAuth, and Composio manages the authentication for each connected app. No local install is required.

## What it can do

- Discover apps and tools relevant to a task at runtime
- Authorize apps on demand with managed OAuth
- Run tools from many apps in one session
- Chain actions across several apps in a single request

## Example prompts

- "Summarize my emails from today"
- "Find a tool that can create a calendar event and schedule a meeting for Friday"
- "Connect my GitHub account and list my open pull requests"
- "Post the summary of this thread to Slack"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

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

2. Start Claude Code, type `/mcp`, pick **composio** and choose **Authenticate**. A browser window opens for the Composio sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Settings → Connectors** and click **Add custom connector**.

2. Name it **Composio** and paste this URL:

```url
https://connect.composio.dev/mcp
```

3. Click **Add**, then **Connect**, and sign in when Composio asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Composio&connectorUrl=https%3A%2F%2Fconnect.composio.dev%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://connect.composio.dev/mcp` and click **Add**.

3. Click **Connect** and sign in when Composio asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://connect.composio.dev/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Composio to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=composio&config=eyJ1cmwiOiJodHRwczovL2Nvbm5lY3QuY29tcG9zaW8uZGV2L21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "composio": {
      "url": "https://connect.composio.dev/mcp"
    }
  }
}
```

Cursor shows **Needs login** next to the server. Click it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=composio&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fconnect.composio.dev%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"composio","type":"http","url":"https://connect.composio.dev/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "composio": {
      "type": "http",
      "url": "https://connect.composio.dev/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "composio": {
      "serverUrl": "https://connect.composio.dev/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add composio --url https://connect.composio.dev/mcp
codex mcp login composio
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http composio https://connect.composio.dev/mcp
```

Then, inside Gemini CLI, run `/mcp auth composio` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "composio": {
      "type": "http",
      "url": "https://connect.composio.dev/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://connect.composio.dev/mcp`.

## Details

- Server version: 1.0.5
- Last checked: 2026-10-03 (reachable, asks for credentials)
- Listed: 2026-10-03
- Updated: 2026-10-03

---
Source: https://mcp.tc/i/composio (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report