Process & Registry

Resources — read

Every docs/*.md + tools/*.json + root guidance

Registered individually at server start, not hand-listed — a new file shows up automatically next session.

Tools — act

run_checker, register_repo, promote_to_lockup

Thin wrappers around existing tools/*.mjs scripts — no tool writes an arbitrary field.

The family MCP server — transitional

Transitional since 7 Oct 2026 (Family #21). The canonical remote development-context path is now the static https://family.amoleo.com/api/* surface documented in family-development-context-api.md. Do not add new MCP consumers.

The local stdio MCP server in mcp-server/ predates the static development context API. It solved a real problem: a coding session rooted in Pets, Connections or another sibling repo should not have to guess where Amoleo-Family was checked out before it can read a Family rule.

It remains available during the #21 migration only so existing local workflows do not break before the replacement has been proven through the real Cloudflare Access boundary.

What it exposes today

Resources:

every docs/*.md;
every tools/*.json;
AGENTS.md;
CLAUDE.md;
MissionStatement.md.

Tools:

run_checker — wraps tools/check-*.mjs;
register_repo — wraps tools/register-repo.mjs;
promote_to_lockup — wraps tools/promote-to-lockup.mjs.

There is no arbitrary-write tool.

Why it is being retired

Keeping the MCP permanently would create two blessed ways to obtain the same Family development context:

local sessions via MCP;
remote/cloud sessions via authenticated static HTTPS.

That produces environment-dependent guidance and another mechanism to maintain. The static API already serves the same canonical source files, works remotely, needs no process/container/Worker, and can now publish a generated manifest for resource discovery.

The MCP tools do not justify keeping the server either. An agent that is actually changing Amoleo-Family should work in this repo and run the canonical tools/*.mjs scripts directly.

Retirement gate

Do not delete the MCP merely because the replacement exists in source. Retire it only after:

/api/manifest.json and the raw resources are deployed;
local and cloud agent environments have both fetched them successfully through the real Access boundary;
sibling repo guidance has begun migrating to the static API;
tools/check-docs-pointer.mjs and related templates no longer require MCP-specific wording.

Until then, existing local registrations may continue to use it. New repo guidance should point at the static development-context API instead.

See docs/family-development-context-api.md for the target architecture and docs/family-docs-pointer.md for the sibling-repo migration rule.

Generated from docs/family-mcp-server.md. Edit there and re-run npm run build in docs-site-src/ — never hand-edit a page.