Custom MCP connection to Ideogram (https://mcp.ideogram.ai/mcp) fails during OAuth token exchange: "OAuth provider rejected the token exchange: Request failed with status code 401." Reproduced on retry with a confirmed active Ideogram account.

Thanks for flagging this! We've updated the Ideogram connection settings and tested that a fresh OAuth connection completes successfully. Please retry by starting a new connection using https://mcp.ideogram.ai/mcp (with no trailing dot). If you’re creating the custom MCP again, name it Ideogram so it picks up the update. It should connect successfully now. Let us know if you still run into any issues. Sent by Composio Support Agent

Issue: Ideogram custom MCP connector shows "Active" in dashboard but isn't functional/callable Details: Added Ideogram as a custom MCP connector (https://mcp.ideogram.ai/mcp) First attempt failed with: OAuth provider rejected the token exchange: Request failed with status code 401 Retried and it eventually completed — dashboard now shows Ideogram as Active with 1 connection However, the API/tool-execution side still reports the connection status as "initiated," not active, and no Ideogram tools are exposed for use — so the connection isn't actually usable despite showing Active in the UI Ask: Is this a known sync issue between dashboard status and backend tool registration for custom MCP connectors? Any way to force it to finish registering, or is this a bug on your end?

Hi, Thanks for clarifying the current state. This is separate from the original 401: OAuth eventually completed, but an active connection alone does not mean the Custom MCP tools have finished syncing and become available to a session. Please trigger a tool sync for the Ideogram

CUSTOM_*

toolkit using its active connected account. After it succeeds, make sure the session includes that toolkit and can select the same connected account. If automatic account matching is not enabled for its auth config, select the account explicitly in the session configuration. We cannot yet confirm that this is a known platform-wide sync issue. If the sync remains stuck at

initiated

or fails, please share the Composio log ID shown for that failed operation. That will distinguish a sync failure from a session or account-selection mismatch without requiring any credentials.