submitmcp

Guides · Checked November 8, 2026

How to get your MCP server into ChatGPT

ChatGPT's app directory is now a plugin directory, shared by ChatGPT and Codex. You upload a plugin ZIP that points at your remote MCP server, pass automated scans, and wait for a person to run your test cases. Plan on two weeks if everything works the first time, and on more than a month if it doesn't.

What changed in 2026

OpenAI opened submissions for apps in ChatGPT on December 17, 2025 (OpenAI). On July 9, 2026 the App Directory became the Plugin Directory, shared with Codex, and existing apps moved over on their own (OpenAI). At DevDay on September 29, 2026, the old web form was replaced by a ZIP upload (TechCrunch).

So guides written before October 2026 describe a form that no longer exists. Screenshot rules went too: OpenAI's docs required 706-pixel-wide screenshots until late October 2026 and no longer mention them.

Before you start

  • A verified identity. Verify yourself as an individual, or your company as a business, in the organization settings of the OpenAI Platform. The directory shows the verified name, whatever your ZIP says, and a plugin published under an unverified name is rejected (OpenAI).
  • The right role. Organization owners can submit. Other members need the Apps Management Write role (OpenAI).
  • A project with global data residency. Projects with EU data residency can't submit plugins with an MCP server.
  • A remote server. Streamable HTTP at a stable public HTTPS address, usually ending in /mcp. Tunnels and local addresses don't count. Local (stdio) servers are only accepted from partners OpenAI has allowlisted (OpenAI).
  • Four public pages: a website, a support page, a privacy policy and terms of service.
  • Sign-in that ChatGPT supports. No sign-in, OAuth, or OAuth for only some tools. There's no way to ask users for an API key. For OAuth, ChatGPT needs PKCE with S256 and protected-resource metadata, and prefers a Client ID Metadata Document over dynamic client registration (OpenAI).

What you need to prepare

The listing. These limits are checked when you submit, not when you upload, so a ZIP can upload fine and still fail at the end (OpenAI):

Field Limit
Name 30 characters
Short description 30 characters
Long description 4,000 characters
Category One of 13, such as Productivity or Developer Tools
Capabilities Up to 20, 120 characters each
Starter prompts Up to 3, 128 characters each
Icon Square, 48 to 4,096 pixels, up to 5 MB

Review materials.

  • Exactly 5 positive test cases. Each has a prompt, the tools it should call and the result you expect. Run every one on the test account just before you submit.
  • Exactly 3 negative test cases. Prompts your plugin should refuse, or answer by asking a question or falling back safely.
  • A demo video that shows the test cases. Alpic, which has sent dozens of submissions, found reviewers expect it to cover desktop, iOS and Android (Alpic).
  • Release notes.
  • Reviewer credentials for a test account with sample data. They go in the dashboard, never in the ZIP.

Tool annotations. Every tool needs readOnlyHint, destructiveHint and openWorldHint set to true or false explicitly (OpenAI). OpenAI reads them from your live server, so to fix one you redeploy and rescan. OpenAI's definitions are stricter than most people expect:

  • readOnlyHint is false for anything that changes state, including queuing a job or sending a message.
  • destructiveHint is true for deleting, overwriting, cancelling, revoking access or sending something that can't be unsent. Being able to undo it doesn't make it non-destructive.
  • openWorldHint is true for anything that reaches the public internet, even a read-only web search. It's false only for tools confined to the user's own account or workspace. One team was rejected for setting it to false on tools that had indirect effects outside the account (3Min API).

The guidelines say you no longer have to justify each hint, but OpenAI's error codes still include a missing justification, and rejection emails in November 2026 still asked for them (OpenAI forum). Write one line per hint anyway.

If your server shows UI, declare every domain it loads from in its content security policy, with no wildcards. Reviewers compare the policy with what the UI does, and each iframe domain needs a written reason (OpenAI). Test it in dark mode and at phone width.

Submitting, step by step

  1. Package the ZIP. Put a plugin.json and an mcp.json (with "type": "streamable-http") at the root, or use the Codex layout with .codex-plugin/plugin.json. Test cases, the demo video URL and release notes can go in plugin.json. Never put credentials, reviewer instructions or a client secret in the ZIP: the upload rejects them (OpenAI). OpenAI's Plugin Creator can scaffold the package, but it adds a .app.json file that you have to delete before uploading (OpenApps).
  2. Add a small skill. The docs contradict each other on whether a plugin with only an MCP server also needs a skill. OpenAI's own example includes a short getting-started skill, so do the same.
  3. Upload it under Plugins in the OpenAI Platform, choosing your verified identity, and fix whatever the automated checks flag. Each fix means uploading a corrected ZIP, and skill scans can take up to two hours.
  4. Connect your server. Under MCPs, select Connect and prove you own the domain: serve the token OpenAI gives you, as plain text, at https://your-domain/.well-known/openai-apps-challenge. Sign in if your server needs it, and let the tool scan finish. A plugin can have only one MCP server, and the server's domain can never change after you publish.
  5. Enter the reviewer credentials under Review details, then submit and accept the policy attestations.
  6. Publish. Approval doesn't make you live. Open the approved version and select Publish plugin.

