EveryMCP
← All marketplace guides
Claude logoClaude
Core platform path•Path checked

Claude Connectors Directory

Anthropic's first-party directory accepts remote MCP servers through the Claude.ai portal. Desktop extensions are a separate path with different packaging requirements.

The brand reference above links to an official platform source. EveryMCP is an independent directory and is not endorsed by this platform.

Destination type

First-party directory

Integration mode

Hosted and local

Eligibility and connection boundary

The checked guide requires a Team or Enterprise organization and directory-management permission. Remote entries can use OAuth, a custom connection, or no auth when appropriate.

Review or publication path

Directory entries are expected to meet security and functionality standards, use clear titles and annotations, maintain accurate docs, and respond to user or review issues. Inclusion is a reviewed directory decision.

Cost and terms

No directory submission fee is stated on the checked guide. Confirm organization plan and portal terms before submitting.

Preparation checklist

  1. 1.Choose the remote directory path or the separate desktop-extension path before packaging anything.
  2. 2.Define OAuth, custom-connection, or no-auth behavior and document the minimum scopes and data flow.
  3. 3.Use descriptive titles, tool annotations, setup instructions, and an honest privacy and support contact.
  4. 4.Keep a versioned test account, a rollback plan, and a response owner available for directory review.

Open questions

  • • Review timing and current regional availability.
  • • Whether a local desktop extension or a remote server is the correct path for a particular client workflow.
Receipt boundary: A connection, a submitted PR, or a registry record does not prove marketplace approval. Keep the platform response, version, review state, and rollback plan with the release evidence.