How to Submit an MCP Server to the Claude Connectors Directory (Step by Step)
You submit a remote MCP server to Claude's Connectors Directory through the developer portal at claude.ai/directory/manage, choosing Submit new and then MCP connector. Your server must be reachable over HTTPS, every tool needs a title plus a readOnlyHint or destructiveHint annotation, and authenticated services must use OAuth 2.0. Anthropic scans each submission automatically and, by default, lists it as a Community connector; Anthropic says review time isn't fixed.
This guide walks through Anthropic's published submission flow for a remote MCP server, in the order the developer portal asks for things. Everything here comes from Anthropic's connector docs and the Software Directory Policy. mcplisted is not affiliated with Anthropic, and following these steps does not guarantee a listing.
Who can submit
You submit from a claude.ai account, and the listing belongs to the organization you submit from. Anthropic lists these conditions:
- Plan: Pro, Max, Ultra, Team, or Enterprise. Free accounts can't submit.
- Role: on Pro, Max, and Ultra you submit from your own account. On Team and Enterprise an Owner submits, and on Enterprise an Owner can grant a Directory permission to other members through a custom role.
- No partner program: Anthropic says there is no program to apply to first.
What you can submit as a connector
- Remote MCP servers: internet-hosted servers. The portal asks for an
https://URL. - MCP Apps: remote servers that render interactive UI. These also need carousel screenshots.
- Local servers: the directory no longer accepts local servers packaged as MCP Bundles (MCPB). To distribute a local server, Anthropic says to include it in a plugin. See local vs remote MCP servers.
If you also ship a plugin that points at your remote server, Anthropic still recommends submitting the server as its own MCP connector so you get the listing, authentication settings, and dashboard.
Pre-submission checklist
- Server is remote and answers on an
https://URL - Authentication works in Claude: OAuth 2.0 if tools act on a user's account, or no auth for public data
- Every tool has a
titleand areadOnlyHintordestructiveHintannotation - Tool names are 64 characters or fewer
- No catch-all tool that mixes reads and writes (for example
api_requestwith amethodparameter) - You added the server as a custom connector in Claude and called every tool
- You have a documentation URL, privacy policy URL, support contact, and an icon
- For an MCP App: 3 to 5 PNG screenshots, at least 1000px wide
A tool definition that passes the annotation check looks like this:
{
"name": "list_invoices",
"title": "List invoices",
"description": "Lists invoices in the connected account, newest first.",
"inputSchema": { "type": "object", "properties": { "status": { "type": "string" } } },
"annotations": { "readOnlyHint": true }
}
The portal flags tools that are missing titles or annotations. More detail is in tool annotations and why reviewers check them.
Requirements every connector must meet
| Area | What Anthropic requires |
|---|---|
| Terms | Comply with the Software Directory Terms and Software Directory Policy |
| Security | Meet Anthropic's security standards; respond to security issues promptly |
| Tool annotations | title plus the applicable readOnlyHint or destructiveHint on every tool |
| Authentication | OAuth 2.0 for authenticated services |
| Transport | Policy says remote servers should support Streamable HTTP; SSE is allowed for now |
| Errors | Handle errors gracefully with helpful messages, not generic ones |
| Documentation | Clear setup and usage docs, public by your publish date |
| Unsupported | Money or crypto transfers, and AI image, video, or audio generation (design visuals are allowed) |
The 10 steps in the developer portal
Open claude.ai/directory/manage, select Submit new, and choose MCP connector. Progress saves in your browser as you move between steps.
- Connection: paste your server's
https://URL or pick a custom connector you already added. If users connect to different URLs, choose Multiple URLs or URL pattern. Those listings can be published only once they have the Verified label. - Tools: tools, prompts, and resources sync from your server, grouped as read-only or write. Fix any flagged tools on the server before you continue.
- Listing: server name up to 100 characters, one-liner up to 200, description up to 2,000, one to five categories, documentation URL, privacy policy URL, support contact, icon, and a URL slug. The slug is permanent once published.
- Use cases: primary use cases, what users need before connecting (accounts, plans), and whether the connector reads, writes, or both.
- Company: company name, website, and a primary contact for review updates.
- Authentication: whether sign-in is required and which methods users have. Pick Required when the server asks if only some tools need sign-in. You can also enter an OAuth client here for Anthropic to hold. See OAuth for remote MCP servers.
- Data handling: whether the API is your own, proxied with permission, or a third party's, and whether you handle personal health data or sponsored content.
- Test & launch: confirm you ran every tool through MCP Inspector or as a custom connector. Don't put credentials in the portal.
- Compliance: seven required acknowledgments covering directory guidelines, first-party API usage, financial transactions, AI media generation, prompt injection, conversation data collection, and public documentation.
- Review and submit: a final check. Quality warnings, such as very short answers, are shared with the review team.
Quick server checks before step 1
Anthropic's troubleshooting guide lists checks you can run from a public network. Two catch a lot of failures:
# Must not be a 3xx redirect to another host
curl -sI https://mcp.example.com/mcp
# Should return 200 with JSON if you use OAuth
curl -i https://mcp.example.com/.well-known/oauth-protected-resource
Claude drops the Authorization header when it follows a redirect to a different host, so register the URL your server actually listens on. You can also run a free check against these and the other published requirements. The full routine is in how to test a remote MCP server.
What happens after you submit
Anthropic scans each submission automatically for policy compliance and, by default, lists it as a Community connector with no action from you. Some submissions also get a review by a person. Anthropic may escalate listings it flags as highly useful to Verified review, where reviewers test each tool; if your connector needs sign-in, a reviewer emails you for test access. There is no application for the Verified label.
Anthropic says review time isn't fixed and varies with queue volume. Status and reviewer feedback appear in the portal, and escalations go to mcp-review@anthropic.com. The statuses are explained in what happens after you submit.
Paste your URL and see what Claude, ChatGPT and Gemini reviewers will flag.
FAQ
Do I need a paid Claude plan to submit an MCP server?
Yes. Anthropic lists Pro, Max, Ultra, Team, or Enterprise. Free accounts can't submit, and on Team and Enterprise an Owner submits.
How long does Claude directory review take?
Not published. Anthropic says review time isn't fixed and that human review times vary with queue volume.
Can I submit a local stdio MCP server?
Not as a connector. The directory no longer accepts local servers packaged as MCPB; Anthropic says to include a local server in a plugin instead.
Does publishing to the MCP Registry list me in Claude?
No. Anthropic says its directory is independent of the open MCP Registry, and publishing there doesn't surface your server in Claude.
How do I get the Verified label?
You can't apply for it. Anthropic escalates some Community listings to Verified review automatically, based on whether they are flagged as highly useful to Claude users.
Sources
- Submit a connector to the directory (Claude docs)
- Connector pre-submission checklist (Claude docs)
- Anthropic Software Directory Policy
- Publish to the directory (Claude docs)
- Connector verification (Claude docs)
- Track your directory submission (Claude docs)
- Troubleshoot your connector (Claude docs)
- Directory connectors vs custom connectors (Claude docs)
Rules change. If something here is out of date, email hello@mcplisted.com and we'll fix it. See our editorial policy.