What it does
The first majordomus mcp in a repository binds one shared server on the loopback
interface and logs every surface it serves: the home page, this documentation, the crate's
rustdoc, the Cockpit, the Swagger UI, the OpenAPI document, the capability routes and MCP
over HTTP. Every later client attaches to it instead of starting another, and the server
ends when its last client leaves. The client configurations at the repository root — one
per provider that reads one, as docs/generated/providers.md lists them — name one
launcher, so opening the repository in any of them is enough.
What the server answers is the registry: a tool, a resource, a route or a command exists because a declaration exists, and the same declaration is what the reference and the website render. A surface — the documentation mount, the crate's rustdoc, a generated report, the Swagger UI — is discovered from the thing that produces it, or from the source that says it exists, and resolved once into a topology the router, the home page, the publication and the validator all read.
What it does not do
Most of what is served reads. Every capability carries its effect in the registry: a read,
a change to the answering runtime's own state (the peer board, the mesh journal, the
evidence ledger), or a change to the repository. The ones that write the repository are
continuity.publish, continuity.resume, continuity.sync, executions.start,
intents.propose, mesh.enrol, plan.transition, reasoning.record and
recover.orphans;
the initialize instructions every client reads name them from the registry, and case
3363 refuses this page when its list and the registry's differ, because a sentence that
promises a read-only surface is exactly the sentence an agent acts on. There is no
authentication and no remote binding by default; the server is for the clients on this
machine. When it is bound beyond loopback, its reads answer whoever reaches it, and every
capability that changes something is refused to a remote caller unless a linked node
signed the input. It does not run a model and it does not route work to one.