- Use the consumer MCP URL directly. If the MCP client supports auth, it can trigger the Composio auth flow, open a popup, let the customer authenticate, and let them select the organization.
- Use the consumer API key when the MCP client does not support auth and only supports API keys/headers. Copy the key from the consumer dashboard and pass it as the
x-consumer-api-keyheader.
- When a Composio-managed auth app is available, the app uses that managed config and does not expose provider credentials for editing.
- When no managed app is available, Manage Auth appears for toolkits with editable customer-owned credentials or multiple auth schemes. Enter the provider client ID/secret or other required fields there and register the callback URI shown by the current form.
- Provider scopes are determined by the selected auth scheme and its current config. A managed app is limited to its approved scope set; customer-owned apps must configure and verify their scopes with the provider.
Rotate the Connect MCP consumer key
These steps apply to a Connect consumer key with theck_* prefix, sent as x-consumer-api-key. They do not apply to a Platform Project API key with the ak_* prefix. Reconnecting Gmail, Calendar, or another individual app does not rotate the consumer key.
- Open For You / Connect.
- Select Settings in the left sidebar.
- Open Sessions & API Key.
- Select Regenerate next to “Your API Key” and confirm.
- Update every MCP client that uses
https://connect.composio.dev/mcpwith the newx-consumer-api-keyvalue.
Workspace members do not automatically share For You connections
In the normal For You/Connect MCP flow, connected accounts belong to the member who authorized them. Another teammate using their own Connect MCP endpoint orck_* consumer key resolves to their own connected accounts, not yours.
- Admins can manage workspace settings and members, but their own Connect MCP session does not automatically use another member’s accounts.
- Members can connect and use their own accounts.
- Viewers cannot connect or invoke tools from the For You surface.
ak_* Project API keys are different from ck_* consumer keys and must be treated as privileged project secrets. Explicitly shared or pinned connections are also a separate configuration from ordinary member-scoped connections.
Shared connections must be explicitly allowed and pinned
A normalPRIVATE connection belongs to the user who created it. A SHARED connection can be used by other user IDs only when its ACL allows them and the connection is explicitly pinned into the session by connected-account ID. Shared connections are deny-by-default and are never selected implicitly.
Follow the Shared Connections guide for the current ACL and session configuration.