What to prepare

  • An installable supported profile and a public, active source repository.
  • An exact canonical marketplace tag and an unused entry identity.
  • Passing source-owner, operator-contribution, schema and duplicate checks.

Installation metadata is part of distribution

Cline stores entries under registry/mcps with a matching identifier and schema. Installation arguments describe the actual connection; tags come from the repository vocabulary. Contributor entries leave verified false. A merged entry and a reviewed verification badge are separate outcomes.

Submission workflow

  1. Inspect the current contribution schema and installation arguments.
  2. Review the generated entry and exact target files in preflight.
  3. Authorize the checked launch; payment queues the contribution PR.
  4. Follow the verified PR receipt and merged entry separately.

Blockers to resolve before review

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

  • Unknown tags or invalid install arguments.
  • A duplicate, conflicting or unsafe entry.

Primary sources

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

← Compare all destinations