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

# Manually Connect to the Domo Essentials MCP Server

export const BetaNote = ({generic = false}) => <Note>
    <strong>Note:</strong>{" "}
    {generic ? "" : "This feature is in beta. "}
    Beta Program participants can enable features{" "}
    <a href="https://embed.domo.com/embed/pages/DQ8Ek">here</a>. To join the
    Beta Program, fill out{" "}
    <a href="https://embed.domo.com/embed/pages/K8GMx">this form</a>. For beta
    questions or feedback, email{" "}
    <a href="mailto:beta.admin@domo.com">beta.admin@domo.com</a>.
  </Note>;

<BetaNote />

## Intro

This article explains how to manually connect to the Domo Essentials MCP Server using Claude Desktop, Claude Code, or VS Code.

***

## Prerequisites

Before connecting, ensure you have the following:

* **Node.js** version 21 or higher installed. Use [nvm](https://github.com/nvm-sh/nvm) to manage your Node.js version.
* A Domo **Access Token** with appropriate permissions. You can provision one at **Admin** > **Authentication** > **Access Tokens**, or request one from your MajorDomo. See [Manage Access Tokens](/docs/s/article/360042934494#manage-access-tokens) for instructions.
* A supported AI code editor (Claude Desktop, Claude Code, VS Code, Cursor, or another MCP-compatible client).

## Connect Claude Desktop

Claude Desktop does not natively support remote MCP servers, so you connect using `mcp-remote` — an NPM tool that bridges desktop AI clients to remote MCP servers.

### Step 1: Provision an Access Token

In your Domo instance, go to **Admin** > **Authentication** > **Access Tokens** and generate a token. See [Manage Access Tokens](/docs/s/article/360042934494#manage-access-tokens) for instructions.

<Frame>
  <img src="https://mintcdn.com/domoinc/m1c7CpONf40y0q2a/images/kb/DOMO-MCP-Server-Screenshot-2.png?fit=max&auto=format&n=m1c7CpONf40y0q2a&q=85&s=739ac8381fbd946a6ac3a17666066ded" alt="Access Tokens management page in Domo Admin settings" width="2210" height="172" data-path="images/kb/DOMO-MCP-Server-Screenshot-2.png" />
</Frame>

### Step 2: Install mcp-remote

Open a terminal and run:

```
npm install mcp-remote
```

### Step 3: Install Claude Desktop

Download and install [Claude Desktop](https://claude.ai/download).

<Frame>
  <img src="https://mintcdn.com/domoinc/m1c7CpONf40y0q2a/images/kb/DOMO-MCP-Server-Screenshot-3.png?fit=max&auto=format&n=m1c7CpONf40y0q2a&q=85&s=643bdc16fe91afc10a95f5bce56be31e" alt="Claude Desktop application download page" width="1196" height="1094" data-path="images/kb/DOMO-MCP-Server-Screenshot-3.png" />
</Frame>

### Step 4: Edit the Claude Desktop configuration

In Claude Desktop, go to **Settings** > **Developer** and select **Edit Config**.

<Frame>
  <img src="https://mintcdn.com/domoinc/m1c7CpONf40y0q2a/images/kb/DOMO-MCP-Server-Screenshot-4.png?fit=max&auto=format&n=m1c7CpONf40y0q2a&q=85&s=50a86eb189823517123c81f0ed2f88b2" alt="Claude Desktop Settings Developer tab showing Edit Config option" width="1196" height="1094" data-path="images/kb/DOMO-MCP-Server-Screenshot-4.png" />
</Frame>

This opens the configuration file located at:

```
/Users/<username>/Library/Application Support/Claude/claude_desktop_config.json
```

<Frame>
  <img src="https://mintcdn.com/domoinc/SG-4eT9d5tqwt_op/images/kb/DOMO-MCP-Server-Screenshot-5.png?fit=max&auto=format&n=SG-4eT9d5tqwt_op&q=85&s=ae9de8216c70c8db7d5c69d02d8c0084" alt="Claude Desktop configuration file open in a text editor" width="1196" height="1094" data-path="images/kb/DOMO-MCP-Server-Screenshot-5.png" />
</Frame>

### Step 5: Add the Domo MCP Server configuration

Paste the following into the configuration file, replacing `<DOMO_DOMAIN>` with your Domo instance domain and `<DOMO_ACCESS_TOKEN>` with your Access Token:

<Note>
  **Note:** If this is your first manual connection, paste the following right after the first opening brace `{`. If you have other manual connections, paste the contents of the `mcpServers` property (second example block).
</Note>

```json theme={"dark"}
  "mcpServers": {
    "domo-mcp-npx": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://<DOMO_DOMAIN>/api/ai/v1/assistant/mcp/toolkits/DOMO_BASIC_MCP",
        "--header",
        "X-DOMO-DEVELOPER-TOKEN:<DOMO_ACCESS_TOKEN>"
      ]
    }
  }
```

```json theme={"dark"}
    "domo-mcp-npx": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://<DOMO_DOMAIN>/api/ai/v1/assistant/mcp/toolkits/DOMO_BASIC_MCP",
        "--header",
        "X-DOMO-DEVELOPER-TOKEN:<DOMO_ACCESS_TOKEN>"
      ]
    }
```

### Step 6: Restart Claude Desktop

Quit and restart Claude Desktop for the configuration to take effect.

<Frame>
  <img src="https://mintcdn.com/domoinc/m1c7CpONf40y0q2a/images/kb/DOMO-MCP-Server-Screenshot-6.png?fit=max&auto=format&n=m1c7CpONf40y0q2a&q=85&s=d3874f8f0031af54db7ef204f241fbed" alt="Claude Desktop restart prompt" width="1196" height="1094" data-path="images/kb/DOMO-MCP-Server-Screenshot-6.png" />
</Frame>

### Step 7: Verify the connection

Go to **Settings** > **Connectors** and confirm the Domo MCP server is listed and connected.

<Note>
  **Note:** Connectors have moved to **Customize**. Head there to browse, connect, and manage them.
</Note>

<Frame>
  <img src="https://mintcdn.com/domoinc/m1c7CpONf40y0q2a/images/kb/DOMO-MCP-Server-Screenshot-7.png?fit=max&auto=format&n=m1c7CpONf40y0q2a&q=85&s=23e681460966d0edc5f7517cf13379f8" alt="Claude Desktop Customize panel showing the connected Domo MCP server" width="1196" height="1094" data-path="images/kb/DOMO-MCP-Server-Screenshot-7.png" />
</Frame>

Select the server to view its tool permissions. You should see the following tools listed:

* `DomoSqlQueryTool`
* `ExtendedThinkingTool`
* `FileSetQueryTool`
* `SearchTool`

<Frame>
  <img src="https://mintcdn.com/domoinc/m1c7CpONf40y0q2a/images/kb/DOMO-MCP-Server-Screenshot-8.png?fit=max&auto=format&n=m1c7CpONf40y0q2a&q=85&s=52f80eebd31aad5a1bc60747bd4e0425" alt="Domo MCP server tool permissions list in Claude Desktop" width="1196" height="1094" data-path="images/kb/DOMO-MCP-Server-Screenshot-8.png" />
</Frame>

To test the connection, try a prompt such as: "How many datasets do I have access to?"

<Frame>
  <img src="https://mintcdn.com/domoinc/m1c7CpONf40y0q2a/images/kb/DOMO-MCP-Server-Screenshot-9.png?fit=max&auto=format&n=m1c7CpONf40y0q2a&q=85&s=5335c4e5f01e845fb178ba75ef671aef" alt="Claude Desktop responding to a test query about Domo DataSets" width="1196" height="1094" data-path="images/kb/DOMO-MCP-Server-Screenshot-9.png" />
</Frame>

## Connect Claude Code

In Claude Code, run the following command from the root of your project. Replace `<DOMO_DOMAIN>` with your Domo instance domain and `<DOMO_ACCESS_TOKEN>` with your Access Token:

```bash theme={"dark"}
claude mcp add --transport http domo-mcp \
  https://<DOMO_DOMAIN>/api/ai/v1/assistant/mcp/toolkits/DOMO_BASIC_MCP \
  --header "X-DOMO-DEVELOPER-TOKEN: <DOMO_ACCESS_TOKEN>"
```

This adds the configuration to a `.mcp` file in the root of your project:

```json theme={"dark"}
{
  "mcpServers": {
    "domo-mcp": {
      "type": "http",
      "url": "https://<DOMO_DOMAIN>/api/ai/v1/assistant/mcp/toolkits/DOMO_BASIC_MCP",
      "headers": {
        "X-DOMO-DEVELOPER-TOKEN": "<DOMO_ACCESS_TOKEN>"
      }
    }
  }
}
```

## Connect VS Code

1. Open the Command Palette with **Cmd+Shift+P** (Mac) or **Ctrl+Shift+P** (Windows/Linux).

2. Choose your configuration scope:
   * For a **global (user) configuration** (recommended) available across all workspaces, search for and select **MCP: Open User Configuration**.
   * For a **workspace-specific configuration** (not recommended for security, as it may expose your credentials), search for and select **MCP: Open Workspace Folder MCP Configuration**. This creates or opens `.vscode/mcp.json`.
   * For a **WSL configuration**, search for and select **MCP: Open Remote User MCP Configuration**. This creates or opens `~/.vscode-server/data/User/mcp.json`.

3. Add the following entry for `domo-mcp` to the `servers` object and `domo-access-token` to the `inputs` array in the configuration file. Replace `<DOMO_DOMAIN>` with your Domo instance domain. You'll be prompted to enter your Access Token when you start the server:

   ```json theme={"dark"}
   {
     "servers": {
       "domo-mcp": {
         "url": "https://<DOMO_DOMAIN>/api/ai/v1/assistant/mcp/toolkits/DOMO_BASIC_MCP",
         "type": "http",
         "headers": {
           "X-DOMO-DEVELOPER-TOKEN": "${input:domo-access-token}"
         }
       }
     },
     "inputs": [
       {
         "id": "domo-access-token",
         "type": "promptString",
         "description": "Domo Access Token",
         "password": true
       }
     ]
   }
   ```

## Troubleshoot

Depending on your environment, you may need to make additional changes to the Claude Desktop configuration.

**Mac**

If `npx` cannot be found, add an `env` property to the `domo-mcp-npx` server entry in your configuration, replacing `<USER_PATH>` with your home directory path:

```json theme={"dark"}
"env": {
  "PATH": "<USER_PATH>/.nvm/versions/node/v22.21.1/bin:/usr/local/bin:/usr/bin:/bin"
}
```

**Windows**

If `npx` cannot be found, replace the `"command"` value in your configuration with the full path to the `npx` executable, for example:

```json theme={"dark"}
"command": "C:\\Program Files\\nodejs\\npx.cmd"
```

## FAQ

<AccordionGroup>
  <Accordion title="Which AI tools are compatible with the Domo MCP Server?">
    The Domo MCP Server works with any MCP-compatible AI client, including Claude
    Desktop, Claude Code, VS Code, Cursor, and ChatGPT.
  </Accordion>

  <Accordion title="What can I do after I'm connected?">
    After you're connected, you can query your Domo DataSets, query documents
    stored in Domo, and search across your Domo instance. Card and dashboard
    summarization are coming soon.
  </Accordion>

  <Accordion title="I connected successfully, but I get an error when I query data.">
    Your Domo account must have the following grants enabled: **Use AI Chat** and **Use AI Services**.
  </Accordion>
</AccordionGroup>
