Composio
Composio enables AI Agents and LLMs to authenticate and integrate with various tools via function calling.
Verdict
Common use cases
- Sync calendar events to project tracker
- Triage support tickets across platforms
- Post standup summaries to Slack channels
- Create GitHub issues from chat requests
- Download reports from S3 for review
Integration
- Vendor
- Composio
- Category
- other
- Auth
- NONE
- Tools
- 30
- 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
This is a workflow builder that ensures the LLM produces a complete, step-by-step plan for any use case. WHEN TO CALL: - Call this tool based on COMPOSIO_SEARCH_TOOLS output. If search tools response indicates create_plan should be called
- 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
Process **REMOTE FILES** or script BULK TOOL EXECUTIONS using Python code IN A REMOTE SANDBOX. If you can see the data in chat, DON'T USE THIS TOOL. **ONLY** use this when processing **data stored in a remote file** or when scripting bul
- 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 user auth to finish. Call ONLY after you have shown the Auth link from COMPOSIO_MANAGE_CONNECTIONS. Wait until mode=any/all toolkits reach a terminal state (ACTIVE/FAILED) or timeout. Example Input: { toolkits: ["gmail","outlook"
- Wait for connection
Wait for connections to be established for given toolkits.
Setup
Setup guide
- 11. In your Switchy workspace, navigate to Settings → Integrations → Add MCP Server. 2. Select Composio from the directory and click Connect. 3. No authentication is required for the Composio MCP itself—it runs locally and manages connections to other services on your behalf. 4. To test, open any Space and type '@Composio ask oracle' to retrieve the system prompt explaining available workflows. 5. Before invoking tools for a specific app (like Slack or GitHub), you'll need to authenticate that service through Composio—the MCP will return connection instructions when you attempt to use a tool without an active session. 6. Once connected, invoke actions by @mentioning Composio followed by the tool name and parameters, such as '@Composio check multiple active connections toolkits=["github", "slack"]'.
What teammates see: by default, memories from Composio are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Audit Active Integrations
@Composio check multiple active connections for all toolkits we've configured. Show me which services are active and which need re-authentication.Open in a Space →
Plan Multi-Step Workflow
@Composio create a plan to pull this week's closed GitHub issues, summarize them by label, and post the summary to our #engineering Slack channel.Open in a Space →
Fetch S3 Report
@Composio download the monthly metrics report from s3://our-bucket/reports/2024-01.csv and show me the first 10 rows.Open in a Space →
Enable Event Trigger
@Composio enable a trigger for new Jira tickets assigned to our team. Post a message here whenever one arrives.Open in a Space →
Save Workflow as Recipe
@Composio we just ran a workflow to sync calendar events to Asana. Save that as a recipe called 'calendar_sync' so we can reuse it weekly.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@composio check which of my team's accounts are actively connected to Slack, GitHub, and Linear right now
Based on the active connection check, here's what I found: Your Slack workspace (team-acme) is connected and active with full message and channel permissions. GitHub shows two connected accounts — one for the main org repo (expires in 14 days) and one personal account. Linear has no active connection; you'll need to authorize it through the Composio dashboard before I can interact with Linear issues. All active connections are using OAuth2 with refresh tokens.
This example shows Composio's connection-status tooling, which is critical before attempting multi-app workflows. Note that connection details vary by user and expire over time — the MCP returns what's currently authorized, not a static list. You'll need to re-auth expired integrations before the AI can act on them.
@composio create a plan to sync all high-priority Linear issues into a new Slack channel and post daily summaries at 9am
I've built a 4-step workflow plan: (1) Query Linear for issues tagged 'high-priority' and status 'In Progress' or 'Todo'. (2) Create a dedicated Slack channel named #priority-tracker if it doesn't exist. (3) Post each issue as a threaded message with title, assignee, and due date. (4) Schedule a daily trigger at 9am to re-run steps 1–3 and summarize changes since yesterday. This plan is now stored in Composio's workflow builder; you can execute it immediately or convert it to a reusable recipe for future runs.
This demonstrates Composio's workflow-planning capability, which structures multi-step automations before execution. The plan is declarative — it doesn't run until you confirm. Be aware that enabling the daily trigger requires setting up Composio's webhook infrastructure, and you'll need active connections to both Linear and Slack before execution starts.
@composio enable a trigger that notifies me in Slack whenever a new GitHub PR is opened in our main repo
Trigger enabled successfully. I've configured a GitHub webhook listener for the 'pull_request.opened' event on your main repository. Whenever a new PR is created, Composio will capture the PR title, author, and branch name, then post a formatted message to your #dev-notifications Slack channel. The trigger is live now and will persist until you disable it. You can view or modify trigger settings in the Composio dashboard under 'Active Triggers'.
This showcases Composio's event-driven trigger system, which bridges real-time events across apps. The trigger runs outside of Switchy — it's a persistent automation managed by Composio's infrastructure. Be mindful of webhook rate limits if your repo has high PR volume, and ensure your GitHub connection has webhook-creation permissions (typically requires admin or write access).
Use-case deep-dives
When Composio handles cross-app ticket workflows at scale
A 6-person support team fields 200 tickets daily across Zendesk, Slack, and Linear. Composio's 30-tool catalog lets you chain actions—pull ticket from Zendesk, check Slack thread context, create Linear issue if escalated—without writing custom integrations. The Ask Oracle tool returns a system prompt that guides the AI through multi-step workflows, and Create Plan structures the routing logic before execution. This works when your team runs predictable escalation paths and the ticket volume justifies automation overhead. If you're under 50 tickets a week or your routing rules change constantly, the setup cost outweighs the gain. For teams at 100+ tickets with stable triage logic, Composio turns a 15-minute manual handoff into a 2-minute automated flow.
Composio bridges CRM and spreadsheet workflows for small sales teams
A 4-person sales team tracks deals in HubSpot but runs weekly forecasts in Google Sheets. Composio's connection-check tools verify active auth across both platforms, then trigger workflows that pull deal stage updates and push them to the forecast sheet on a schedule. The Create Recipe feature converts a one-time sync into a reusable notebook, so the ops lead doesn't rebuild the flow each quarter. This makes sense when your CRM and reporting tools don't natively integrate and you need bi-directional sync. If your sales cycle is under 30 days or you only update forecasts monthly, manual exports are faster. For teams closing 20+ deals a month with weekly forecast reviews, Composio eliminates the Friday-afternoon copy-paste ritual.
When Composio automates on-call handoffs across PagerDuty and Slack
A 10-engineer team rotates on-call shifts and logs incidents in PagerDuty, posts updates in Slack, and tracks root-cause tickets in Jira. Composio's trigger-enable tool listens for PagerDuty alerts, then fires a workflow that creates a Slack thread, assigns a Jira ticket, and notifies the on-call engineer. The workflow builder ensures each step completes before the next starts, so nothing falls through the cracks during a 3am page. This pays off when your incident volume is high enough that manual coordination burns time—typically 5+ incidents a week. If you're under that threshold or your team prefers ad-hoc Slack threads, the automation adds complexity without saving hours. For teams handling 20+ incidents monthly, Composio turns a 10-minute scramble into a 1-click response.
Frequently asked
What does the Composio MCP do in Switchy?
Composio acts as a meta-integration layer that lets your AI agents connect to 200+ external apps through a single MCP. Instead of installing separate MCPs for Slack, GitHub, Gmail, etc., you authenticate once with Composio and the AI can orchestrate multi-step workflows across those tools. It's designed for complex automation, not quick one-off queries.
Do I need to authenticate with each app Composio connects to?
Yes. Composio itself requires no auth in Switchy, but each underlying app (Slack, Notion, etc.) needs its own OAuth or API key connection through Composio's platform. The "Check active connection" tool tells you which apps are connected and which need setup. You manage those credentials in Composio's dashboard, not in Switchy.
Can Composio execute workflows automatically or does the AI need to trigger each step?
The AI triggers each step. Composio's "Create Plan" tool generates a multi-step workflow, but your agent must call the individual tools (send Slack message, create GitHub issue, etc.) in sequence. It's not a background scheduler. If you want fully automated triggers, you'd set those up in Composio's platform separately.
How is this different from connecting apps directly via their own MCPs?
Composio shines when you need cross-app workflows—like "search Gmail, summarise in Notion, post to Slack". A single-app MCP is simpler and faster for one-tool tasks. Composio adds latency (extra API hops) but saves you from wiring 10 different MCPs together. Use it when orchestration complexity justifies the trade-off.
Who on the team should set up the Composio connections?
Whoever has admin or OAuth access to the apps you want to automate. Once connected in Composio, any Switchy workspace member can invoke those tools through the MCP. The 30-tool limit in this MCP is a Composio platform constraint, not a Switchy seat limit—check your Composio plan for details.