Developer guide · pending review / remote-MCP replacement choice 11 October · OAuth client location clarified 10 October · supporting OAuth checks 9 October · public-ZIP channel gate inspected 6 October · annotation conflict 4 October · other readiness 1 October 2026
Submit and review a public plugin
Prepare evidence for a first public release without confusing ZIP upload, final validation, review, approval and the developer’s Publish action.
Provided OAuth client: configure the ID in the package, not an advanced editor
Portable public remote-MCP flow · documentary clarification/correction 10 October 2026 · portal/connect/use untested.
The documented location is now established. This corrects our 9 October location-unknown claim, not the original unverified problem report or a proven UI/documentation change. Its actual upload format/account/control/cause/fix remain UNKNOWN. The decision order and stop advice are our synthesis, not a tested fix or universal procedure.
- Confirm the provider registration and use its server namespace. In root
mcp.json, the named server’smcpServers.<server>.extensions["com.openai"].auth.clientholdsmode: "provided"and case-sensitiveclientId—notplugin.jsonmetadata, a guessed top-level key or local Codex/TOML. The reference makesclientoptional,moderequired when present andclientIdrequired forprovided.tokenEndpointAuthMethodis optional there; Submission instructs declaring the chosen method. Match the actual provider contract:client_secret_basic,client_secret_postor legitimate public-clientnone. Omitted-method behavior is unestablished; do not switch to DCR/CIMD to evade a field. Packaging · Registered client / OAuth reference, Submission · Configure authentication. - Keep a required secret in connection setup. Documented route: MCPs → select server → Connect → OAuth Client Secret. The field appears for a provided client unless
tokenEndpointAuthMethodis"none".clientSecretis rejected inmcp.json; keep secrets outside the ZIP, chat, logs and report. This authenticates the application—not a user password, access token or reviewer login. Endpoint overrides are needed only when discovery lacks them; match real scopes/callback. Aprivate_key_jwtdeclaration supplies no signing-key setup; seek platform clarification before choosing it for submission. Submission · Configure authentication / Limitations. - Compare source/upload with the saved connection. Advanced settings are read from
mcp.jsonand displayed, not edited in the panel. Documented update: edit source → Upload new version → inspect saved MCPs settings before connecting. Existing registration can lock credential changes; upload does not prove replacement. Contradictory/locked saved settings → stop for authorized provider/platform clarification with redacted plugin/draft/stage/mode/error evidence, not resets or repeated uploads. Keep the exact callback and separate user/reviewer checks retained below from 9 October. Actual saved state/lock remains unknown. Submission · Configure authentication, Authentication · Redirect / Client registration. - Retry only the applicable gate after agreement. Direct remote-MCP declarations differ from excluded registered
apps/.app.jsonmappings. Configuration is not package eligibility, connection, scan, useful work or review. API-key declarations cannot complete portal setup; there is no bearer-input or nonempty-server-header bypass. Never downgrade protected access. No operation ran. Submission · Limitations / Public ZIP scope.
Genuine alternative: when protected customer data/actions are unnecessary, an ordinary prompt/skill or existing legitimate website/integration may suffice. Untested alternatives—not drop-ins or authentication/review bypasses.
Registration contracts and provider prerequisites · retained 9 October checks
Client ID Metadata Document (CIMD) uses an HTTPS document URL as identity; Dynamic Client Registration (DCR) obtains and reuses a generated client. Check real resource/provider discovery, accepted token-endpoint authentication methods and S256 support for Proof Key for Code Exchange (PKCE). CIMD needs advertised support and document fetching; DCR needs a registration endpoint and login-enabled client. Predefined credentials do not mean the unsupported machine-to-machine client_credentials grant.
Authentication · OAuth metadata / Client registration / Client identification, Troubleshooting · Authentication problems. Documentary checks 9 October; no provider operation.
Exact callback and real issuer behavior · retained 9 October checks
Use this connection’s production redirect shown on its MCP management page and the authorized provider allowlist—not a sample or wildcard. Missing management output stays UNKNOWN; never bypass validation or transfer a ChatGPT callback to another host.
Stable eligibility requires advertised issuer identification. The authorization-server metadata issuer must match that server’s entry in the MCP protected-resource metadata authorization_servers list; every successful/error authorization response iss must match that issuer—not the MCP resource URL. A flag alone is insufficient.
Authentication · Protect callbacks with issuer identification / Redirect URL. Documentary checks 9 October; actual callback/behavior unknown.
Retained DCR, user/reviewer access and the next gate · retained 9 October checks
For an existing DCR connection returning invalid_client, check/restore the retained client and any secret rather than create another. An expired access token is different. This conditional advice is not the reported blocker’s diagnosis. Reviewer test-account credentials belong separately in Review details, not the ZIP or in place of OAuth registration. Separately establish user consent/resource access and useful workflow results.
After legitimate correction, use documented Reconnect for connection attention or applicable Rescan for server/tool findings; inspect results before submission. Custom-development Refresh is different. Connection, scan, review, approval and chosen Publish are not equivalent.
Our owner fork: evidenced provider/client/method/redirect mismatch → authorized provider maintainer; unresolved platform control/saved-state conflict → support clarification. Submission asks for the plugin ID; the broader redacted packet is our advice. No contact occurred.
Troubleshooting · Authentication problems / Escalation, Submission · Review information / Connect and scan / Support, Connect and test · Refresh / Evaluation. Documentary checks 9 October; all operations untested.
10 October source scope and remaining unknowns · Unchanged 9 October historical report. No configuration sample, credential, observed account control or tested fix supplied.
Choose the channel before preparing review materials
6 October check: not as-is. Current public-submission guidance excludes ZIPs containing lifecycle hooks or registered MCP server mappings (apps / .app.json). A locally supported or optional helper does not make that same bundle eligible.
Submission · Automatically provide submission and review information. Newly inspected restriction, not a changed rule or observed upload rejection.
Registered mappings are not optional MCP UI. Adjacent guidance uses direct MCP URLs and dashboard setup; any service needs legitimate server/control/provider authority and applicable verification, authentication and scans. Local package support is a different scope—not a blanket UI, script or local-plugin ban.
Packaging · Path rules / Publish official public plugins, Submission · Complete metadata examples / Connect and scan your MCP server, Errors · MCP server reference errors. Narrow channel check, 6 Oct.
What the sources do not resolve
The conversion guide directs hook adaptation in both submission-path support tables, followed by preparation/submission steps. This conflicts in implication with the explicit ZIP exclusion; no exception, source precedence or controlling real path is established. It is not “local-only” guidance. Withhold a hook-bearing public eligibility claim pending authoritative clarification.
Errors' skills-only exclusions and reference-removal/import warnings are scoped, not a hook workaround. No universal optional/disabled/untrusted, unselected/undeclared or empty-scaffold exemption is established. Local default discovery makes deleting a manifest key no reliable general remedy. Actual public parsing, normalization and enforcement were not observed.
Conversion · Review what OpenAI supports / Prepare and upload / Prepare and submit, Errors · ZIP upload / MCP references / Package warnings, Packaging · Bundled MCP servers and lifecycle hooks. Dated comparison and exact scope.
Upload and submit. Checked 1 Oct 2026.
- Complete ZIP
- Automated upload checks
- Final submission
- Review
- Approval
- Choose Publish
An upload pass is not final submission acceptance. Approval is not an automatic Publish action, an estimated review time or a distribution guarantee.
Upload and submit, MCP review and distribution, Submission error reference. Checked 1 Oct 2026.
A review is pending and the next fix is ready
Public-plugin package choice · documentary checks 11 October 2026 · operations untested.
Do not plan a second simultaneous review of the same plugin. Local preparation does not replace the submitted package. Our conditional default: leave a still-truthful/useful submission in review while preparing locally. This is our synthesis—not an official instruction to keep materially wrong materials pending. Submission · Submit the draft.
- Identify the actual package and change. An authorized maintainer compares the selected package in Metadata & Skills, Review status and review email with the intended fix. These are documented handles, not observations here. Our optional note records plugin ID, selected version/status, changed scope and why replacement is needed; redact secrets/private customer data. Separate local source, submitted package and running service: prepared is not uploaded or approved. Submission · Submit / Update.
- Choose deliberate replacement, not upload/cancel loops. Wait for the decision or cancel the active review before replacement upload; a rejected package takes a corrected ZIP addressing feedback. Keep scope-sensitive wording: remote-MCP guidance describes Cancel Review and same-version-draft resubmission; new package/version updates need a complete updated-version ZIP with retained components and applicable checks/review. No universal transaction is established. Each resubmission starts a new review—no queue-position retention, deadline, priority, expedition or approval promise. Our genuine already-working website/manual service/ordinary-answer alternative, when useful, is untested here—not a duplicate listing or access/review bypass. Submission · Submit / Update, MCP review · New versions.
- Already published? Keep it during replacement review. Remote-MCP maintenance guidance instructs publishing the approved replacement directly; do not unpublish the current version first merely to update. Removing it without a published replacement makes the plugin unavailable. Removal/deletion is not Cancel Review. This narrows our broad documentary retention uncertainty for that supported path only—not every rejected review, security removal, directory state, recipient or loaded session. Actual continuity remains unobserved. MCP review · Replacement / Maintenance.
- Use the applicable change or appeal path. After initial publication, hosted-tool checks are separate: new tools await approval, held changes retain approved definitions, and calls reach live implementation. Keep it compatible; scans cannot publish a pending initial package. Held-tool Appeal / Withdraw appeal differs from rejected-package email appeal; automatic MCP updates pause during a tool appeal. Support may clarify an unresolved boundary with the plugin ID, not expedite review. Our broader note/default/order are optional synthesis, not an official form or tested fix. Submission · MCP updates / Appeals, MCP review · Help / FAQ.
Actual account/control/status/cancellation transaction/queue/result/recipient/loaded continuity: UNKNOWN. Upload/cancel/contact/scan/deploy/use: untested. No rule-change date established.
Evidence scope and access limits · not an account walkthrough
Two undated canonical primary pages independently inspected 11 October, in the 21:02:27–21:03:02 UTC source-inspection bracket—not exact HTTP/publication/change times. One-active-review and replacement instructions are newly inspected; package versus post-publication tool boundaries reconfirmed; draft/new-ZIP wording scope-sensitive. No cancellation control, completed transaction, queue position, review result or actual listing was observed. Provider authentication, portal actions, appeals, installation and retesting were not performed. Dated source headings and limits.
Check the submitter and release identity
- Platform eligibility. Use the appropriate organization/project, Apps Management Write role and verified identity; package files do not supply these.
- Truthful public listing. Prepare publisher/interface metadata, required disclosures, current listing text bounds and a primary square icon. A relaxed skills-only metadata URL-import check is not permission to omit the privacy policy or other applicable disclosures.
- One complete package root. Valid UTF-8/JSON/skill files, referenced assets and the final semantic version. Local portable schema requirements and final listing requirements differ.
- Distinctive production utility. Demonstrate a real purpose and quality beyond a trial or teaching demo. Do not invent test output, approval, third-party authorization or enhanced placement.
Upload and submit, Submission error reference, Plugin guidelines. Checked 1 Oct 2026.
Skills-only and MCP require different evidence
- Skills-only release
- Skill checks/safety scans and broader listing/policy eligibility still apply. MCP reviewer credentials, tool demo video and five-positive/three-negative MCP cases are not required merely because the package includes a skill. Our ten host specifications are original QA, not mandatory portal cases.
- Public MCP release
- Prepare a stable production publicly accessible HTTPS endpoint, domain verification, suitable auth, accurate tool schemas and annotations. Provide a dedicated reviewer sample account, an accessible demo and exactly five positive/three negative MCP cases.
- UI-bearing review material
- Directory screenshots no longer being displayed does not eliminate all UI review-material rules. Guidelines and submission-error references concern different contexts; verify the actual portal requirements.
Upload and submit, MCP review and distribution, Submission error reference, Plugin guidelines. Checked 1 Oct 2026.
Meeting Evidence: the honest gap list
The unchanged source is a portable authoring example, not a completed public product. The new release-rehearsal kit establishes only finite offline observations: 33 TOOLING assertions passed, not host or safety results.
- Portable manifest syntax
- The schema requires
$schemaandname. Our four-field identity/version/description profile is stricter in selected ways and not complete JSON Schema validation. - Codex package compatibility
- Current guidance requires
logoandcomposerIcon. This two-file source has neither; host compatibility is untested. Adding metadata/assets needs a broader profile and recorded host acceptance. - Portable upload versus public submission
- Portable upload may omit those icon fields, but primary icon, truthful listing/identity/disclosures, final name/version rules and current final validation still apply before submission. Upload success is not final acceptance.
- Behavior, safety and production utility
- All ten host cases are untested. No secret/safety scan, public validation, review or approval ran for this sample. Distinctive production utility is unproven; a teaching demo does not establish policy eligibility.
- Approval versus publication
- Applicable review and approval must precede a separate chosen Publish. No sample submission or plugin publication was performed.
Portable schema, Host metadata and submission, Final validation errors, Production utility and privacy policy. Checked 1 Oct 2026.
Readiness worksheet
Release identity / semantic version / package root:
Submitter organization, project, write role, verified identity:
Distinct user task and demonstrated production utility:
Listing/publisher metadata, square icon, disclosures:
Codex logo/composerIcon compatibility; primary submission icon:
Bundled assets and complete package checks:
Actual local behavior records and unresolved failures:
Skill scan findings (when available):
MCP endpoint/domain/auth/reviewer account (if applicable):
MCP five positive + three negative cases and demo (if applicable):
Live portal conflicts still requiring clarification:
Review outcome and separate Publish decision: NOT PERFORMEDThis is our preparation template, not a portal schema or evidence that any row has passed.
Advertise the full behavior; do not guess required explanation fields
Narrow check · 4 October 2026. Explicit readOnlyHint, destructiveHint and openWorldHint values must describe all supported modes/defaults and indirect effects—not a favorable dry run or tool name. The flags are independent; explanations cannot override scanned values. A saved draft, job or outbound send cannot hide behind “read-only preview.” Inspect the conditional three-operation example.
Guidelines · MCP requirements → Tools → Correct annotation, MCP review · Metadata stored during tool scanning / annotation mismatch. Only consequential behavior/annotation sections refreshed; no scan performed.
Correct annotation, Final directory submission / annotations_required / justification_required, Review FAQs · annotation mismatch. Paired annotation-only conflict checked 4 Oct. No changed rule established; other readiness material retains 1 Oct.
After approval, choosing Publish remains a separate action. Exact-name/direct-link discovery is not discretionary enhanced placement; no review SLA or approval promise was established.
MCP review and distribution. Checked 1 Oct 2026.
Next: choose distribution and maintain the release → · Revisit the trust boundary
Maintaining a public release? Separate the complete versioned-bundle/Publish record from live scans and deployments (bundle/recorder scope retains 2 October). 11 October remote-MCP clarification: keep the current published version during replacement review and publish the approved replacement directly; do not remove-first merely to update. Actual/universal recipient or loaded continuity remains UNKNOWN. MCP review · Changing published metadata versions. Pending-package decision above.