This guide covers publishing CodeAlive MCP to the MCP Registry.
Build from source (documented install methods like brew install and install.sh are not available):
git clone https://github.com/modelcontextprotocol/registry.git
cd registry
make publisherThe binary will be at ./bin/mcp-publisher.
Your organization membership must be public:
- Go to https://github.com/orgs/CodeAlive-AI/people
- Find your username and set visibility to "Public"
./bin/mcp-publisher login githubFollow the device authorization flow:
- Go to the URL shown (e.g., https://github.com/login/device)
- Enter the code displayed
- Authorize the application
Before publishing, update server.json:
- Bump the version field to match your release
- Use the latest schema (currently
2025-12-11) - Update package identifier with new version tag
Example server.json structure:
{
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"name": "io.github.CodeAlive-AI/codealive-mcp",
"version": "0.4.7",
...
"packages": [
{
"registryType": "oci",
"identifier": "ghcr.io/codealive-ai/codealive-mcp:0.4.7",
"runtimeHint": "docker",
...
}
]
}Important notes:
- OCI packages must NOT have a separate
versionfield inside the package object - the version is embedded in theidentifiertag - Schema version must be current (check changelog)
cd /path/to/codealive-mcp
/path/to/registry/bin/mcp-publisher publishOn success:
Publishing to https://registry.modelcontextprotocol.io...
✓ Successfully published
✓ Server io.github.CodeAlive-AI/codealive-mcp version 0.4.7
Re-run login:
./bin/mcp-publisher login githubMake your organization membership public:
- Go to https://github.com/orgs/CodeAlive-AI/people
- Find your username
- Change visibility to "Public"
- Re-login and try again
Update $schema in server.json to the current version. Check the migration checklist.
Remove the version field from inside the packages array. The version should only appear in the identifier tag (e.g., ghcr.io/codealive-ai/codealive-mcp:0.4.7).
- Patch (0.4.6 → 0.4.7): Bug fixes, minor improvements
- Minor (0.4.0 → 0.5.0): New features, enhancements
- Major (0.x.x → 1.0.0): Breaking changes, major releases