> ## 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.

# Share with your team

> Distribute the Nodal MCP endpoint to your whole team with a single .mcp.json file.

Sharing Nodal with your team is one file: a **`.mcp.json`** that points every teammate's agent at
your hosted endpoint. Commit it to a repo your team works in, and each person's agent picks up the
server automatically.

## Step 1 — Provision once (admin)

In the [Nodal admin](https://aiden.nodaldata.io):

1. **Subscribe** to activate your organization's endpoint.
2. **Add a read-only GitHub token** for your analytics-context repo.
3. *(Optional)* Add a read-only token for your **dbt project repo** to enable the lineage
   connector.

<Note>
  That's the entire access footprint — read-only GitHub. **No database connection is ever
  requested.** [Details →](/mcp/data-access)
</Note>

## Step 2 — Add the `.mcp.json` file

Drop this file at the root of a repo your team shares (or into each teammate's agent config):

```json .mcp.json theme={null}
{
  "mcpServers": {
    "nodal": {
      "type": "http",
      "url": "https://analyst.nodaldata.io/mcp"
    }
  }
}
```

That's the whole distribution mechanism — anyone whose agent reads this file gets the Nodal tools.

## Step 3 — Authenticate

The first time a teammate's agent calls the endpoint, it runs the standard **OAuth 2.0** flow: the
agent opens a browser, the teammate signs in, and a token is issued (scoped to your organization).
No API keys to copy around.

<Tip>
  Different agents read MCP config from slightly different places. `.mcp.json` at a repo root is the
  project-scoped convention for Claude Code; for other agents, add an HTTP MCP server with the URL
  `https://analyst.nodaldata.io/mcp` per that agent's MCP docs.
</Tip>

## Verify it worked

Ask a question your context covers. The teammate's agent should call the Nodal tools (for example
`get_business_context` or `search_corpus`) and return an answer grounded in your definitions. See
the [tool reference](/mcp/tools) for what's available.