Dremio MCP server
About
Integrate Large Language Models (LLMs) with the Dremio data lakehouse platform.
Details
- License
- Apache-2.0
Explore
- ✅ OAuth + External Token Provider authentication (recommended for production)
- ✅ Streaming HTTP mode for web-based deployments
- ✅ Horizontal Pod Autoscaling for scalability
- ✅ Prometheus metrics integration
- ✅ Ingress support with TLS/SSL
- ✅ Security best practices (non-root, read-only filesystem)
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Dremio MCP serverCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
The Dremio MCP server can be deployed in two ways:
For production deployments in Kubernetes environments, use the Helm chart:
helm install my-dremio-mcp ./helm/dremio-mcp \
--set dremio.uri=https://dremio.example.com:9047
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
4. Do a sanity check by running the command and validating the output as shown below.
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
--pat <dremio pat> \
The rest of the documentation below provides details of the config files
---
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
#prometheus:
#uri: ...
#token: ...
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`Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"dremio mcp server": {
"dremio-mcp": {
"command": "docker",
"args": [
"build",
"-t",
"dremio-mcp:0.1.0",
"."
]
}
}
}
}McpServers
{
"dremio-mcp": {
"command": "docker",
"args": [
"build",
"-t",
"dremio-mcp:0.1.0",
"."
]
}
}Table of Contents
- Introduction
- Installation
- Initial setup
- Quick start
- Demo
- Configuration details
- MCP server config file
- Format
- Modes
- The LLM (Claude) config file
- Logging
- Log File Locations
- Log Features
- Enabling File Logging
- Further Documentation
- Additional Information
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
