Composio
Give the Sazabi agent tools from the Composio toolkits and connected apps you have configured, through a single hosted MCP endpoint.
All Composio integration capabilities
About
This is an MCP connector that gives the Sazabi agent tools from Composio's hosted Connect MCP server (connect.composio.dev/mcp). Composio aggregates many SaaS integrations behind one endpoint — the agent can call tools from whatever toolkits you have connected in your Composio account. Sazabi stores your Composio API key securely and sends it as the x-consumer-api-key header on each request to Composio's MCP endpoint. Write operations are governed by the per-connection read-only toggle and your organization's tool policy.
What the agent can do:
- Call tools from your configured Composio toolkits and connected apps
- Reach many SaaS integrations through a single connection
Prerequisites
- A Composio account with a configured toolkit or connected apps
- A Composio API key, created in the Composio dashboard
Set up in the dashboard
Configure connectors in the dashboard under Settings > MCP connectors.
Open the connector
Find Composio in Settings > MCP connectors.
Add your key
Before connecting, make sure you have connected the toolkits you want the agent to use in the Composio dashboard. The MCP server only exposes tools for apps you have already connected.
In the Composio dashboard, open Settings > Project Settings and copy your project API key from the API Keys section (or use the AI Clients page). Paste the key into Sazabi. Sazabi stores it securely and sends it as the x-consumer-api-key header to Composio's Connect MCP endpoint at https://connect.composio.dev/mcp.
Set up with the CLI
Composio authenticates with a Composio API key. With the Sazabi CLI installed and authenticated (see sazabi mcp-connectors reference), connect it in one command, passing the credential as a header:
sazabi mcp-connectors connect composio --header x-consumer-api-key=<api-key>The CLI connects to the MCP server at once and prints the connection with the tools it discovered; a credential the server rejects is reported, and the connection is left needing attention. Use NAME=@<file> to read a value from a file, or --header-file <file.json> for a JSON object of header names and values. To rotate the stored credentials later, use sazabi mcp-connectors update-credentials <connection-id>; find the connection ID with sazabi mcp-connectors list.
Verify
Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm the API key is correct and that you have connected at least one toolkit in your Composio account.
Troubleshooting
No tools discovered — Confirm you have connected at least one toolkit in the Composio dashboard and that the API key is correct.
Connection shows needs attention — The API key may have expired or been revoked; create a new key and reconnect from Settings > MCP connectors.