Plugins submission: OAuth secret field disappears; Connect rejects imported clientId

We cannot complete OAuth setup for a public plugin submission. The portal displays the imported client configuration, but Connect rep


orts:

MCP details save failed: OAuth client ID is required when using pre-defined OAuth client credentials.

Environment

  • OpenAI Platform public Plugins submission portal: https://platform.openai.com/plugins
  • Verified publisher organization: Tapify
  • Plugin ID: plugin_asdk_app_6acd61b590e4819188d4b7f44d527015
  • MCP app ID: asdk_app_6acd61b590e4819188d4b7f44d527015
  • macOS; reproduced in Brave, and the publisher reports the same behavior in Safari.
  • Reproduction window: October 12, 2026, approximately 22:49–22:51 UTC.
  • MCP endpoint: https://mcp.tapify.ro/mcp
  • Domain verification succeeds.

Reproduction

  1. Upload a plugin ZIP containing the following mcp.json.
  2. Open MCPs → Tapify → Connect.
  3. Confirm the imported settings show mode: provided, the client ID, and client_secret_basic.
  4. The OAuth Client Secret input briefly appears during loading, then disappears.
  5. Click Connect. The portal reports that the OAuth client ID is required, despite displaying it in the saved configuration. No OAuth sign-in starts.
{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/mcp.schema.json",
  "mcpServers": {
    "tapify": {
      "type": "streamable-http",
      "url": "https://mcp.tapify.ro/mcp",
      "extensions": {
        "com.openai": {
          "auth": {
            "type": "oauth",
            "client": {
              "mode": "provided",
              "clientId": "tapify-mcp-chatgpt",
              "tokenEndpointAuthMethod": "client_secret_basic"
            }
          }
        }
      }
    }
  }
}

The same draft initially used {"mode":"cimd"}. That also failed with the same predefined-client-ID error. Refreshing the page did not fix it. A separate personal custom-MCP connection has worked, but public submission setup remains blocked.

Expected behavior

The provided-client configuration should honor the imported client ID and show the secure secret input. CIMD should use its configured registration flow without requiring a predefined client ID.

Official reference: Upload and submit your plugin – Plugins | OpenAI Developers

Diagnostics

The registered OAuth client is active, requires PKCE and consent, uses client_secret_basic, and permits https://chatgpt.com/connector_platform_oauth_redirect. Live discovery advertises CIMD support and S256 PKCE.

During a fresh Connect reproduction with DevTools Network recording, we did not identify a failed API request corresponding to the save error. Observed app-read and configuration-refresh requests succeeded. Therefore no failing request’s x-request-id is available; the validation may occur in the browser, but that is not confirmed.

The support assistant acknowledged a possible portal save/validation mismatch and directed us to this forum. Can the team inspect this draft’s imported configuration versus the Connect form’s resolved authentication state, or provide a supported workaround?

Screenshot below shows the imported provided-client configuration and missing secret field. No client secrets, tokens, cookies, or customer data are included.

Hit the same error and found the cause, in case it helps others.

@OpenAI: the CIMD-only case looks like a bug, since your docs and the MCP spec both treat CIMD as sufficient on its own.

Cause: the portal seems to require a registration_endpoint (DCR) in your authorization server metadata, whatever client.mode you declare. Our server is CIMD-only (as the MCP 2026-07-28 spec recommends) and advertises client_id_metadata_document_supported: true.

Our logs show the portal’s backend fetching that metadata successfully and still failing with "OAuth client ID is required when using pre-defined OAuth client credentials".

