Composio MCP server
Composio's universal MCP server: connect an agent to 500+ apps like Gmail, Slack, GitHub, and Notion through one OAuth-authenticated endpoint.
Rube is Composio's official universal MCP server. Instead of wiring up a separate MCP server for every SaaS app, you point your agent at a single hosted endpoint and get tool access to 500+ applications — Gmail, Slack, GitHub, Notion, Linear, Google Sheets, Stripe, Supabase, and many more. Rube solves context overload with a meta-tool architecture: rather than dumping thousands of tool definitions into the model's context, the agent first searches for the right tools for a task, fetches their schemas on demand, and then executes them. This keeps the prompt small while still reaching a huge surface of real actions.
The canonical deployment is the hosted remote endpoint at https://rube.app/mcp, which uses OAuth so there are no long-lived API tokens sitting on disk. The first time an agent touches an app, Rube returns a branded authentication link and runs the per-app OAuth (or API-key) flow; Composio stores and encrypts the resulting tokens and lets you revoke them from a dashboard. Clients that support streamable HTTP connect directly to the URL; others can bridge through the npx @composio/mcp setup helper or mcp-remote. The tool surface is intentionally small and composable — search, schema lookup, connection management, recipes (reusable saved workflows), parallel multi-execution, and a remote Python/bash sandbox for post-processing — so a single server can orchestrate complex cross-app automations.
Quick install
Copy-paste configs are provided for all 8 supported clients. Pick your client below.
Add to ~/.claude.json
{
"mcpServers": {
"composio": {
"type": "http",
"url": "https://rube.app/mcp"
}
}
}claude mcp add --transport http composio https://rube.app/mcpHeads up
- First tool call opens a browser to authorize.
Available tools
| Tool | Description |
|---|---|
| RUBE_SEARCH_TOOLS | Searches across the 500+ connected toolkits and returns the best tools for a task, with their slugs, descriptions, input schemas, connection status, and related prerequisite/fallback tools. |
| RUBE_GET_TOOL_SCHEMAS | Retrieves the full input schemas for one or more tools by slug, so the agent can construct schema-compliant arguments before executing. |
| RUBE_MANAGE_CONNECTIONS | Creates or manages connections to the user's apps. Returns a branded authentication link that works for OAuth, API keys, and all other auth types. |
| RUBE_MULTI_EXECUTE_TOOL | Executes multiple tools in parallel across apps in a single call and returns structured outputs ready for analysis. |
| RUBE_REMOTE_WORKBENCH | Processes remote files or scripts bulk tool executions using Python in a remote cloud sandbox, ideal for parsing raw API responses and batching operations. |
| RUBE_REMOTE_BASH_TOOL | Executes bash commands in a remote sandbox for file manipulation and shell-based post-processing between tool calls. |
| RUBE_FIND_RECIPE | Finds reusable recipes (saved multi-step workflows) using natural-language search. |
| RUBE_GET_RECIPE_DETAILS | Retrieves the full details and steps for a specific recipe by ID. |
| RUBE_CREATE_UPDATE_RECIPE | Converts an executed workflow into a reusable recipe (notebook); used when a workflow is complete or the user explicitly asks to save it. |
| RUBE_EXECUTE_RECIPE | Runs a previously saved recipe end to end. |
| RUBE_MANAGE_RECIPE_SCHEDULE | Manages scheduled, recurring runs for a recipe. |
What you can do with it
One server for every app your agent touches
Connect Rube once and let the agent reach Gmail, Slack, GitHub, Notion, Linear, and hundreds more without configuring a separate MCP server per app. It searches for the right tool, fetches its schema, and executes — keeping the context window small.
Cross-app automations with parallel execution
Ask the agent to pull issues from GitHub, summarize them, post to Slack, and file follow-ups in Linear. Rube plans the steps, manages the OAuth connections, and runs the tools in parallel, with a remote sandbox to post-process results.
FAQ
- Is it free?
- Yes, there is a free plan for Rube that covers individual use across the connected apps, with paid tiers for higher usage and team features. You only need a Composio/Rube account; usage of each underlying app is governed by your own accounts and the credentials you authorize.
- Does it support remote/OAuth?
- Yes. The canonical deployment is the remote endpoint at https://rube.app/mcp using OAuth. The first time an agent uses an app, Rube returns an authentication link and runs the per-app OAuth (or API-key) flow; Composio encrypts the tokens and lets you revoke them. Clients without native HTTP support can bridge via the npx @composio/mcp setup helper.