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
- Upload a plugin ZIP containing the following
mcp.json. - Open MCPs → Tapify → Connect.
- Confirm the imported settings show
mode: provided, the client ID, andclient_secret_basic. - The OAuth Client Secret input briefly appears during loading, then disappears.
- 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.

