Contributing

MCP docs content lives in the website repo under mcp-docs/.

Structure

Section	Path	Audience
Use	use/	End users and agents — capabilities, tools, connection
Internals	internals/	Us and deep-divers — architecture, engine API, quality, deploy

When a capability ships:

1. Add or update a page under use/tools/ (generic MCP tool reference)
2. Add or update use/eips/eip-NNNN.md for every live website exploration — Runnable or Planned (human catalogue — prompts, twins; not demo bytecode). Runnable engine modules also update the live catalog in use/coverage.md.
3. Add or update use/forks/<id>.md when a named fork catalog row changes (generic hardfork runs — Amsterdam, Osaka, Prague).
4. Update use/coverage.md index and sidebar in .vitepress/config.ts
5. Update internals/execution-engine or internals/gateway as needed
6. Add a changelog entry on the affected page
7. Update public/llms.txt and public/llms-full.txt

use/ is the hosted product. Do not document local stdio, Cursor mcp.json, or self-host setup on user-facing pages. Build steps belong in GitHub READMEs and internals/ (development transport), not as a public early-access path.

Builder invariants for engine/gateway code: mcp-execution-engine/AGENTS.md, mcp-gateway/AGENTS.md.

See Quality for test and lint commands.

Changelog

Contributing Changelog

1. v0.62026-09-16Named-fork catalogue pages under use/forks/ when fork capability rows change.
2. v0.52026-09-02use/ documents the hosted product only — no self-host early access.
3. v0.42026-08-27EIP catalogue under use/eips/; link to engine/gateway AGENTS.md for builders.
4. v0.32026-07-20Contributing page under internals/.