Lists CE's public MCP endpoint (`https://godbolt.org/mcp`) in the
[official MCP Registry](https://registry.modelcontextprotocol.io) as
`io.github.compiler-explorer/compiler-explorer`.
### What's here
- `server.json` — the registry record. Validated with `mcp-publisher
validate` against the live registry.
- `docs/MCP.md` — a "Registry listing" section covering how and when to
re-publish.
### Notes for review
**Publishing is deliberately not wired to a deploy.** The registry
stores metadata only — it records where the endpoint is, not what's
running behind it. Nothing in the record changes when the site updates,
and the registry rejects a repeat of an existing version, so a publish
on every deploy would simply fail. `server.json`'s `version` identifies
the *metadata record*; it's unrelated to `gh-NNNNN` build numbers.
Re-publish by hand on the rare occasion the file changes (documented in
`docs/MCP.md`). No CI workflow, and no infra changes.
**The namespace comes from GitHub org ownership**, not DNS —
`io.github.compiler-explorer/*` is granted to Owners/admins of the org,
so no TXT records or `.well-known` files are involved. It was chosen
over `org.godbolt/*` because the GitHub identity has exactly one name,
sidestepping the godbolt.org / compiler-explorer.com question.
**`name` is the one field that can't be changed later.** The URL,
description and icon all live in a versioned record and can be updated
by bumping the version and re-publishing — worth a second look at that
line specifically.
Not yet published — that needs a `mcp-publisher login github`
device-code auth from an org admin.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
