# Claude Desktop

> Connect Claude Desktop to your Holistics workspace via MCP.

## Overview

Here's what you'll do to connect [Claude Desktop](https://claude.ai/download) to Holistics:

- **Turn on MCP Server**: A one-time step in your Holistics workspace, done by an admin. If it's already on, skip ahead.
- **Get your connection URL**: Choose the environment you want to work with:
  - **Reporting**: Published Holistics objects (those on the Reporting tab).
  - **Development**: Unpublished Holistics objects in your current AMQL project branch (those on the Development tab).
- **Choose your authentication method**:
  - **OAuth**: Logs in with your Holistics account (no key to create or manage).
  - **API key**: Uses a static key instead, useful for headless or scripted setups.
  - Learn more: [OAuth vs. API key - which should I use?](/docs/ai/mcp-server/faq#oauth-vs-api-key-which-should-i-use)

## Step 1: Turn on MCP Server

This is a one-time setup done by a workspace admin. Go to [AI Settings](/docs/ai/ai-settings) and enable both **[Holistics AI](/docs/ai/enable-ai)** and the **MCP Server**.

## Step 2: Get your connection URL

Your connection URL depends on your data center region and the Holistics environment you want your AI to work with.

Select your data region

<Tabs groupId="holistics-region" queryString className="tabs--button">
  <TabItem value="apac" label="APAC (secure.holistics.io)">
    Select your working environment
    <Tabs groupId="holistics-env" queryString className="tabs--button">
      <TabItem value="reporting" label="Reporting">
        Let your AI work with published Holistics objects — those on the Reporting tab.
        Get your connection url

        ```text
        https://mcp-apac.holistics.io/reporting/mcp
        ```

      </TabItem>
      <TabItem value="development" label="Development">
        Let your AI work with unpublished Holistics objects in your current AMQL project branch — those on the Development tab.
        Get your connection url

        ```text
        https://mcp-apac.holistics.io/development/mcp
        ```

      </TabItem>
    </Tabs>
  </TabItem>
  <TabItem value="us" label="US (us.holistics.io)">
    Select your working environment
    <Tabs groupId="holistics-env" queryString className="tabs--button">
      <TabItem value="reporting" label="Reporting">
        Let your AI work with published Holistics objects — those on the Reporting tab.
        Get your connection url

        ```text
        https://mcp-us.holistics.io/reporting/mcp
        ```

      </TabItem>
      <TabItem value="development" label="Development">
        Let your AI work with unpublished Holistics objects in your current AMQL project branch — those on the Development tab.
        Get your connection url

        ```text
        https://mcp-us.holistics.io/development/mcp
        ```

      </TabItem>
    </Tabs>
  </TabItem>
  <TabItem value="eu" label="EU (eu.holistics.io)">
    Select your working environment
    <Tabs groupId="holistics-env" queryString className="tabs--button">
      <TabItem value="reporting" label="Reporting">
        Let your AI work with published Holistics objects — those on the Reporting tab.
        Get your connection url

        ```text
        https://mcp-eu.holistics.io/reporting/mcp
        ```

      </TabItem>
      <TabItem value="development" label="Development">
        Let your AI work with unpublished Holistics objects in your current AMQL project branch — those on the Development tab.
        Get your connection url

        ```text
        https://mcp-eu.holistics.io/development/mcp
        ```

      </TabItem>
    </Tabs>
  </TabItem>
  <TabItem value="custom" label="Custom domain">
    Get your connection url

    :::note
    Please contact [support@holistics.io](mailto:support@holistics.io) for your MCP server address.
    :::

  </TabItem>
</Tabs>

<details>
<summary>URL format</summary>

```
https://mcp-<REGION>.holistics.io/<ENV>/mcp
```

* **`<REGION>`**: Choose based on your [data center](/docs/security-compliance/data-centers#how-do-i-know-which-data-center-im-on): `apac`, `eu`, or `us`
* **`<ENV>`**:
  * `reporting` (default): Let your AI work with **published** Holistics objects (i.e. objects on your Holistics **Reporting** tab)
  * `development`: Let your AI work with **unpublished** Holistics objects in your current AMQL project branch (i.e. objects on your Holistics **Development** tab)

</details>

## Step 3: Connect

Claude Desktop uses a local command config and supports either OAuth or API key.

1. Go to **Settings > Developer > Edit Config**.

   

2. Add Holistics to your config:

#### OAuth

- Use your connection URL from [Step 2](#step-2-get-your-connection-url) and replace `<MCP_SERVER_ADDRESS>`.

```json
{
  "mcpServers": {
    "holistics": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "<MCP_SERVER_ADDRESS>"
      ]
    }
  }
}
```

#### API key

- Use your connection URL from [Step 2](#step-2-get-your-connection-url) and replace `<MCP_SERVER_ADDRESS>`.
- Obtain your API key:

Find your key under **Account settings** in Holistics.

- Replace `<YOUR_HOLISTICS_API_KEY>` below with it.

```json
{
  "mcpServers": {
    "holistics": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "<MCP_SERVER_ADDRESS>",
        "--header", "X-Holistics-Key:<YOUR_HOLISTICS_API_KEY>"
      ]
    }
  }
}
```

3. Save and restart Claude Desktop.

## Need more help?

See the [MCP FAQ](/docs/ai/mcp-server/faq) for questions about permissions, data access, and security.