MCP Server Marketplace submission process

[dhurv123]

Hello Kilo Code Team,

We are preparing to publish our MCP server on the Kilo Code Marketplace and are comfortable making the repository public as required.

However, our MCP is still under *active development, and we would like to understand the recommended workflow for early testing after Marketplace publishing.

Specifically, we want to clarify:

Once an MCP is published to the Marketplace, is there any *supported way to perform early testing, such as:

staging or development mode

• limited rollout

• testing with a controlled set of users

• If no staging or restricted-access option exists, what is the best-practice approach you recommend for teams who want to:

  • publish early
  • observe real installation and usage behavior
  • validate how the MCP works when installed from the Marketplace
  • continue development safely before a stable release

At the moment, we do not see explicit staging or developer-mode options in the documentation, so we wanted to confirm the intended process directly with you.

Our goal is to ensure that we follow a Marketplace-compliant and safe workflow while validating our MCP in real-world conditions before declaring it fully stable.

Any guidance or recommended patterns would be greatly appreciated.

Best regards,
Sphere Plugins