Getting a connector listed in the Claude Connectors Directory
To list an MCP connector in the Claude Connectors Directory or a plugin in the Claude plugin directory, submit it through the directory submission portal Anthropic opened on September 25, 2026. You submit a connector as a remote server URL, and a plugin as a bundle hosted on GitHub.
The portal runs automated checks and a safety scan on both, and shows each submission's review status and the changes Anthropic asks for. New connectors are listed as Community. For a plugin, once a version passes you decide when to publish it, and by default an Anthropic reviewer then publishes it; after launch, the plugin's listing reports installs, listing views and the searches that find it.
Below is each requirement we track, with its source and the date we last checked it.
Reviewed by Mohd. Ashhar · Last verified:
Invokary is an independent studio. We are not affiliated with or endorsed by Anthropic, OpenAI or Anysphere.
Requirements
Submission
Anthropic opened its directory submission portal, for plugins and MCP connectors, on September 25, 2026.
The portal accepts two kinds of submission: an MCP connector, given as a remote server URL and listed in the Connectors Directory, or a plugin bundle hosted on GitHub and listed in the Claude plugin directory.
Plugin and connector submissions go through automated checks and a safety scan.
Plugin and connector publishers see each submission's review status in the developer portal, and the changes Anthropic asks for.
Once a plugin version passes review, you select Publish. By default an Anthropic reviewer then publishes it, and Anthropic can let later versions publish automatically.
Official sourceSource: Claude docs: Submit your plugin; Anthropic, September 25, 2026: Build plugins for Claude with the directory submission portalChecked
Who can submit
Plugins and MCP connectors have the same submitter rules: Pro, Max, Team and Enterprise plans can submit; free accounts can't. On Team and Enterprise an Owner submits, and on Enterprise an Owner can also grant the Directory permission to other members.
Official sourceSource: Claude docs: Publish to the directory; Claude docs: Submit a connector to the directoryChecked
Listing tiers
New Connectors Directory listings carry the Community label. Anthropic may escalate a connector to Verified review on its own: there is no application, and Verified reviewers run a functional test of each tool.
Official sourceSource: Claude docs: Connector verification; Claude docs: Connector pre-submission checklistChecked
Auth
Claude connects to a remote MCP server with OAuth 2.0, where each user signs in, with a static API key or bearer token that an organization Owner enters once (in beta, for a limited set of organizations), or with no authentication.
Review rules
Every tool has a title and the applicable hint: readOnlyHint for read-only tools, destructiveHint for tools that modify or delete data.
Tool names are 64 characters or fewer.
Tool descriptions say what the tool does and when to use it. They must not tell Claude how to behave.
A single tool that mixes safe and unsafe HTTP methods, such as a catch-all api_request tool, is rejected. Read and write actions go in separate tools.
A connector submission includes test credentials for a fully populated account.
For a plugin bundle, the first organization to submit a repository folder holds that listing.
After launch
After launch, plugin publishers see installs by product surface and version, listing views, and the searches that lead to a listing.
Official sourceSource: Anthropic, September 25, 2026: Build plugins for Claude with the directory submission portalChecked
Extensions
Claude supports two MCP extensions for connectors and the plugins built on them: MCP Apps, for interactive UI inside chat, and Enterprise Managed Auth, for zero-touch OAuth for enterprise users.
Common rejection risks
Submitting from an account whose plan or directory permissions do not qualify
A tool without a title, or with the wrong read-only or destructive hint
A tool name longer than 64 characters
Requirement: Tool names are 64 characters or fewer.
A tool description that tells Claude what to do
Requirement: Tool descriptions say what the tool does and when to use it. They must not tell Claude how to behave.
Another organization submitting your repository folder first
Requirement: For a plugin bundle, the first organization to submit a repository folder holds that listing.
A catch-all tool that mixes read and write actions
Test credentials that aren't for a fully populated account
Requirement: A connector submission includes test credentials for a fully populated account.
Already rejected?
How we handle it
- We design 8 to 20 tools, each with a title, the right read-only and destructive hints, and a description written for the model, not at it.
- We build OAuth 2.1 with Client ID Metadata Documents plus a DCR fallback, so each user signs in with their own account.
- We run MCP Inspector and our eval suite before every submission.
- We submit from your accounts, so the listing is yours.
- The Sprint includes two rejection cycles.