Dremio MCP

Installation

The Dremio MCP server can be deployed in two ways:

Remote / Streaming HTTP Deployment

For production deployments in Kubernetes environments, use the Helm chart:

📦 Helm Chart Documentation

Build Docker image

docker build -t dremio-mcp:0.1.0 .

Production deployment with OAuth (Recommended)

helm install my-dremio-mcp ./helm/dremio-mcp \ --set dremio.uri=https://dremio.example.com:9047

Local Installation (Desktop/Development)

The MCP server runs locally on the machine that runs the LLM frontend (eg Claude). The installation steps are simple:

1. Clone or download this repository. 2. Install the uv package manager (note that the MCP server requires python 3.11 or later) - If you install this for the first time, restart your terminal at the end of the install 3. Ensure that you have python installed by running the command below. It should show python 3.11 or later (If you don't have python installed, follow the instructions here OR simply run uv python install)

$ uv python find

```shell

Initial setup

There are two configurations necessary before the MCP server can be invoked.

1. The server config file: This will cover the details of connecting and communicating with Dremio
2. The LLM config file: This covers configuring the LLM desktop app (Claude for now) to make it aware of the MCP server

Quick start

The quickest way to do this setup is -

1. Create the dremio config file as outlined below and be prepared with these values

$ uv run dremio-mcp-server config create dremioai \
    --uri <dremio uri> \
    # the endpoint portion of the URL for your environment
    --pat <dremio pat> \
    # https://docs.dremio.com/current/security/authentication/personal-access-tokens/#using-a-pat
    # required for cloud: add your project ID if setting up for dremio cloud
    # --project-id <dremio project id>

Note: the uri is api endpoint associated with your environment:

• For Dremio cloud based in the US region (https://app.dremio.cloud) use https://api.dremio.cloud or use the short hand prod
• For Dremio cloud based in the EMEA region (https://app.eu.dremio.cloud) use https://api.eu.dremio.cloud or use the short hand prodemea
• For SW/K8S deployments use https://<coordinator‑host>:<9047 or custom port>

Note: For security purposes, if you don't want the PAT to leak into your shell history file, create a file with your PAT in it and give it as an argument to the dremio config.

Example:

$ uv run dremio-mcp-server config create dremioai \
    --uri <dremio uri> \
    --pat @/path/to/tokenfile \

1. Download and install Claude Desktop (Claude)

Note: Claude has system requirements, such as node.js, please validate your system requirements with Claude official documentation.

1. Create the Claude config file using

$ uv run dremio-mcp-server config create claude

1. Validate the config files using

$ uv run dremio-mcp-server config list --type claude

Default config file: '/Users/..../Library/Application Support/Claude/claude_desktop_config.json' (exists = True)
{
    'globalShortcut': '',
    'mcpServers': {
        'Dremio': {
            'command': '/opt/homebrew/Cellar/uv/0.6.14/bin/uv',
            'args': [
                'run',
                '--directory',
                '...../dremio-mcp',
                'dremio-mcp-server',
                'run'
            ]
        }
    }
}

$ uv run dremio-mcp-server config list --type dremioai
Default config file: /Users/..../.config/dremioai/config.yaml (exists = True)
dremio:
  enable_search: false
  pat: ....
  uri: ....
tools:
  server_mode: FOR_DATA_PATTERNS

You are done!. You can start Claude and start using the MCP server

Demo (Local install)

The rest of the documentation below provides details of the config files

---

has been enabled for your Dremio cluster (typically useful for SW installations)

#prometheus: #uri: ... #token: ... ```

Modes

There are 3 modes

1. FOR_DATA_PATTERNS - the normal mode where MCP server will allow LLM to look at tables and data to allow pattern discovery and other use cases
2. FOR_SELF - a mode which allows the MCP server to introspect Dremio system, including workload analysis and so on.
3. FOR_PROMETHEUS - a mode that allow MCP server to connect to your prometheus setup, if one exists, to enhance insights with Dremio related metrics

Multiple modes can be specified with separated by ,

Quick Start with Helm

```bash

Configuration details

MCP server config file

This file is located by default at $HOME/.config/dremioai/config.yaml but can be overriden using the --cfg option at runtime for dremio-mcp-server

Format

```yaml

and optionally the project_id if using with Dremio Cloud

dremio: uri: https://.... # the Dremio URI pat: "@~/ws/tokens/idl.token" # PAT can be put in a file and used here with @ prefix project_id: <string> Project ID required for Dremio Cloud enable_search: <bool> # Optional: Enable semantic search allow_dml: <bool> # Optional: Allow MCP Server to create views in Dremio tools: server_mode: FOR_DATA_PATTERNS # the serverm

Optionally the MCP server can also connect and use a prometheus configuration if it

The LLM (Claude) config file

Note: This is applicable only for local installs

To setup the Claude config file (refer to this as an example) edit the Claude desktop config file

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

And then add this section

{
  "globalShortcut": "",
  "mcpServers": {
    "Dremio": {
      "command": "uv",
      "args": [
        "run",
        "--directory", "<toplevel git directory>"
        "dremio-mcp-server",
        "run"
      ]
    }
  }
}

This will pickup the default location of MCP server config file. It can also be passed in the args section above as "--config-file", "<custom config file>" after run