Only one review can run per plugin. To change something mid-review, cancel the review and submit again.

How long review takes

OpenAI publishes no timeline and won't speed up a review (OpenAI forum). What developers report:

  • About two weeks when it goes well. 2,758 plugins that went live in late October 2026 took a median of 15 days from creation to going live (OpenApps). One team logged every status change of a 16-day review (ScoreStarling).
  • One to two weeks per round when it doesn't. Rejection emails have often been vague about which tool is the problem, and some teams went through four rounds (OpenAI forum).
  • Sometimes months. Developers on OpenAI's forum say "30 days or more is not uncommon", and some reported 60 to 120 days in spring 2026 (OpenAI forum). One developer spent two weeks building and three months in review (Hacker News).

If a rejection shows in the dashboard without an email, or you need details, reply to the rejection or contact [email protected] with the case ID.

Why plugins get rejected

OpenAI names four common reasons (OpenAI):

  1. The reviewer can't connect. Two-factor codes, expired credentials, or a login that only works inside your network.
  2. Test cases fail. Results don't match what you wrote, the UI breaks, or the output contains extra or identifying information. They have to pass on every surface you support.
  3. Your tools return data your privacy policy doesn't mention, including nested fields, debug output, internal IDs or telemetry.
  4. Annotations don't match what the tools do.

Developers add these:

  • Test cases that depend on each other. A reviewer runs them in any order on a fresh account. One team was rejected after nine days when a case relied on data an earlier case created, which also exposed three server bugs (Xenition).
  • A developer name that doesn't match the verified identity (OpenAI forum).
  • Descriptions that read as manipulation: "ALWAYS call this first", "MUST CALL", second-person phrasing like "your data", or instructions inside tool results (r/LLMDevs).
  • Gaps in the privacy policy. The same team had to add a gender field and data it derived to its policy, and name OpenAI as a recipient.
  • Marketing in the listing or the results: taglines, brand claims you can't back up, or promotional lines in tool output (OpenAI forum).
  • Generic or trademarked names (Alpic).

Rules that can rule you out

From OpenAI's plugin guidelines:

  • No selling digital goods: no subscriptions, credits, tokens or upsells inside ChatGPT. Users can sign in to an account they already pay for, and you can link to a pricing page, but not to checkout. Physical goods are allowed, paid for on your own site.
  • No prices, trials or promotions in the listing, and no comparisons with other products.
  • No "MCP", "MCP Server" or "Plugin" at the end of the name, and no generic dictionary-word names.
  • Suitable for ages 13 to 17. Adult content isn't supported yet.
  • No collecting payment card data, health data, government IDs or passwords, no asking for the conversation history, and no precise location.
  • No unofficial connectors to someone else's service, and no general-purpose tools that run operations the reviewer never saw.
  • No ads, and nothing that nudges the model toward your plugin or away from others.

After you're live

  • Tool changes go live without a new review. OpenAI scans your server daily, and you can rescan whenever you like. New tools stay hidden until they pass the automated checks, and changed tools keep their old version until the new one passes (OpenAI).
  • Listing and skill changes need a new ZIP, a new review and a new publish. The current version stays live meanwhile.
  • You can't ask to be featured. The directory's main pages show only plugins OpenAI picks for "strong real-world utility and high user satisfaction". Everyone else is found by exact name or a direct link. A few selected developers also get an OpenAI Verified badge (OpenAI).
  • Plan a launch with OpenAI by emailing [email protected] before you announce it.

Tools that help

  • OpenAI's chatgpt-app-submission skill drafts the 5 positive and 3 negative test cases and the hint justifications, and checks your content security policy and naming. It was written for the old form, so check its output against the ZIP format.
  • MCPJam Inspector emulates ChatGPT's widget host, dark mode and devices, and runs your test cases before a reviewer does.
  • Alpic Beacon renders your app in the real ChatGPT and tells you whether it's ready. Servers without sign-in only.
  • Dawloom's preflight script checks annotations, content security policy, inputs OpenAI forbids, ID-like fields in results, and the domain challenge.

More checkers, and companies that will submit for you, are in the overview.