The same plugin pointed at a server that advertises DCR next to CIMD connects fine, and then uses ChatGPT’s CIMD client (https://chatgpt.com/oauth/client.json), so the endpoint only seems to be checked for presence.

Workaround (no DCR needed):

  1. Host your own client metadata document, e.g. https://yourdomain.com/.well-known/chatgpt-oauth-client.json, with client_id set to its own URL, redirect_uris: ["https://chatgpt.com/connector_platform_oauth_redirect"], token_endpoint_auth_method: "none",
    grant_types: ["authorization_code", "refresh_token"], response_types: ["code"].

2. In mcp.json:

"auth": { "type": "oauth", "client": { "mode": "provided", "clientId": "https://yourdomain.com/.well-known/chatgpt-oauth-client.json", "tokenEndpointAuthMethod": "none" } }

  1. Delete the plugin and create a new one. Uploading a new version doesn’t replace the saved MCP auth settings, which made our earlier attempts look broken when they weren’t.

Your server resolves that client ID as a normal CIMD client.

Same here, 2026-10-13. Plugin plugin_asdk_app_6ace348cacd88191ab927642d0d5bc4c, remote MCP server with OAuth, ZIP upload.

Four packages on the same draft, each uploaded with “Upload new version”, all fail on Connect with “MCP details save failed: OAuth client ID is required when using pre-defined OAuth client credentials”:

  1. client.mode: "cimd"
  2. client.mode: "dcr"
  3. auth: {"type":"oauth"} with no client object
  4. client.mode: "provided", clientId: "https://chatgpt.com/oauth/client.json", tokenEndpointAuthMethod: "none"

In case 4 the panel shows the imported client ID in the settings JSON, and Connect still says the client ID is required.

Our authorization server advertises both client_id_metadata_document_supported: true and a registration_endpoint, so a missing DCR endpoint does not explain it in our case. Domain verification passes. No save request leaves the browser when Connect is clicked. The same server works in ChatGPT as a custom MCP server.

Same here, 2026-10-13. ZIP-created plugin. Domain verification succeeds. Connect shows Authorization unavailable, the settings JSON includes our pre-registered client ID, and there is no OAuth Client Secret field.

Clicking Connect fails in the page with:

MCP details save failed: OAuth client ID is required when using pre-defined OAuth client credentials.

The imported settings are mode: "provided", tokenEndpointAuthMethod: "client_secret_basic", and baseScopes: ["all"], plus the authorization and token URLs. Our authorization server advertises S256, client_secret_basic, and client_secret_post. It does not advertise dynamic client registration or a client metadata document. Adding the endpoint URLs to mcp.json did not change the error. Uploading a new version did not either.

Has anyone found a resolution for a pre-registered client that requires client_secret_basic?

workaround: The Connect dialog never saves the imported client. Use the MCP editor, which is the screen that still has the fields.

https://platform.openai.com/plugins/apps/edit/<app id>/<version id>?section=MCP%20Server

The app id is the plugin id without the plugin_ prefix. Open Advanced settings. Token endpoint auth method is set to None, which is why the secret field is missing and Connect fails in the page with “OAuth client ID is required” before any request is sent. Change it to Client Secret Basic, fill OAuth Client ID and the client secret, then click Scan Tools.

The Callback URL on that page has to be an exact redirect URI on the OAuth client. Ours was https://chatgpt.com/connector/oauth/``<callback id>, because our authorization server does not advertise authorization_response_iss_parameter_supported. Uploading a new ZIP does not update these fields.

Hi @tapify, your mcp.json already has the right fields for a provided client. You don’t need to add DCR.

Can you try the MCP Server editor workaround above, with Client Secret Basic selected? Enter the client ID and secret there, then choose Scan Tools. Use the exact callback URL shown by that connection. You can try this on the existing plugin.

hey @OpenAI_Support, can you verify if this workaround is the right path to fix this? when trying to use it I’m hitting a 500 status request and that’s blocking my plugin submission completely

Thanks @bendersej and @OpenAI_Support. Following up with what actually worked for us.

On October 13, we created a separate, fresh diagnostic plugin draft, keeping the original failing draft intact, and used this configuration in mcp.json:

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/mcp.schema.json",
  "mcpServers": {
    "tapify": {
      "type": "streamable-http",
      "url": "https://mcp.tapify.ro/mcp",
      "extensions": {
        "com.openai": {
          "auth": {
            "type": "oauth",
            "client": {
              "mode": "provided",
              "clientId": "https://chatgpt.com/oauth/client.json",
              "tokenEndpointAuthMethod": "none"
            }
          }
        }
      }
    }
  }
}

