{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreid2n7qq4glfjsknrshtcngh7nsphbxoqcc2xdvgpamk4vlfymfqra",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3ml6kmoqg3aq2"
  },
  "path": "/t/oauth-mcp-server-works-in-chatgpt-developer-mode-create-app-but-fails-in-app-review-form-what-does-unsupported-oauth-config-type-really-mean/1380378#post_1",
  "publishedAt": "2026-05-06T09:54:03.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "chatgpt.com"
  ],
  "textContent": "Hi all,\n\nI’m hoping someone can help me understand an error I’m hitting, and why the behavior differs between two OAuth flows in ChatGPT.\n\n**The Problem**\n\nWith the same MCP server URL, with the same OAuth configuration:\n\n  * Works perfectly when connected via **chatgpt.com → Developer Mode → Create App.** The server supports both pre-defined and DCR modes no problems!\n\n  * Fails in the **App Review submission form** at Step 2 (“MCP Server”) when clicking **Scan Tools** , with:\n\n> `MCP details save failed: OAuth discovery returned unsupported OAuth config type`\n\n\n\n\nInterestingly, “Scan Tools” on the review form worked fine for me on **21 April 2026** with a test (unpublished) app. The failure started showing up recent, on **6 May 2026** (attempts around ~05:00 and ~10:00 GMT+0800) against the same server.\n\n**What I’m trying to understand**\n\n  1. What does _“OAuth discovery returned unsupported OAuth config type”_ actually mean? Which part of the OAuth discovery document is it reporting an error about?\n  2. Why would the App Review form’s OAuth discovery treat a server differently from Developer Mode’s “Create App” flow, if both are ostensibly doing MCP OAuth discovery against the same URL?\n  3. Is there a stricter OAuth metadata requirement on the review path (e.g. specific `authorization_servers`, PKCE, or dynamic client registration fields) that Developer Mode doesn’t enforce? I’m struggling to debug what’s going on ~\n\n\n\n**Reproduction**\n\n  1. Create a new App Review draft, fill in details up to **Step 2: MCP Server**\n  2. MCP server URL: `https://example.com/api/mcp`\n  3. Auth mode: **OAuth**\n  4. Click **Scan Tools** → error dialog appears\n\n\n\nScreenshot of the error dialog:\n\nIf anyone has shipped an OAuth-backed MCP server through App Review recently, I’d love to know what discovery-document shape worked for you — and whether the two flows are expected to diverge.\n\nThank you!!",
  "title": "OAuth MCP server works in ChatGPT Developer Mode (\"Create App\") but fails in App Review form — what does \"unsupported OAuth config type\" really mean?"
}