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

# MCP Quickstart

> Connect SAN to any MCP-compatible client.

## Choose an authentication method

SAN's MCP server authenticates with an API key. You can pass the key either as a query parameter in the server URL or as an `x-api-key` header.

* Use the **query parameter** URL when you're connecting from a consumer chat app or any MCP client that doesn't support custom headers.
* Use the **`x-api-key` header** when you're connecting from a developer tool whose config supports headers (Claude Desktop, Claude Code, custom agents, CI).

You'll need an API key first. Follow the [API Quickstart](/api-quickstart) to create one with a single click, no account required.

<Tabs>
  <Tab title="Connect by URL (recommended)">
    Any MCP client that lets you add a server by URL can connect to SAN, including consumer apps that don't support custom headers. Just append your API key as the `api_key` query parameter:

    ```text theme={null}
    https://playground.sanfoundation.com/mcp?api_key=sk_...
    ```

    In [claude.ai](https://claude.ai/settings/connectors), this is under **Settings > Connectors > Add custom connector** — paste the full URL there.

    <Warning>
      The URL contains your API key, so treat the entire URL as a secret. Anyone who has it can spend your balance. Don't share it, commit it to source control, or paste it anywhere public.
    </Warning>
  </Tab>

  <Tab title="API key header">
    If your MCP client's config supports HTTP headers, pass your key in the `x-api-key` header instead of the URL. For Claude Desktop, edit `claude_desktop_config.json`:

    ```json theme={null}
    {
      "mcpServers": {
        "san": {
          "url": "https://playground.sanfoundation.com/mcp",
          "headers": {
            "x-api-key": "sk_..."
          }
        }
      }
    }
    ```

    Restart your client and SAN's tools will appear alongside any others you've configured. Other clients use slightly different config formats, but the `url` and `x-api-key` header are the same.
  </Tab>
</Tabs>