> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nodaldata.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Nodal MCP overview

> A hosted, team-shared MCP endpoint that serves your context layer to everyone's agent.

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.

<Note>
  **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 →](/mcp/data-access)
</Note>

## The endpoint

|               |                                              |
| ------------- | -------------------------------------------- |
| **URL**       | `https://analyst.nodaldata.io/mcp`           |
| **Transport** | Streamable HTTP                              |
| **Auth**      | OAuth 2.0 (tokens issued by AWS Cognito)     |
| **Scope**     | Every request is scoped to your organization |

## How teammates connect

1. **An admin provisions once** in the [Nodal admin](https://aiden.nodaldata.io): 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](/mcp/share-with-your-team).
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.

<CardGroup cols={2}>
  <Card title="Share with your team" icon="users" href="/mcp/share-with-your-team">
    The `.mcp.json` file to hand out.
  </Card>

  <Card title="Tool reference" icon="wrench" href="/mcp/tools">
    Every tool the endpoint exposes.
  </Card>
</CardGroup>