Deployment Guide
Walks through publishing a server to the MCP Registry using the official mcp-publisher CLI tool.
What this file does
Walks through publishing a server to the MCP Registry using the official mcp-publisher CLI tool.
When to use it
- You need to publish a server to the MCP Registry for the first time
- You are updating an existing MCP server version and re-publishing
- You encounter permission or schema errors during MCP Registry publishing
Assumes this stack
Deployment Guide
This guide covers publishing CodeAlive MCP to the MCP Registry.
Prerequisites
Install mcp-publisher
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 publisher
The binary will be at ./bin/mcp-publisher.
GitHub org membership (for org repos)
Your organization membership must be public:
- Go to https://github.com/orgs/CodeAlive-AI/people
- Find your username and set visibility to "Public"
Publishing to MCP Registry
1. Login with GitHub
./bin/mcp-publisher login github
Follow the device authorization flow:
- Go to the URL shown (e.g., https://github.com/login/device)
- Enter the code displayed
- Authorize the application
2. Update server.json
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)
3. Publish
cd /path/to/codealive-mcp
/path/to/registry/bin/mcp-publisher publish
On success:
Publishing to https://registry.modelcontextprotocol.io...
✓ Successfully published
✓ Server io.github.CodeAlive-AI/codealive-mcp version 0.4.7
Troubleshooting
"not authenticated"
Re-run login:
./bin/mcp-publisher login github
"403: your GitHub account doesn't have permission"
Make 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
"deprecated schema detected"
Update $schema in server.json to the current version. Check the migration checklist.
"OCI packages must not have 'version' field"
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).
Version Guidelines
- 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
Related Resources
What's inside
5 sections: prerequisites, publishing steps, troubleshooting, version guidelines, related resources. 4 code blocks, 1 JSON example.
Change this for your project
- Replace
CodeAlive-AIwith your GitHub org or username - Replace
io.github.CodeAlive-AI/codealive-mcpwith your server name - Replace
ghcr.io/codealive-ai/codealive-mcpwith your OCI package identifier - Replace
0.4.7with your current version
Where it goes
Keep it in your repository where the agent or team that needs it will read it.
Worth borrowing
- Using a dedicated publisher CLI for registry login and upload
- Embedding version in the OCI identifier tag rather than a separate field
- Providing a troubleshooting section with exact error messages and fixes
Related Documents
🌟 GitHub MCP Server - Feature Showcase
Showcases eight GitHub MCP server tools with example inputs, outputs, and real-world use cases for AI agents.
OpenCode Agents
Provides a collection of specialised Markdown agent files for OpenCode, each with a distinct role and thinking algorithm.
Chloe 部署文档
Guides you through deploying an enhanced SillyTavern fork with direct, Docker, and reverse-proxy setups, plus security hardening and troubleshooting.
msitarzewski/agency-agents
Curates a directory of 100+ specialised AI agent personalities for software engineering, design, marketing, sales, and more, each with identity, workflows, and deliverables.