Build on the decision substrate.
Cascadian is one MCP server in front of one Postgres. Connect your agent in one line, then call the tools behind every Cascadian answer: memory that cannot lie about the past, a causal graph humans own, knock-on simulation, and a ledger that scores every call. Start with the quickstart, or jump to a tool.
New here? Start with the overview.
Run a call right here.
Three canned calls, no key, no setup. Pick a scenario and run it — the response is the exact shape your agent gets back over MCP. Sample data, clearly labeled; the live server is gated behind the alpha.
Sandbox — canned, spec-true responses. No key, no server, no live data.
// Press RUN to call get_context_pack() in the sandbox.The substrate behind every call.
~27 tools. Four surfaces.
Every tool is callable over MCP — JSON-schema validated, workspace-scoped, audited, with an honest capability_status where it matters. A REST mirror is planned; the alpha is MCP-only. Each tool gets its own page with a diagram and a worked call.

