What to prepare

  • A public source containing one reviewed root MCP configuration matching the actual release.
  • A dedicated owner login and complete owner-profile inventory for pending/public duplicate checks.
  • A pinned source revision, approved component/name/description and unchanged publishing form.

A real MCP component and an authorized publisher

Cursor’s community directory imports MCP configuration from a public repository. The service requires one supported MCP component, freezes the imported configuration and rechecks the source before Scan and Publish. A dedicated owner profile exposes pending submissions so they are not posted twice.

The returned plugin page proves submission. Public discovery of the matching source and name proves listing; scans, moderation and official Marketplace curation remain separate decisions.

Submission workflow

  1. Prepare and merge the reviewed MCP configuration if needed.
  2. Authorize the account login; the service checks existing owner entries and public listings.
  3. Review the exact imported MCP component and listing fields before paying.
  4. The service scans and publishes through the owner session, retains the returned plugin page, and follows moderation.

Blockers to resolve before review

Use these as preparation checks. The destination makes its own acceptance decision.

  • An old MCP submission URL or outdated field list is used after the directory changed scope.
  • The plugin package does not describe or load the intended MCP component.
  • Client-specific behavior is advertised as portable without testing.

Primary sources

Checked 2026-10-30. Follow the destination’s current instructions if its requirements change.

← Compare all destinations