Specific implementation researched
Composio
Implementation, permissions and documented client compatibility.
A directory listing or verification does not replace a security audit. No installation is triggered automatically here. Do not enter API keys in public forms.
What is specifically documented?
- Connected service
- Composio
- Publisher
- Composio
- Origin
- Officially from the named publisher
- Deployment mode
- Remote
- Transport
- HTTP
- Authentication
- Composio login; connected apps are authorized through their respective OAuth permissions.
- Read capabilities
- Find app tools and retrieve schemas · Read data through connected apps
- Write capabilities
- Execute actions in connected apps · Manage app connections · Execute Python and Bash in a remote sandbox
- Permissions
- Meta-tools discover and launch actions in connected apps. Individual apps are authorized through OAuth; connections persist across sessions.
- Required plan
- No confirmed information
- Additional costs
- No confirmed information
- Maintenance status
- Documented Composio Connect endpoint for MCP clients; developer sessions are a separate offering.
- Review date
- 11/10/2026
Support by client
Documented setup is not an independent functional test. General MCP support does not imply full compatibility.
| Client | Status | Source |
|---|---|---|
| Claude Desktop | Setup documented | Documentation ↗ |
| Claude Code | Not verified | — |
| Claude Web | Not verified | — |
| Cursor | Not verified | — |
Sources & implementation
Composio Connect | Composio ↗Retrieved on 11/10/2026. Provider statements, not a security audit.
Implementation: https://connect.composio.dev/mcp