Our authorization server already supported CIMD and allowed that exact ChatGPT client metadata URL, so it resolved the URL as a public OAuth client. No client secret was needed, and we did not add DCR or host our own client metadata document.

With that fresh draft:

  1. Connect saved the configuration without the “OAuth client ID is required” error.
  2. The flow reached our sign-in and consent screens, using S256 PKCE and the expected MCP resource.
  3. After sign-in, the portal showed Account connected.
  4. It discovered all 31 tools and completed the scan.

In our successful test, the callback was https://chatgpt.com/connector_platform_oauth_redirect. Other setups should use the exact callback and client metadata URL shown for their connection, since these can vary.

This is a variation of @bendersej’s workaround: we used ChatGPT’s official metadata document instead of hosting our own, and created a separate draft rather than deleting the original. Because we changed both the client configuration and the draft, we cannot isolate which part caused the original failure or confirm that uploading a new version to the existing draft would have fixed it.

@OpenAI_Support, thanks for the MCP Server editor suggestion. Our successful test predates that reply and used the public-client approach above, so we haven’t verified the Client Secret Basic → Scan Tools workaround.

To be precise about the outcome: OAuth connection and the authenticated tool scan succeeded. That did not mean the plugin was approved or published; review findings and submission steps remained.

Thanks for posting this. The older editor workaround fixed it for us too, with one difference: our public OAuth client uses None, so we left that setting alone.

The newer Connect dialog showed our client ID, but the OAuth Client ID field in the older editor was blank.

We opened:
https://platform.openai.com/plugins/apps/edit/<app_id>/<mcp_version_id>?section=MCP%20Server

Then expanded Advanced settings, entered our existing client ID, and clicked Scan Tools. Registration stayed Pre-defined, and token endpoint authentication stayed None.

After authorization, the existing draft showed Configured / Authorized and completed tool discovery and scanning. We didn’t need a new draft, client secret, DCR or CIMD.

Hopefully that helps anyone using a pre-registered public client who’s hitting the same error.

Thanks for the updates, @tapify and @dyeoman2. If your client uses None, keep that setting; no client secret is needed.

@superset-jvmaia, your October 15 request used a submission ID where the editor expected an app-version ID. That caused the 500 before OAuth started. The older editor link now redirects to plugin management, so those Advanced settings steps are no longer current.

Hi @OpenAI_Support, I have the same issue and the MCP Server editor is no longer available (the link redirects to plugin management).

Plugin: plugin_asdk_app_6ad7492152908191afaba9cc9198b8b3
Submission: appsub_6ad7492152bc81919cb6551114bf2500

My mcp.json declares extensions["com.openai"].auth with client.mode: "provided", clientId: "altfins-chatgpt-connector", tokenEndpointAuthMethod: "client_secret_basic". The portal shows this config, but Connect fails with “MCP details save failed: OAuth client ID is required when using pre-defined OAuth client credentials.” There is no field to enter the client ID or secret. Where can I enter them now, or can you fix this on your side?

Same client-side Connect failure for us — including with mode: "dcr" (no predefined client ID expected).

Plugin

  • Plugin ID: plugin_asdk_app_6ad7d85ef0dc8191923d1c2d1ce90cc2
  • App ID: asdk_app_6ad7d85ef0dc8191923d1c2d1ce90cc2
  • Org: Dabarli
  • Version: 1.0.9 (draft, not submitted)
  • MCP endpoint: https://mcp.dabarli.app/mcp
  • Domain verification: succeeds

mcp.json (relevant)

"auth": {
  "type": "oauth",
  "client": { "mode": "dcr" },
  "registrationUrl": "https://mcp.dabarli.app/oauth/register",
  "baseScopes": ["workforce"],
  "resource": "https://mcp.dabarli.app"
}

