-
Notifications
You must be signed in to change notification settings - Fork 1
How to share a snapshot or serve over HTTP
Arun Soman edited this page Aug 31, 2026
·
1 revision
cie export-html . --out snapshot.htmlOpen it via file:// — single file (~224K on a 110-file repo),
sections: Overview / Task & test chains / Atomic tasks / Orphans (no
test, no contract) / Indexed files. This is the scene-05 beat of the
README demo.
cie-mcp /path/to/project --backend embedded --policy inspector \
--transport streamable-http --host 127.0.0.1 --port 8000Loopback by default — binding wider turns cie into a network service behind the ToolPolicy boundary (see Security). The same policy filters registration on every transport: a read-only caller never sees write tools.
POST /tools/{tool} per request — the forge/CI path. Neo4j mode
today; embedded-over-HTTP is not claimed (see
storage how-to).
If code and this wiki disagree, the code wins — then this wiki gets a PR. Evidence lives in the repo, not here.
Start
How-tos
- Install & serve to your MCP client
- Choose your storage backend
- Run the Neo4j team mode
- Index & keep it fresh
- Ask impact questions
- Task & QA layer
- Semantic search
- Snapshot or serve HTTP
- Policies & the write boundary
- Troubleshoot
Reference
- Extraction pipeline
- Data model
- Tool reference
- Benchmarks
- Security & determinism
- Two tiers · Project layout · Docs index
Contribute