How long ChatGPT and Claude app review takes in 2026
ChatGPT plugin and Claude connector review times in 2026 from real submissions, why you hear nothing while you wait, and the common rejections.
In late 2026, ChatGPT plugin reviews took about two to four weeks to approval, and Claude connector reviews have run from a few days to more than two months. WarrantyWarden's ChatGPT plugin was submitted by 13 October 2026 and approved on 29 October. Neither OpenAI nor Anthropic publishes a review time or sends progress updates while a submission is in review. Check the status page yourself, keep your server and reviewer test account working, and don't ask support to speed it up.
Is three weeks with no news normal?
Yes. In November 2026, many developers waited three weeks or more on both stores without hearing anything.
- WarrantyWarden, a warranty-tracking app, in ChatGPT. OpenAI's portal flagged three things on the first upload, by 7 October 2026. The fixed plugin was submitted by 13 October and approved on 29 October. The approval email said: "Your plugin, WarrantyWarden, has been approved and is ready to publish." The case study has the full story.
- Transica's own connector in Claude. It was submitted by 24 October 2026. On 12 November it still showed In review.
- Reddit. In an r/mcp thread, a developer who had submitted to both stores was still waiting after three weeks. Approval came after just over four. In another r/mcp thread, a developer listed in both directories said Anthropic took about 3 to 5 days and ChatGPT about 3 weeks. Someone else in that thread had waited a month for Anthropic, while their ChatGPT plugin had been live for a week.
- OpenAI's forum. One developer waited 27 days, then got a rejection because reviewers couldn't sign in, although the login worked. Another was In review from 6 October and saw a "Review on hold" banner with no reason. OpenAI Support replied that it has a high volume of reviews and can't give a completion date.
- GitHub. In one issue, developers have listed 11 Claude connectors stuck In review, two of them first submitted in July 2026. Those who emailed Anthropic got only automatic replies. On 20 November, one team was still waiting on a submission from 18 September.
How long does each step take?
ChatGPT
| Step | What happens | How long |
|---|---|---|
| Upload | You upload the plugin ZIP. Automated checks and an MCP scan run, and you fix what they find | Until the findings are fixed |
| Submit | You add the reviewer account, test cases and video, then submit | Your pace |
| Review | OpenAI tests the plugin. The state shows under Review status on the Plugins page | Median 13 days to approval; WarrantyWarden took just over two weeks |
| Feedback | A rejection email names the failed checks and gives a case ID | Median 3 days to rejection |
| Resubmit | You fix the issues and submit a corrected ZIP for a new review | No published time |
| Publish | After approval, you click Publish plugin when you're ready | Your choice |
The medians come from reviewtimes.fyi, a site that collects review times from developers. On 20 November 2026 it had 55 ChatGPT reports. It put the typical wait at 27 days, counting submissions still waiting.
Claude
| Step | What happens | How long |
|---|---|---|
| Submit | You work through the portal's steps at claude.ai/directory/manage. Your tools sync from the server | Your pace |
| Scan | Anthropic scans the connector automatically. By default it's listed as Community | No published time |
| In review | Some submissions also get a review from a person | 3 to 5 days in one report; over two months in others |
| Feedback | The status changes to Changes requested or Not approved. The note is under View feedback in the portal | No published time |
| Resubmit | You edit the listing and submit again | No published time |
| Publish | After Approved, someone who can edit the listing clicks Publish | Your choice |
Anthropic's docs say review time isn't fixed and varies with queue volume. On 20 November 2026, reviewtimes.fyi showed more than 50 days for Claude connectors, from 17 reports. After approval, editing the listing before you publish sends it back to draft for another review.
Does OpenAI or Anthropic email you during review?
Not with progress updates.
- OpenAI. Its review page says you get an email when the status changes, and another when the plugin is approved. Rejections come by email too. Some developers say they never got the status emails. OpenAI Support says review messages come from trustandsafety@openai.com or no-reply@openai.com, so search your inbox and spam for both.
- Anthropic. The portal shows one status for each submission. While a connector is In review, Anthropic emails your primary contact if it needs something, such as test access. Reviewer notes appear in the portal.
One developer on Reddit waited about three weeks for an email, then found the submission already approved on the submission site. Check the status page every few days.
Why do apps get rejected?
From OpenAI's app review page and plugin guidelines, and Anthropic's pre-submission checklist and directory policy:
| Reason | Store | Fix |
|---|---|---|
| Reviewers can't connect or sign in | Both | Give a reviewer account that works at once. For ChatGPT, that means no MFA, email or SMS codes, or magic links. Test it from outside your own network, and check it hasn't expired |
| Test cases give the wrong result | ChatGPT | Rerun all eight cases with the reviewer account. Make each expected result clear. Leave out extra or personal data |
| Tools return personal data the privacy policy doesn't mention | ChatGPT | Remove fields the tool doesn't need. List the rest in your privacy policy |
| Tool annotations don't match what the tool does | Both | ChatGPT wants readOnlyHint, destructiveHint and openWorldHint set to true or false on every tool. Claude wants a title plus readOnlyHint or destructiveHint |
| Pricing, promotions or claims no tool backs up in the listing | ChatGPT | Describe only what your tools do |
| A trial or demo build | ChatGPT | Submit a complete, stable plugin |
One catch-all tool, such as api_request with a method input | Claude | Split reads and writes into separate tools |
| Descriptions that tell Claude how to behave or promote products | Claude | Say what the tool does and when to use it |
| Generic errors or oversized responses | Claude | Return errors that say what went wrong. Return only what the task needs |
| A server that calls someone else's API | Claude | Call your own API, or one you have permission to proxy |
In the first r/mcp thread, a developer's first OpenAI review was rejected in one sentence: the privacy policy described an older version of the server. In the second, a developer said OpenAI asked them to mark tools that change or delete data as destructive. OpenAI's guidelines add that being able to undo a change isn't enough reason to set destructiveHint to false.
What should I check before I submit?
- Privacy policy. Publish it, and make it match what your tools return today. OpenAI wants the categories of personal data, why you use them, who receives them, how long you keep them and what control people have.
- Reviewer test account. Use a separate account with sample data, not a real customer's. For ChatGPT, it must work without MFA. In an r/microsaas thread, the developer of an app for GitHub Projects had to create a fresh GitHub account with no MFA just for reviewers. ChatGPT takes the login in the review form. Claude takes no credentials in the portal: a reviewer emails you if they need test access.
- Demo video. ChatGPT wants a walkthrough of your test cases at a link reviewers can open. Claude takes no video. For an MCP App, it takes 3 to 5 PNG screenshots.
- Test prompts. ChatGPT needs exactly five prompts that should use a tool and three that shouldn't. Run all eight with the test account first. Claude asks you to confirm you've run every tool, and its policy asks for at least three working example prompts.
- Tool annotations. Set them on every tool, as in the table above. Claude also limits tool names to 64 characters.
- Sign-in. Use OAuth for tools that act on someone's account, or no sign-in for public data. ChatGPT's portal doesn't support API keys. See MCP server authentication.
- Reachability. Make sure your firewall or CDN doesn't block the stores' requests. Anthropic's docs ask for OAuth responses in under ten seconds.
- OpenAI project. Projects with EU data residency can't submit plugins with MCP servers for now.
What should I do while I wait?
- Check the status page. That's Review status on OpenAI's Plugins page, or the card on your connector's page in Claude's portal.
- Keep everything running. You don't know when a reviewer will test. A server that's down or a test account that has expired can turn into a rejection.
- Leave the submission alone unless a reviewer asks for changes. OpenAI allows one review per plugin at a time, so changing a submission means selecting Cancel Review and submitting again. On Claude, withdrawing hasn't helped: in the GitHub issue, a connector In review since July was withdrawn and resubmitted on 5 November, and the new submission went straight back to In review.
- Contact support only for a real problem. OpenAI asks developers not to contact support to speed up a review. When you do contact OpenAI support, include the plugin ID from the portal. To appeal a rejection, reply to the rejection email with your case ID. For a Claude connector, email mcp-review@anthropic.com with the listing name, the organization you submitted from and the status the portal shows.
How Transica helps
Transica checks your server against both directories' published rules before you submit. It runs the test prompts signed in as the reviewer account, builds the ChatGPT package and gives you every field Claude's portal asks for. Its health checks alert you within 15 minutes when a hosted server fails. You submit, and OpenAI or Anthropic decides.
- Free directory check. Paste your server's address into the MCP directory check, no account needed.
- Done for you. On the done-for-you listing, from $1,500, Transica builds the app, records the demo, prepares both submissions and stays with you through review.
Step-by-step guides: ChatGPT app directory and Claude connectors directory.
Common questions
How long does ChatGPT app review take in 2026?
OpenAI doesn't publish a time. Reported approvals in late 2026 took about two to four weeks. WarrantyWarden was submitted by 13 October 2026 and approved on 29 October.
How long does Claude connector review take?
Anthropic says review time isn't fixed. Reports range from 3 to 5 days to more than two months, and some submissions from September 2026 were still In review on 20 November.
Does OpenAI send updates during review?
No progress updates. OpenAI says it emails when the status changes and when a plugin is approved. Check Review status on the Plugins page too.
Can I ask OpenAI or Anthropic to speed up review?
No. OpenAI says requests for expedited review can't be accommodated. Anthropic's docs describe no way to speed it up.
Why was my ChatGPT app rejected?
The most common reasons OpenAI lists are reviewers who can't connect or sign in, failed test cases, personal data your privacy policy doesn't mention and tool annotations that don't match what tools do. The rejection email names the failed checks.
What happens after approval?
Nothing goes live until you publish. In ChatGPT you click Publish plugin. In Claude, someone who can edit the listing clicks Publish.
Sources
Read on 20 November 2026.
- OpenAI: Upload and submit your plugin, App review, Plugin guidelines
- Anthropic: Submit a connector, Pre-submission checklist, Track your directory submission, Publish to the directory, Test your connector, Software Directory Policy
- OpenAI developer forum: 27 days, then rejected for a login that works, Review on hold for 3+ weeks, Two plugins stuck in Changes required
- GitHub: Connector submission In review since 2 October
- Reddit: r/mcp, getting an MCP plugin approved, r/mcp, listed in both directories, r/microsaas, first users and directory review
- reviewtimes.fyi, crowdsourced review times
- WarrantyWarden in ChatGPT's plugin directory