submitmcp

Guides · Checked November 8, 2026

How to get your MCP server into Claude's directory

Claude has the most open of the big directories. Anyone on a paid plan can submit a remote server in Anthropic's developer portal, an automated scan checks it, and most connectors are listed as Community connectors within days. A person only tests your tools if Anthropic picks your connector for Verified review, which you can't apply for.

What changed in 2026

Until September 2026, you submitted a remote server through a Google Form that warned it couldn't promise a reply. Developers waited three to seven months, and some never heard back (r/ClaudeAI). Anthropic then closed the old queue and asked everyone in it to submit again.

On September 25, 2026, Anthropic opened one developer portal for connectors and plugins, with usage figures for each listing (Anthropic). Two days earlier it launched Claude Marketplace, a website that shows the same directory. There's no separate Marketplace submission (Anthropic).

Desktop extensions (.mcpb) are no longer accepted. A local server can only get into the directory inside a plugin.

Connector or plugin?

The portal at claude.ai/directory/manage asks which one you're submitting (Anthropic):

  • MCP connector: a remote server, identified by its URL. No repository needed.
  • Plugin bundle: a GitHub repository with skills, commands, agents or MCP server settings. It has to be public before it goes live.

If you run a remote server, submit it as a connector even if you also submit a plugin that uses it. The connector listing gets its own dashboard and sign-in settings, and you can pair the two listings. The exception is a server that takes an API key: connectors sign in with OAuth or not at all, so a plugin, which can ask the user for a key, is the way in. Connectors vs plugins compares the two, and what other apps call them.

Before you start

  • A paid plan: Pro, Max, Ultra, Team or Enterprise. On Team and Enterprise, an Owner submits. The listing belongs to the organization you submit from, so pick the one that should own it long term.
  • A remote server Claude can reach (Anthropic):
    • Streamable HTTP. The older HTTP with SSE still works, but is being phased out.
    • A hostname with a public IPv4 address. Connectors don't work over IPv6 only.
    • No redirect to another host: Claude drops the Authorization header when it follows one.
    • Anthropic's traffic comes from 160.79.104.0/21. Allow it through your firewall, and through the one in front of your sign-in provider.
  • Sign-in Claude supports. No sign-in, OAuth with dynamic client registration, OAuth with a Client ID Metadata Document, or OAuth with a client you give Anthropic in the portal. API keys entered by an admin are in a limited beta. Machine-to-machine OAuth isn't supported.
  • OAuth details that trip people up:
    • The callback URL is https://claude.ai/api/mcp/auth_callback. Claude Code uses http://localhost/callback on a random port, so match it without the port.
    • A request without a token must get a 401 with a WWW-Authenticate header that points at your resource metadata. Claude ignores that header on any other status.
    • The resource in that metadata must match your server URL exactly, and Claude only uses the first authorization server listed.
    • PKCE with S256 is required.
  • Limits. Tool results are cut off at about 150,000 characters in claude.ai and Claude Desktop, and 25,000 tokens in Claude Code. A tool call times out after 240 seconds (Anthropic).

What you need to prepare

From the portal and Anthropic's directory policy:

Item Requirement
Name Up to 100 characters
One-liner Up to 200 characters
Description Up to 2,000 characters
Categories 1 to 5
Web address (slug) Permanent once published
Documentation Public by the time you publish. A help article or blog post is enough
Privacy policy Covering what you collect, why, and how long you keep it
Support A contact that works
Example prompts At least 3
Test account Email and password, already filled with data
Screenshots Only for interactive apps: 3 to 5 PNGs, at least 1,000 pixels wide, cropped to the app's response

Tool annotations. Every tool needs a title, plus readOnlyHint: true if it only reads. Claude uses the hints to decide which tools need the user's confirmation (Anthropic). On every other tool, set readOnlyHint: false and set destructiveHint explicitly, true if it deletes or overwrites: under the MCP spec, a write tool without destructiveHint counts as destructive (Privatrak). The portal reads annotations.title, not a title at the top level of the tool, so set that one (Remoet).

Tool names have to be 64 characters or fewer.

Submitting, step by step

The connector form has ten pages and saves as you go (Anthropic):

  1. Connection: your server's URL. Listings with several URLs or a URL pattern can only be published once Verified.
  2. Tools: synced from your live server. The portal flags tools without a title or annotations. Fix those on the server, not in the form.
  3. Listing: name, one-liner, description, categories, documentation, privacy policy, support contact, icon and web address.
  4. Use cases: the main tasks, what users need before connecting, and whether it reads data, writes data, or both. Write them as real tasks, like "find last month's unpaid invoices" rather than "invoice search" (MCP Tower).
  5. Company: your company and a contact for review updates.
  6. Sign-in: when users have to sign in and how, plus your OAuth client if Anthropic should hold it. The portal can guess your sign-in mode wrong, so check it (Remoet).
  7. Data handling: whether the API is yours, proxied with permission or someone else's, and whether you handle health data or sponsored content.
  8. Test and launch: how reviewers get in, and credentials for the test account. You confirm you've called every tool yourself.
  9. Compliance: seven statements, about the directory rules, using your own API, payments, AI-generated media, prompt injection, collecting conversation data and public documentation.
  10. Review and submit. Quality warnings, like very short answers, are passed on to reviewers.