Portal Connect

  • Error: OAuth client ID is required when using pre-defined OAuth client credentials.
  • Happens for dcr (and previously for provided / cimd on the same draft).
  • DevTools Network: no failing save/update request when Connect is clicked — looks client-side validation.
  • Re-uploading the ZIP / flipping mcp.json on the same draft does not clear the stuck auth state.
  • MCP configuration remains incomplete; submission blocked only by Connect/scan.

OAuth works outside the portal
Same MCP URL + OAuth works in ChatGPT (custom/dev plugin → Connect → login as review account ``youssef.demo (Dabarli review seeker)). Account connects; authenticated tools run (e.g. search waiter jobs in Tunis returned live Café Medina listing; account verified as Youssef Mejri).

So the authorization server and ChatGPT OAuth path are fine. The submission blocker is the plugins portal Connect form treating DCR as if a predefined client ID were required, without making a network save call.

@OpenAI_Support — can someone inspect this draft’s saved MCP auth vs the Connect form? Happy to try a fresh draft if that’s still the only unblock, but we’d rather not churn metadata that already passes checks.

We are also having client-side connect failure in both mode: "cimd" and mode: "dcr" (no predefined client ID expected)

Plugin

  • Plugin ID: plugin_asdk_app_6ad88a72f954819188b2cc35668dd351
  • App ID: asdk_app_6ad88a72f954819188b2cc35668dd351
  • Org: Pick n Pay Omnichannel
  • Version: 0.1.2 (draft, not submitted)
  • MCP server url: https://b783eff7-cb05-4eca-8a2e-e6bc87bb985f.sabr-mcp.cnstrc.com/openai/mcp
  • Domain verification: succeeded

Our OAuth supports both CIMD and DCR, we prefer to use DCR but both are failing for us.

Similar to above comment we are getting the same error: OAuth client ID is required when using pre-defined OAuth client credentials. No failing save/update request when Connect is clicked, same as above in previous comment so looks like client side validation. Our submission remains blocked only by connect/scan.

As above, the same MCP url & OAuth works fine in chatgpt for testing (building custom plugin in dev mode), connect works perfectly with OAuth without needing sign in, as designed. Issue seems specific to the platform submission area.

One other issue that we run into is on the checks section, since we don’t require login to access the mcp server is this screen:

Since we don’t require login or pw to access the mcp server, I’m not sure what exactly to do here, since it wont pass this scan without providing something. It is also not clear if the request is to access the server vs. access the chatgpt organisation account, could you clarify this?

@OpenAI_Support Could you look into this plugin specifically and see if this is a bug and whether workarounds exist, we are eager to submit our plugin and have invested quite some time in our efforts here and it would be a shame to fall at the last hurdle here.

Thanks in Advance

{
  "type": "streamable-http",
  "url": "https://api.runplutus.com/v3/mcp",
  "headers": {},
  "extensions": {
    "com.openai": {
      "auth": {
        "type": "oauth",
        "client": {
          "mode": "provided",
          "clientId": "https://chatgpt.com/oauth/client.json",
          "tokenEndpointAuthMethod": "none"
        },
        "baseScopes": [
          "investor:read"
        ],
        "defaultScopes": [
          "investor:read",
          "offline_access"
        ]
      }
    }
  }
}

I have tried cimd mode, supplied a generated client id, and also used the client id url link shown here. All results in the error:

MCP details save failed: OAuth client ID is rerquired when using pre-defined OAuth client credentials

I have confirmed in my backend that we receive request logs for when chatgpt and claude connect to my MCP endpoint. But when i click connect in the plugin creation portal there is no request sent to my backend. There is no request sent to the OpenAI backend either, the error seems to be a frontend validation error.

@OpenAI_Support Can I get some help to unblock this step? Since I am not able to publish my plugin to chatgpt. This points to portal-side validation failing before OAuth starts, despite clientId being visible in the imported settings.

My plugin is called Plutus and link is here:

@sean.ocarroll, that field asks for a test login to your own service when sign-in is required. It’s separate from your ChatGPT account and OAuth client secret.

@altFINS @firasguendouzz @jz1, I checked the current records for your submissions and Pick n Pay. All four completed connection and tool scanning and reached review. Plutus used its original draft; the other three used newer submissions.