What to prepare
- A public remote Streamable HTTP server with complete Docker slug, category, documentation and supported none/OAuth authentication metadata.
- A matching healthy Glama connector evaluation and accurate authentication declaration.
- The operator’s configured official Docker catalog validator at an approved pinned revision, confirming the exact public files.
- A verified operator GitHub contribution identity and passing current upstream requirements.
The initial execution route is remote
Docker supports different contribution paths for local containers and hosted remote services. The initial MCP Server List adapter covers a public remote service with supported authentication metadata; it does not sell an unreviewed local container build.
Supply the exact endpoint, documentation, slug and category. The generated public files form an installation contract, so configuration errors should be corrected during the free preflight rather than discovered after charging.
Validate the exact contribution before charging
A plausible server.yaml is not enough. The operator must configure the official catalog validator and approved revision, then confirm that the precise generated files passed. Missing tooling, unsupported authentication or a changed validation contract blocks purchase.
The worker repeats that validation before its first write. No secret value is committed to the catalog contribution. OAuth or reviewer-access requirements must follow Docker’s documented private setup rather than public PR comments.
Distinguish a private catalog from public acceptance
A custom catalog can help your team test and distribute an internal server, but creating one does not put the server in Docker’s public catalog. Track the public contribution separately, with the PR and final catalog record as evidence. Local validation is readiness evidence, not an approval decision.
Submission workflow
- Choose the supported remote-server route and supply accurate profile and authentication fields.
- Run free preflight; generated remote catalog files must pass the configured official validator before payment.
- Review the exact files and authorize the checked launch; the worker revalidates and opens the contribution PR automatically after payment.
- Track review and merge separately from public catalog ingestion. Listed requires the expected endpoint in actual public catalog evidence.
Blockers to resolve before review
Use these as preparation checks. The destination makes its own acceptance decision.
- A container cannot build, start, or expose the expected MCP capabilities.
- Configuration hides a required secret or grants unnecessary filesystem or service access.
- The license, metadata, remote discovery, or reviewer test access does not meet current contribution requirements.
Primary sources
Checked 2026-10-29. Follow the destination’s current instructions if its requirements change.