Documentation

How this registry works

This site is the durable list of every MCP server the estate runs. It is generated from one JSON file: 23 servers and 286 tools in the registry right now. Nothing on a page is hardcoded per server.

What an MCP is here

An MCP server is a small process or endpoint that exposes tools to a model client over the Model Context Protocol. In this estate it is one of two things:

  • In-house. We build it, we run it, and it carries our own safety rules. It gets an operator client in Pocket ID and a row in the estate directories.
  • Vendor. We install and configure someone else's server. It gets a card here with the tools it publishes, its transport, and a link to the vendor documentation.

A registry entry is a claim about a server: what it is called, what it does, how a client reaches it, what it can change, and where its own documentation lives. The tools listed are the documented surface, not a promise that every tool is enabled in your client.

Adding a server

The policy is one line: a new MCP is not done until it is in this registry with a documentation page. The steps:

  1. Build or install the server and get it answering tools/list.
  2. Add one entry to data/mcp-registry.json: slug, name, category, tagline, summary, transport, surface, enabled, version, safety, install, website, tools.
  3. The entry becomes a catalog card and a /mcp/<slug>/ page on the next load; nothing is hardcoded in a template.
  4. Link where it lives (website or repo page) and the documentation URL. Local filesystem paths stay out of the public copy.
  5. If it is in-house, it also gets a Pocket ID operator client and a registry row; the console only ever shows read-only state.
  6. Run the site tests. An empty summary, an unknown transport or a malformed entry fails them; an upstream tool with no description is reported as a warning on /watchdog and does not block the page.

The site reads data/mcp-registry.json on every request (cached by mtime). It never writes the file: the estate orchestrator owns refreshes, so a page cannot drift from the snapshot it documents.

Transport legend

stdioThe client starts the server as a child process and speaks JSON-RPC over stdin/stdout. No port, no network, no shared secret.
httpThe client calls a remote HTTPS endpoint with a scoped bearer key. The key lives in the client environment; this site never stores one.

Safety legend

Read-only by defaultA server that only lists or reads cannot change the estate, whatever the client asks.
Scoped credentialsWrite-capable servers take a key whose scope names the write. The server checks the scope again before acting.
Back up, then writeWrites that reach a live service back up first, replace atomically and record the run.
Local onlyDesktop servers are stdio on one machine. They are never published through a tunnel or the reverse proxy.

Public registry JSON

/registry.json is a field-allowlisted copy: slugs, names, categories, taglines, summaries, transports, enabled state, versions, websites, documentation URLs and tool names. It deliberately omits the repo field and every local filesystem path, and it contains no credential, token or connection string.

Machines may read it freely. It is cached for five minutes and is not an authorization surface.

The private console

/console/ is read-only telemetry for the mouse driver. It requires a Pocket ID sign-in whose subject is a configured operator. A signed session that is not an operator gets a 403 and no data. There are no arm, disarm or click controls on the site: arming stays local to the desktop, and the console can only look.

Telemetry is proxied server-side to 127.0.0.1:8340 with a 1.5-second timeout and a 400 ms cache. If the driver is not running, the console says so and every public page still renders.

Watchdog

/watchdog shows six checks computed on request: site reachable, TLS, the reverse tunnel unit, the driver link, registry freshness and deploy freshness. The light profile has no scheduler and no history store, so it shows current state and says plainly that no uptime percentage is collected. /watchdog.json is the same data for machines.

Categories

23 servers across 11 categories, in-house first, then vendors alphabetically inside each category.

BrowserDrive a real browser for checks, screenshots and end-to-end tests.
CodeWork with repositories, diffs, review and static analysis.
DataTalk to a database or cache. Connection strings stay in the client environment, never in this registry.
DesignProduce or inspect diagrams and design files.
DesktopTouch the machine itself: pointer, windows, input. Local stdio only, never exposed.
InfrastructureCloud, containers, clusters and the homelab.
KituwaServers we build and run ourselves. These carry our own safety rules and are the ones the console can inspect.
MediaTranscode, inspect and cut audio and video.
ReasoningStructure a problem before acting on it.
UtilitySmall deterministic helpers such as time and identifiers.
WebFetch and read pages on the public web.