ManyCP is not affiliated with, endorsed by or sponsored by any directory, Docker, OpenAI, Anthropic or GitHub named here. Names are used to say which service a fact is about.
ChatGPT and Claude each have a directory for MCP servers, with its own form and its own review. OpenAI's takes remote servers. Anthropic's takes remote servers as connectors, and puts a local server inside a plugin[4]. Both ask for tools that declare what they do and a test account for the reviewer. Both are yours to send: you sign in and you press Submit, and ManyCP does not do either for you. OpenAI's docs now call what you submit a plugin[3].
Side by side
Catalog rows checked 29 Sept 2026. Review statements read from each company's docs on 1 Oct 2026.
You. It needs your verified identity and your own OpenAI organization.
You. The listing belongs to your own Claude organization and you accept Anthropic's terms.
Review time
No set time. OpenAI says review timelines may vary and that support cannot speed one up[2]. Its submission guide gives no figure[1].
No set time. An automatic scan runs first. Some submissions also get a person's review, and those times vary with queue volume[4]. For escalations, Anthropic gives mcp-review@anthropic.com[4].
Both reviews read each tool's annotations. Anthropic wants a title and a readOnlyHint or destructiveHint on every tool[4]. OpenAI wants readOnlyHint, openWorldHint and destructiveHint on every tool, and a written reason for each value in the submission[2]. A tool that sets all of them satisfies both. The field is part of the tool definition in the protocol[5].
One tool, annotated for both reviews
{
"name": "get_forecast",
"title": "Get forecast",
"description": "Get the forecast for a city.",
"annotations": {
"readOnlyHint": true,
"destructiveHint": false,
"openWorldHint": true
}
}
An example tool, not a real server. For a tool that writes, set readOnlyHint to false.
ChatGPT and Codex plugin directory: the steps
These are the portal's steps as ManyCP's catalog has them, checked . OpenAI's own guide, read on , also describes uploading a plugin as a ZIP file[1]. Read it before you start.
Sign in to platform.openai.com and finish individual or business verification in your organization's settings. The plugin is shown under that verified name.
Organization owners can submit. Anyone else needs the Apps Management Write role.
Package the plugin as a ZIP of 100 MB or less with a plugin.json: display name and short description (30 characters max each), long description (4,000 max), up to 3 starter prompts (128 max each), test cases, release notes and a demo recording URL.
Open platform.openai.com/plugins, upload the ZIP and pick your developer identity. A draft opens once it passes validation.
Host the token the portal shows, as plain text, at /.well-known/openai-apps-challenge on your MCP host. Verify the domain, then connect your server so its tools are scanned.
Set readOnlyHint, openWorldHint and destructiveHint on every tool.
Give exactly 5 test cases that should work and 3 that should not. If your server needs sign-in, give a demo login that works at once, with no sign-up, MFA, email or SMS code.
Click Submit for review and tick the policy attestations. After approval, click Publish plugin.
Claude Connectors Directory: the steps
Anthropic's page lists these portal steps[4]. The directory no longer accepts a local server packaged as an MCP Bundle; a local server goes inside a plugin instead[4].
Use a paid Claude plan (Pro, Max, Team or Enterprise). On Team, an Owner submits.
Open claude.ai/directory/manage and click Submit new.
Remote server: choose MCP connector. Local server: choose Plugin bundle, a GitHub repo with a .mcp.json.
Connector step 1: enter your HTTPS server URL and click Connect and authorize. Step 2 shows the tools it found. Fix any tool without a title or a read-only or destructive hint, then reconnect.
Step 3, Listing: name (100 characters max), slug (50, permanent), one-liner (200), description (2,000), up to 5 categories, author, docs, support and privacy links, icon.
Step 4, Use cases: up to 3 use cases with example prompts, what people need first, and read, write or both.
Step 5, Company: company name, website and a contact person.
Step 6, Authentication: OAuth (DCR, CIMD or a client Anthropic holds), or none. A static API key is not enough.
Step 7, Data handling: who owns the API, personal health data, sponsored content.
Step 8, Test and launch: write steps a reviewer can follow, with a demo account. Tick that you ran every tool.
Step 9, Compliance: tick 7 boxes. Step 10: read the recap and click Submit for review.
What ManyCP does for these two
ChatGPT and Codex plugin directory
Claude Connectors Directory
ManyCP prepares
plugin.json and mcp.json, ready to zip
The name and short description cut to 30 characters, the long description and starter prompts
A first set of test cases, in plugin.json
A checklist of what OpenAI's review checks, each linked to OpenAI's docs
A zip command and a command to check your domain challenge file
Answers for steps 3, 4, 5 and 7: name, slug, one-liner, description, categories, author, links, use cases, prerequisites, read or write
A link that adds your server to Claude as a custom connector, to test first
For a local server: the .mcp.json for a plugin bundle
You do
Verify your identity
Add your logo and URLs, zip the folder and upload it
Host the challenge token, verify your domain and connect your server
Write the privacy and terms pages and record the demo
Submit for review, then Publish after approval
Sign in on a paid plan
Connect and authorize (step 1)
Give a test account (step 8)
Tick the 7 compliance boxes (step 9)
Submit
When you don't need ManyCP
You are sending one server to one of them. The steps above are the whole job, and you do them with your own account either way.
Your server is not ready. Both reviews look at tool annotations and at a reviewer account that can sign in, so fix those first.
You only want the listing text. Write it from your README; the limits are in the steps above.
ManyCP helps when the same server goes to several directories at once, or when the listing text has to stay the same in all of them. See all 26 directories compared, or run the free checker to see where a repo is listed today.
