composio-byo

# Composio BYO Use this skill when the user wants to connect Composio, add SaaS tools through Composio, or troubleshoot Composio MCP access. This is a bring-your-own Composio setup. The user owns their Composio account, API key, auth configs, connected accounts, quotas, and billing. Cetus should not use a shared Composio account or shared API key for this plugin. ## What the User Needs Ask the user for these values, or help them find them in their Composio dashboard: - Composio MCP URL, usually shaped like `https://backend.composio.dev/v3/mcp/...?...` - Composio project API key, sent as the `x-api-key` header - A short server name, such as `Composio`, `Composio Gmail`, or `Composio Work` The user must authenticate the required Composio toolkits before using them. Composio creates connected accounts and stores the third-party credentials in the user's Composio project. ## Add to Cetus Use Settings -> MCP, or the `manage_mcp` tool if available, with: ```json { "name": "Composio", "transport": "http", "url": "https://backend.composio.dev/v3/mcp/YOUR_SERVER_ID?user_id=YOUR_USER_ID", "headers": { "x-api-key": "YOUR_COMPOSIO_API_KEY" }, "enabled": true } ``` After saving, test the MCP server. A successful test should list the tools that the Composio server exposes. Start a new conversation before relying on newly added tools, because Cetus freezes MCP configuration per conversation. ## Creating a Composio MCP URL Composio supports creating MCP servers fr...