What to prepare

  • A supported installation configuration and complete public profile.
  • A recognized marketplace category and nonconflicting entry.
  • Current contribution files, source authority and service-contributor access verified before payment.

A maintained client ecosystem

Kilo’s marketplace contains MCP servers alongside other agent capabilities. Use the MCP entry format and test the actual installation configuration. The initial adapter intentionally supports a constrained subset; free preflight explains unsupported combinations before checkout.

Submission workflow

  1. Read the maintained marketplace format.
  2. Inspect the exact generated configuration and source identity.
  3. Approve the contribution payload and pay for the checked launch.
  4. Track the PR and verified merged entry.

Blockers to resolve before review

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

  • Unsupported configuration, authentication or missing fields.
  • Duplicate identity or changed upstream contribution requirements.

Primary sources

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

← Compare all destinations