Skip to main content
A context repo is just Markdown and YAML, so you are never locked in. There are three ways to serve it:
  • Point your own agent at the files — clone the repo and read it locally. Great for a single analyst. Always free.
  • Build your own MCP server — self-host a small read-only MCP server against the raw repo, so your team’s agents can call it. Always free, no lock-in.
  • Launch on Nodal (hosted) — the low-cost, self-serve path when you want governed answers for the whole team without running infrastructure.
The format stays open and self-hosting is always free — the hosted endpoint is a convenience for team-scale distribution, not a lock on the format. The generated context repo carries its own copy of the spec, schemas, scripts, CI, and eval harness, so a teammate who clones it (and installs the plugin) can keep building and evaluating without a Nodal source checkout — and the hosted MCP serves that same repo, not your data, if you later opt in. For running Nodal in your own cloud/VPC (data-residency or security requirements), contact sales at info@nodaldata.io.