mcp-registry-publish

To publish an MCP server to the official registry, you validate your server.json against the registry schema and ensure GitHub namespace authentication alignment. This skill automates pre-flight checks, metadata generation, and the publish flow.

Validating server.json against the MCP registry schema involves checking that your server identity and version align with your package manifest. The validation process ensures metadata correctness and GitHub namespace authentication alignment before publication.

Yes, you need GitHub namespace authentication alignment to publish to the MCP registry. The publishing workflow verifies your GitHub identity to ensure you have the authority to publish the server under a specific namespace.

Validating and publishing MCP servers requires curl, python3, jq, grep, npx, and sed. These dependencies support the scripts that automate pre-flight checks, metadata generation, schema validation, and the registry publish flow.

Your MCP server is not publishing to the registry likely because server.json validation failed or GitHub namespace authentication is misaligned. The publish flow performs pre-flight checks to identify metadata mismatches between your server identity and package manifest before attempting publication.