Marketplace Publishing

The Cosmo marketplace lets teams discover and install pre-built MCP integrations. Publishing your server makes it available to all Cosmo organizations.

Before you publish

Your server must meet these requirements:

• Passes the MCP Server Spec requirements
• Has a public, stable endpoint (for remote servers) or a published npm package (for stdio servers)
• Includes a clear README with setup instructions and tool descriptions
• Does not store user credentials beyond what's needed for the integration

Submission process

Marketplace submissions are currently reviewed manually. To submit:

1. Prepare your server — ensure it meets the spec requirements above
2. Write a connector definition — a JSON descriptor that tells Cosmo how to install and configure your server
3. Submit for review — open a pull request to the Cosmo connector registry (link provided after signing up as a developer partner)

Connector definition format

Each marketplace entry is a ConnectorProvider record. The required and optional fields mirror the ConnectorProvider database model exactly:

{
  "serverId": "my-integration",
  "displayName": "My Integration",
  "description": "Connect Cosmo to My Integration for ...",
  "iconUrl": "https://cdn.example.com/logo.png",
  "category": "productivity",
  "authMode": "API_KEY",
  "mcpTransport": "HTTP",
  "mcpUrl": "https://mcp.example.com",
  "mcpCommand": null,
  "mcpArgs": []
}

For stdio servers (local process), use:

{
  "serverId": "my-local-server",
  "displayName": "My Local Server",
  "description": "...",
  "authMode": "NONE",
  "mcpTransport": "STDIO",
  "mcpCommand": "npx",
  "mcpArgs": ["-y", "@myorg/my-mcp-server"]
}

authMode values: NONE · API_KEY · SERVER_MEDIATED · REMOTE_OAUTH

mcpTransport values: STDIO · SSE · HTTP

Categories

Choose the category that best fits your integration:

Versioning

Marketplace connectors are versioned. When you push a breaking change:

1. Bump the version field in your connector definition
2. Document what changed in the changelog field
3. Cosmo will prompt existing users to reconfigure if credentials or config fields changed

After publishing

Once approved, your connector appears in the Cosmo marketplace under the Connect tab. Users can install it with one click, and Cosmo handles credential storage, OAuth flows, and MCP lifecycle management.

To update a published connector, submit a new connector definition with an incremented version. Patch updates (bug fixes, no config changes) are auto-approved; minor and major updates go through a lightweight review.