Plugins go through five pages instead, starting from your GitHub repo (Anthropic). Run claude plugin validate first. Anthropic blocks a plugin with a README under 40 words, no LICENSE file, npx or uvx packages without an exact version, or secrets in the repo, and sends anything with binaries or bundled packages to a person (Anthropic). An organization can submit 10 plugins a day.

Community and Verified

Every connector is scanned automatically and, by default, listed as a Community connector. Anthropic may escalate one it finds especially useful to Verified review, where a person tests each tool against its checklist. You can't apply for Verified or for a better spot (Anthropic).

Verified connectors are a minority: about 1,450 of 9,300 listings in early November 2026 (Gaintage).

How long review takes

Anthropic says review time isn't fixed (Anthropic). Since the portal opened, Community listings have been fast:

  • About an hour, approved automatically (Privatrak, October 2026).
  • Four days after resubmitting in the portal, following three months of silence on the old form (3Min API).
  • Four and a half days, after a May submission was never listed (Remoet).

Approved doesn't mean live: select Publish in the portal. If you edit before publishing, it goes back to draft. If you're stuck, email [email protected] for connectors or [email protected] for plugins. A polite follow-up has gotten replies within a day (r/mcp).

Why connectors get rejected

Anthropic's checklist is built around its most common rejections (Anthropic):

  1. One tool that both reads and writes, like an api_request tool with a method parameter, even if the description says which methods are safe.
  2. Missing or wrong annotations.
  3. Tool names over 64 characters.
  4. Descriptions that steer Claude: telling it to call or avoid other tools, to fetch instructions from elsewhere, hidden text, or promotion. One team rewrote 14 descriptions that were "bossing the agent" before it passed (Remoet).
  5. Query tools that don't say which API they query. Name and link it: "Queries the Slack Web API, see api.slack.com/methods".
  6. Tools that fail with valid input, or return a bare "Internal Server Error".
  7. Responses that are too big.
  8. Collecting conversation data, or reading Claude's memory, chat history or uploads.
  9. Calling an API you don't own or have permission to proxy.
  10. Moving money without a person approving it, crypto, or generating images, video or audio.
  11. An empty test account.

Developers add:

  • Reviewers can't get in. Firewalls and bot protection blocking review traffic, a 403 instead of a 401 without a token, or a 404 because of a trailing slash (reviewtimes.fyi). A test account that signs in with Google and a phone code fails too: use a plain email and password (Privatrak).

Rules that can rule you out

From the directory policy:

  • No payments or trades without a person approving each one, and generally no crypto.
  • No AI-generated images, video or audio. Slides, diagrams, charts and mockups are fine.
  • No ads, sponsored content or paid placement.
  • No adult content.
  • Collect only the data you need, never read Claude's memory or chat history, and don't build user profiles.
  • You own or control every domain and API your server touches.

After you're live

  • Your listing is at claude.ai/directory/connectors/your-slug, and the same catalog serves claude.ai, Claude Desktop, mobile, Claude Code and Cowork.
  • Ranking is by usage, and every listing can show up as a suggested connector inside a conversation (Anthropic).
  • A dashboard shows your rank, accounts that used a tool, tool calls, error rate, latency and a health badge, updated daily (Anthropic).
  • Tool changes need no review: deploy your server. Listing changes are reviewed while the old listing stays up, and renaming always triggers a new review.
  • Connect faster in Claude Code by setting listChanged: false if your tool list never changes. It removed a 25-second delay when connecting (Privatrak).

Tools that help

  • MCP Inspector: list your tools from the command line with npx @modelcontextprotocol/inspector --cli https://your-server/mcp --transport http --method tools/list. Then add the server as a custom connector in Claude and call every tool from a conversation (Anthropic).
  • MCPJam: mcpjam readiness check claude grades your server against the directory rules, and its OAuth debugger walks through each sign-in step.
  • mcpready: npx mcpready preflight https://your-server/mcp --target claude.
  • Anthropic's troubleshooting checklist covers DNS, redirects, firewalls and sign-in metadata. Persistent failures can be reported with the error's reference ID on the claude-ai-mcp tracker.

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