ChatGPT Compatibility

The current Ideagram endpoint requires a personal access token in an Authorization: Bearer ... header. Do not assume that a client described as "ChatGPT-compatible" accepts the same configuration as Cursor.

ChatGPT Web

OpenAI documents remote MCP developer-mode apps with OAuth, no authentication, or mixed authentication. The documented setup does not provide the arbitrary bearer-header configuration used by Ideagram's current PAT endpoint. See OpenAI's developer-mode guide.

Ideagram does not currently implement the OAuth authorization flow required for that authenticated setup. Direct connection from ChatGPT web is therefore not a supported setup in this guide. A local mcpServers JSON block does not configure ChatGPT web, and choosing "No authentication" will not authenticate to Ideagram.

Clients With Custom Headers

Use Cursor or Claude Code for the documented PAT setup. Other MCP clients must explicitly support Streamable HTTP and a custom Authorization header.

Do not put a token in a URL or disable server authentication to work around a client's limitations. OAuth support remains future work.