Skip to main content
A context repo is just Markdown and YAML, so a single analyst can point their own agent at the files and get governed answers for free. That works for one person on one machine. To put the same context in front of your whole team — so a non-technical business user asks a question in their own agent and gets the answer the analyst would give — connect over the hosted Nodal MCP endpoint. It serves your context layer (and the query hub it grows into) as tools any agent can call: it retrieves the right definitions and canonical queries for a question and returns a governed answer grounded in verified context.
Nodal never needs access to your database. The endpoint serves your context repo, not your data. Warehouse SQL still runs through your own read-only warehouse connector. See exactly what we access →

​
The endpoint

URLhttps://analyst.nodaldata.io/mcp
TransportStreamable HTTP
AuthOAuth 2.0 (tokens issued by AWS Cognito)
ScopeEvery request is scoped to your organization

​
How teammates connect

  1. An admin provisions once in the Nodal admin: subscribe, then paste a read-only GitHub token for your context repo (and, optionally, your dbt repo).
  2. Each teammate adds the endpoint to their own agent via a .mcp.json file.
  3. They authenticate the first time through the standard OAuth flow — their agent opens a browser, they sign in, done.

​
What you get

  • Governed answers grounded in the analyst-curated context, for anyone on the team.
  • One place to update. Change a definition in the context repo; every agent picks it up.
  • An optional lineage connector that exposes your dbt/warehouse lineage, so the agent can check how a metric is computed, not just what it means.

Share with your team

The .mcp.json file to hand out.

Tool reference

Every tool the endpoint exposes.