Composio Remote MCP Gateway

🔌 Gateway✓ VerifiedStreamable HTTPOAuth 2.13 tools·Degraded103ms·30d uptime: 100%·Last checked 18m ago

Composio's MCP gateway multiplexes hundreds of SaaS integrations into one endpoint with managed authentication — connect once, get many apps' tools.

https://mcp.composio.dev/mcp

Provider: Composio ↗
Source: https://github.com/composiohq/composio ↗
Categories: 🔌 Multi-App Gateways & Automation

中文简介

Composio 远程 MCP 网关，通过托管 OAuth 暴露 250+ SaaS 工具集（GitHub、Slack、Notion 等），一个端点支撑多应用工作流。

Streamable HTTPhttps://mcp.composio.dev/mcp

Install in Cursor →

Or add to ~/.cursor/mcp.json:

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

🔬 Test Live in Online Inspector 🔐 Audit OAuth 2.1 Config

🧰 Tools exposed by Composio MCP (3)

Tool	Safety	Description	Parameters
list_active_integrations	🟢 Read	List app integrations currently connected and active.	—
execute_composio_tool	🟠 Write	Execute a tool from a connected Composio toolkit.	toolName*: stringparams: object
initiate_oauth_connection	🟠 Write	Start an OAuth connection flow for a third-party app.	appName*: string

🔐 OAuth 2.1 & Security

Auth type: OAuth 2.1
Dynamic Client Registration: ✅ Supported
PKCE S256: ✅ Supported
Protected resource metadata: https://mcp.composio.dev/.well-known/oauth-protected-resource (expected location)

🔐 Audit OAuth 2.1 Config →

🧩 Recommended Agent Skills

Automation skills ↗

📖 Guide

Composio MCP — Remote MCP Server

Composio is an integration layer for agents: instead of wiring each SaaS app's MCP or API yourself, you connect through Composio's gateway and get curated toolkits for GitHub, Slack, Notion and 250+ more apps, with OAuth managed on your behalf. Your exact endpoint URL embeds your Composio project — the value in this directory is the documented entry point.

Endpoint & Transport

Endpoint URL: https://mcp.composio.dev/mcp
Transport: Streamable HTTP

Authentication

Composio MCP uses OAuth 2.1 — the first request returns a 401 Unauthorized challenge with a WWW-Authenticate header pointing at the authorization metadata. Compliant clients (Cursor, Claude, VS Code, ChatGPT) handle the whole flow — PKCE and Dynamic Client Registration, so no manual client setup is needed — and simply open a browser consent screen.

Available Tools (3)

Tool	Safety	Description
`list_active_integrations`	read	List app integrations currently connected and active.
`execute_composio_tool`	write	Execute a tool from a connected Composio toolkit.
`initiate_oauth_connection`	write	Start an OAuth connection flow for a third-party app.

Connect in 30 Seconds

Claude Code — one command:

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

Cursor — add to ~/.cursor/mcp.json:

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

VS Code — add to .vscode/mcp.json:

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

Claude Desktop & stdio clients — bridge with mcp-remote:

{ "mcpServers": { "composio": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.composio.dev/mcp"] } } }

On first connect your client opens a browser OAuth consent screen — approve it and tools become available immediately.

Troubleshooting

401 Unauthorized on connect — that's expected; the server is OAuth-protected. Let your client complete the browser consent flow, or inspect the endpoint in our OAuth debugger to see the exact WWW-Authenticate challenge.
"Session expired" / stale Mcp-Session-Id — just re-send initialize; stateless clients can ignore session headers entirely.
Your usable endpoint includes a project/user segment generated in the Composio dashboard.
Toolkits must be enabled and connected per app before their tools appear.

🚀 How to Connect

Copy the Composio MCP endpoint URL
The remote endpoint is https://mcp.composio.dev/mcp.
Add it to your MCP client
Claude Code: claude mcp add --transport http composio https://mcp.composio.dev/mcp. Cursor: add "composio": { "url": "https://mcp.composio.dev/mcp" } under mcpServers in ~/.cursor/mcp.json. Other clients work similarly.
Complete the OAuth consent
On first connection your client opens a Composio consent screen in the browser. Approve it to grant access; the token is stored by the client and refreshed automatically.
Verify with the online inspector
Paste https://mcp.composio.dev/mcp into remotemcp.net/inspector, run initialize and tools/list, and confirm Composio MCP's 3 tools respond.

❓ FAQ

What is the Composio MCP remote MCP endpoint?

The primary endpoint is https://mcp.composio.dev/mcp. It is a hosted gateway server operated by Composio, speaking the Streamable HTTP transport.

How do I authenticate with Composio MCP?

Composio MCP uses OAuth 2.1. When your client first connects it receives a 401 challenge, discovers the authorization server via RFC 9728 metadata, and opens a browser consent screen. Dynamic Client Registration is supported, so compliant clients register themselves automatically.

I'm getting a 401 Unauthorized from Composio MCP — what's wrong?

A 401 means your client hasn't completed (or has lost) the OAuth authorization. Remove and re-add the server in your client to restart the consent flow, and check that your browser session can reach the provider's login page. If the 401 arrives without a WWW-Authenticate header, run it through our OAuth debugger to see what's missing.

Which MCP clients work with Composio MCP?

Any client that supports remote MCP servers: Cursor, Claude Code (`claude mcp add --transport http composio https://mcp.composio.dev/mcp`), VS Code Copilot, ChatGPT connectors, Windsurf, and Claude Desktop via the `mcp-remote` bridge.

What tools does Composio MCP expose?

3 tools are cataloged in this directory — including `list_active_integrations`, `execute_composio_tool`, `initiate_oauth_connection`. Use our online inspector to fetch the live tool list straight from the endpoint.

🔗 Connect Guides

Cursor

Connect Composio MCP →

Claude

Connect Composio MCP →

Claude Code

Connect Composio MCP →

VS Code

Connect Composio MCP →

ChatGPT

Connect Composio MCP →

Windsurf

Connect Composio MCP →

📛 Embed Status Badge in README

[![Remote MCP Status](https://remotemcp.net/api/badge/status/composio.svg)](https://remotemcp.net/servers/composio)

[![Test in Inspector](https://remotemcp.net/api/badge/inspect/composio.svg)](https://remotemcp.net/inspector?url=https%3A%2F%2Fmcp.composio.dev%2Fmcp)

Related Servers

Zapier MCPZapier

Zapier's MCP gateway — one endpoint that proxies thousands of app actions (Gmail, Slack, Sheets...) as MCP tools with your Zapier-connected accounts.

https://mcp.zapier.com/api/mcp/mcp

🔌 Gateway✓ VerifiedStreamable HTTPOAuth 2.13 toolsOnline302ms

Pipedream MCPPipedream

Pipedream's remote MCP gateway. Run 2,700+ app actions and managed triggers against connected accounts through a single OAuth-protected endpoint.

https://remote.mcp.pipedream.net

🔌 Gateway✓ VerifiedStreamable HTTPOAuth 2.13 toolsOnline511ms