There is a public MCP registry that serves as a central catalog of publicly available Model Context Protocol (MCP) servers, improving discoverability and standardizing how clients find and connect to servers.

Currently, the Coder remote MCP server is not listed in that registry. This makes it harder for developers and AI clients to discover, install, and integrate with Coder’s MCP server compared to other public MCP servers that are easily found via the registry.

Easy registry listing would help as a single source of truth for MCP servers and get the Coder server in front of more users and tools. https://blog.modelcontextprotocol.io/posts/2025-09-08-mcp-registry-preview

An example discovery & publish workflow is documented in the official registry docs: Adding Servers to the MCP Registry. (techcommunity.microsoft.com)

Desired Solution

Publish the Coder remote MCP server entry in the public Model Context Protocol Registry. This only requires adding a server.json file in the repo and setting up CI to publish new versions automatically.

Benefits:

• Better discovery by developers and MCP clients searching the registry for available servers
• Simplified installation/configuration via registry tooling

Links for reference:

• MCP Registry quickstart docs: https://github.com/modelcontextprotocol/registry/blob/main/docs
• MCP regsitry: https://registry.modelcontextprotocol.io/

Related

• JFrog is a similar SDLC tool that is also self-hosted and is already listed: https://registry.modelcontextprotocol.io/?q=jfrog