feat: publish Coder MCP server to official MCP Registry - #21673
Conversation
This adds the necessary configuration to publish Coder's remote MCP server to the official MCP Registry at registry.modelcontextprotocol.io. Changes: - Add server.json with MCP server metadata for registry discovery - Add GitHub Actions workflow to automatically publish on release The MCP server is accessible at /api/experimental/mcp/http and provides workspace and template management tools for AI agents. Closes #21275
a5a0340 to
877efd8
Compare
Documentation CheckUpdates Needed
This addition bridges the gap between the existing "Remote MCP server" section and how users will discover Coder through the registry. Consider adding this as a new section after "Remote MCP server" explaining registry-based discovery as an alternative to manual configuration. No Changes Needed for:
Automated review via Coder Tasks |
The version is dynamically set from the git tag during the publish workflow. Using "0.0.0-dev" makes it clear this value is not manually maintained.
The version is dynamically set from the git tag during the GitHub Actions publish workflow. Using 0.0.0-dev makes it clear this value is replaced at publish time.
Addresses documentation feedback from PR review.
The specific server URL will 404 until first publish after merge. Link to the registry root instead. --- _Generated with `mux` • Model: `claude-sonnet-4-20250514` • Thinking: `none`_
- Remove broken registry link (registry has no browsable UI) - Update VS Code instructions to clarify registry discovery - Add comprehensive list of all 30+ available MCP tools - Fix Claude Desktop config to use OAuth2 instead of headers
Maintains the distinction between: - Local MCP server (CLI, stdio transport) - Remote MCP server (HTTP transport, MCP Registry) The MCP Registry publishing only applies to the remote server.
Keep the document title as "MCP Server" per maintainer preference.
Documentation CheckPrevious Feedback✅ Fully Addressed - The documentation has been completely rewritten and now comprehensively covers MCP Registry integration. Updated Documentation IncludesThe PR updates with:
The documentation now provides a complete guide from discovery through configuration, addressing all points from the previous review. No Further Changes NeededThe documentation is comprehensive and ready for users to discover and use Coder through the MCP Registry. Automated review via Coder Tasks |
Docs preview📖 View docs preview for |
Add workflow_dispatch with a manual semver version input and an opt-in publish flag. Manual runs default to validate-only (mcp-publisher validate) and never authenticate or publish unless explicitly requested. Version is derived from the tag on release events or the input on manual runs, and rejected unless it is valid semver so branch refs can never be published as a version. Generated with Coder Agents.
Documentation CheckUpdates Needed
Automated review via Coder Agents |
Move workflow_dispatch inputs into step env vars so they are not expanded inside run blocks (zizmor template-injection), and set persist-credentials: false on checkout (artipacked). Also run the markdown table formatter on docs/ai-coder/mcp-server.md to satisfy fmt and lint-docs. Generated with Coder Agents.
Point server.json documentation at the real page (/docs/ai-coder/mcp-server). List both the oauth2 and mcp-server-http experiments in Prerequisites, matching the remote MCP HTTP endpoint gate in coderd.go. Add the missing coder_get_template tool and link the tool tables to the authoritative toolsdk package to reduce drift. Generated with Coder Agents.
The per-category tool tables drift from the code over time. Replace them with a short overview of tool areas and a link to the authoritative toolsdk package, matching the previous version of this page. Generated with Coder Agents.
Summary
This adds the necessary configuration to publish Coder's remote MCP server to the official MCP Registry at registry.modelcontextprotocol.io.
Changes
server.json: MCP server metadata for registry discovery.github/workflows/publish-mcp-registry.yaml: GitHub Actions workflow to automatically publish on releaseHow it works
MCP Registry Entry
The server will be listed as
io.github.coder/coderwith:streamable-http{coder_url}/api/experimental/mcp/http/.well-known/oauth-authorization-server)Testing
After merge and next release, verify at:
curl "https://registry.modelcontextprotocol.io/v0.1/servers?q=io.github.coder"Closes #21275
Generated with
mux• Model:anthropic:claude-opus-4-5• Thinking:medium