Composio
Composio enables AI Agents and LLMs to authenticate and integrate with various tools via function calling.
Verdict
Common use cases
- Search for tools across connected platforms
- Send emails and Slack messages from chat
- Create GitHub issues from meeting notes
- Build multi-step workflows across apps
- Enable triggers for automated responses
Integration
- Vendor
- Composio
- Category
- other
- Auth
- NONE
- Tools
- 24
- Composio slug
composio
Tools
- Ask Oracle
Static helper that returns a comprehensive system prompt describing how to plan and execute tasks using the available composio tools and workflows. no inputs required; simply call to retrieve the prompt. always call this after the search to
- Check active connection (deprecated)
Deprecated: use check active connections instead for bulk operations. check active connection status for a toolkit or specific connected account id. returns connection details if active, or required parameters for establishing connection if
- Check multiple active connections
Check active connection status for multiple toolkits or specific connected account ids. returns connection details if active, or required parameters for establishing connection if none exists. active connections enable agent actions on tool
- Create Plan
Important - always call this after manage connections tool is executed. you are an efficient workflow builder, your job is to guide the llm to create a plan for the given use case
- Create / Update Recipe from Workflow
Convert the executed workflow into a recipe using Python Pydantic code. The recipe_slug parameter is required. If a recipe with the provided slug already exists, a new version will be created. If the slug does not exist, a new
- Create / Update Recipe from Workflow
Convert executed workflow into a reusable notebook. Only use when workflow is complete or user explicitly requests. --- DESCRIPTION FORMAT (MARKDOWN) - MUST BE NEUTRAL --- Description is for ANY user of this recipe, not just the creat
- Download S3 File
Download a file from a public s3 (or r2) url to a local path.
- Enable trigger
Enable a specific trigger for the authenticated user.
- Execute agent
Execute complex workflows using ai agent reasoning between multiple tool calls. use this for: complex multi-step workflows requiring reasoning, error handling and retry logic. use composio multi execute tool instead for: simple parallel ope
- Execute Code remotely in work bench
Use this persistent Jupyter sandbox only for **remote files** or scripted **bulk tool executions**. Do not use it for inline data, quick parsing or summaries, or basic math. USE IT TO - Parse or analyze tool outputs saved by COMPOSIO_MULT
- Execute Composio Tool
Execute a tool using the composio api.
- Execute Recipe
Executes a Recipe
- Get Existing Recipe Details
Get the details of the existing recipe for a given recipe id.
- Get Recipe Details by Slug
Get the details of an existing recipe by its slug. Returns the recipe's name, description, input/output schemas, and the toolkits it uses. Use this to inspect a recipe's structure before executing it.
- Get required parameters for connection
Gets the required parameters for connecting to a toolkit via initiate connection. returns the exact parameter names and types needed for initiate connection's parameters field. supports api keys, oauth credentials, connection fields, and hy
- Get response schema
Retrieves the response schema for a specified composio tool. this action fetches the complete response schema definition for any valid composio tool, returning it as a dictionary that describes the expected response structure.
- Get Tool Dependency Graph
Get the dependency graph for a given tool, showing related parent tools that might be useful. this action calls the composio labs dependency graph api to retrieve tools that are commonly used together with or before the specified tool. this
- Get Tool Schemas
Retrieve input schemas for tools by slug. Returns complete parameter definitions required to execute each tool. Only pass tool slugs returned by COMPOSIO_SEARCH_TOOLS — never guess or fabricate slugs. If unsure of the exact slug, call COMPO
- Initiate connection
Initiate a connection to a toolkit with comprehensive authentication support. supports all authentication scenarios: 1. composio default oauth (no parameters needed) 2. custom oauth (user's client id/client secret) 3. api key/bearer token a
- List toolkits
List all the available toolkits on composio with filtering options.
- List triggers
List available triggers and their configuration schemas.
- Manage connection
Manage a connection to a toolkit with comprehensive authentication support. supports all authentication scenarios: 1. composio default oauth (no parameters needed) 2. custom oauth (user's client id/client secret) 3. api key/bearer token aut
- Manage connections
Create or manage connections to user's apps. Returns a branded authentication link that works for OAuth, API keys, and all other auth types. Call policy: - First call COMPOSIO_SEARCH_TOOLS for the user's query. - If COMPOSIO_SEARCH_TOOLS
- Multi Execute Composio Tools
Fast and parallel tool executor for tools discovered through COMPOSIO_SEARCH_TOOLS. Use this tool to execute up to 50 tools in parallel across apps only when they're logically independent (no ordering/output dependencies). Response conta
- Retrieve Toolkits
Toolkits are like github, linear, gmail, etc. tools are like send email, create issue, etc programmatic functions that can be used to perform the action. not all toolkits support all tools. some toolkits support only a subset of tools that
- Run bash commands
Execute bash commands in a REMOTE sandbox for file operations, data processing, and system tasks. Essential for handling large tool responses saved to remote files. **Hard 3-minute (180s) execution limit** — break large tasks into smalle
- Search agent
Discover tools and analyze dependencies for complex workflows using ai agent. this action uses an ai agent to intelligently search for tools across toolkits and create optimized execution sequences with detailed instructions.
- Search Composio Tools
Tool Server Info: Composio connects 500+ apps—Slack, GitHub, Notion, Google Workspace (Gmail, Sheets, Drive, Calendar), Microsoft (Outlook, Teams), X/Twitter, Figma, Web Search / Deep research, Browser tool (scrape URLs, browser automati
- Wait for connection
Wait for connections to be established for given toolkits.
- Wait for connection
Wait for user auth to finish. Call only after the user confirms they have completed authentication. Wait until mode=any/all toolkits reach a terminal state (ACTIVE/FAILED) or timeout. Example Input: { toolkits: ["gmail","outlook"], mode:
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > MCP Servers. 2. Click 'Add MCP Server' and select Composio from the list. 3. No API key is required for this MCP — Switchy connects to Composio's local server instance running on your machine. 4. Click 'Connect' to authorize the integration. 5. Composio will prompt you to link external accounts (Gmail, Slack, GitHub, etc.) through its web dashboard at app.composio.dev. 6. Return to Switchy and create a new Project or open an existing one. 7. Type '@Composio' in the chat to invoke the MCP. 8. Test the connection by asking '@Composio check which accounts I have connected' — you should see a list of active integrations. 9. To execute an action, describe your task naturally: '@Composio send an email via Gmail to team@example.com with subject Update'.
What teammates see: by default, memories from Composio are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Check Connected Accounts
@Composio check which accounts I have connected and show me the active integrations
Send Cross-Platform Update
@Composio send 'Sprint demo at 3pm today' to our team Slack channel and also email it to stakeholders@company.com
Create Workflow Plan
@Composio create a plan to pull unresolved tickets from Jira, summarize them, and post the summary to Slack every Monday
Search Available Tools
@Composio search for tools that can create calendar events and tell me which accounts I need to connect
Enable Automation Trigger
@Composio enable a trigger that notifies me in Slack whenever a new GitHub issue is labeled 'urgent'
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@composio check which of my accounts are connected and active right now across all my integrated tools
Based on your Composio configuration, you have 3 active connections: GitHub (connected as @yourhandle, expires in 14 days), Slack (workspace: YourTeam, connected 2 hours ago), and Gmail (account: you@company.com, OAuth valid). No authentication is required to refresh these. Your Notion connection expired 3 days ago and needs re-authorization before use.
This example shows Composio's connection-management layer, which tracks auth state across dozens of integrations. Useful before attempting multi-tool workflows. Note that connection details depend on what you've previously authorized in Composio's dashboard — this MCP cannot create new connections, only report and use existing ones.
@composio create a plan to sync all my GitHub issues labeled 'bug' into a new Notion database, then post a summary to our #eng-updates Slack channel
I've generated a 4-step workflow plan: (1) Authenticate GitHub and Notion connections, (2) Query GitHub Issues API filtering by label='bug', (3) For each issue, create a Notion page in your specified database with title, status, and assignee fields mapped, (4) Format a summary message and post to Slack channel #eng-updates via webhook. This plan is now ready to execute — confirm to proceed, or I can save it as a reusable recipe for future runs.
Composio's planning tool breaks complex multi-service tasks into discrete steps, then orchestrates execution across APIs. This example highlights cross-tool synthesis (GitHub → Notion → Slack). Be aware that execution depends on active connections for all three services, and rate limits apply per vendor (GitHub: 5000 req/hr, Notion: 3 req/sec).
@composio enable a trigger so I get notified in this chat whenever a new pull request is opened in our main repo
Trigger enabled: I've configured a GitHub webhook listener for repository 'yourorg/main-repo' that fires on 'pull_request.opened' events. When a new PR is created, Composio will push a notification to this Switchy project with PR title, author, and link. You can disable this trigger anytime by calling the disable-trigger tool with trigger_id='gh_pr_main_12345'.
This demonstrates Composio's event-driven capabilities — instead of polling APIs, you subscribe to real-time webhooks. Requires an active GitHub connection with repo-level permissions. Trigger state persists across Switchy sessions, so you'll receive notifications even when this project is closed. Manage active triggers via Composio's dashboard to avoid notification fatigue.
Use-case deep-dives
When Composio makes sense for cross-platform workflows
A 6-person ops team runs weekly vendor audits that touch Slack, Google Sheets, and their internal ticketing system. Composio's 24-tool catalog and workflow builder let them chain actions across platforms without writing custom integrations. The "Create Plan" tool is the hook: it scaffolds multi-step sequences the LLM can execute in one pass. The trade-off is setup friction—each toolkit needs its own connection check, and the "Ask Oracle" prompt is a 200-word system message you'll paste into every relevant chat. If your workflow touches fewer than three external tools, a single-purpose MCP (like Google Drive or Slack) is faster. If you're orchestrating four or more, Composio's unified interface pays off. Best for teams that already know which platforms they need to connect and want one MCP to rule them all.
Why Composio isn't the right call for pure search
A 3-person support team wants to pull answers from Notion, Confluence, and Zendesk during live chats. Composio's toolkit includes connectors for all three, but the "Check active connection" and "Enable trigger" overhead means you're managing auth state for each platform before you can query. The real blocker: Composio's design assumes you're building workflows, not running one-off searches. The "Create Plan" tool is overkill when you just need a fast semantic lookup. A dedicated knowledge-base MCP (like Notion or Confluence standalone) gives you instant read access without the workflow scaffolding. Use Composio if your support flow includes writing back to those platforms—creating tickets, updating docs, posting Slack summaries. If you're only reading, a lighter MCP wins on speed and setup simplicity.
When Composio's recipe builder justifies the learning curve
A 5-person sales team syncs deal stages between HubSpot and their custom CRM every morning. Composio's "Create / Update Recipe from Workflow" tool lets them codify the sync logic once, then reuse it as a notebook-style automation. The workflow builder ensures the LLM doesn't skip steps—critical when you're moving money data between systems. The catch: the initial recipe creation takes 20-30 minutes of trial runs to get the parameter mapping right, and the "Ask Oracle" prompt is mandatory reading for anyone on the team who'll modify the workflow. If your sync is a one-time migration, the setup cost isn't worth it. If you're running the same multi-platform update daily or weekly, Composio's recipe model saves you from re-explaining the sequence every time. Best for teams with repeating cross-tool workflows who can invest the upfront config time.
Frequently asked
What does the Composio MCP do in Switchy?
Composio MCP gives your AI agents access to 200+ third-party app integrations through a single connection. Instead of building separate MCPs for Slack, GitHub, Gmail, etc., you connect Composio once and your agents can orchestrate actions across all supported apps. It's a meta-integration that routes tool calls to the underlying services.
Do I need API keys for each app Composio connects to?
Yes. Composio itself requires no auth in Switchy, but each underlying app (Slack, Notion, Salesforce) needs its own OAuth or API key connection. You authenticate those apps through Composio's dashboard, then reference the connected account ID when calling tools. The MCP doesn't store credentials — it proxies requests to Composio's API.
Can Composio MCP execute multi-step workflows automatically?
Partially. The "Create Plan" tool generates a step-by-step execution plan, but your agent still calls each action sequentially. Composio doesn't run workflows server-side like Zapier. If you need true background automation, use the "Create / Update Recipe from Workflow" tool to convert a completed workflow into a reusable notebook, then trigger it outside Switchy.
How is this different from connecting apps directly via their MCPs?
Direct MCPs (GitHub MCP, Slack MCP) give you full control and lower latency. Composio trades that for breadth — you get 200+ apps through one integration, but you're dependent on Composio's API uptime and rate limits. Use Composio when you need many apps quickly; use direct MCPs for mission-critical workflows in a single app.
Who on the team should set up Composio connections?
Whoever owns the API keys for your third-party apps. Composio connections are account-level, not workspace-level, so the person connecting Slack or HubSpot must have admin access to those tools. Once connected, any Switchy team member can reference those connections in prompts by passing the connected account ID to the MCP tools.