dbt MCP Server
OFFICIAL SERVERdbt Labs' server for running dbt commands, querying metrics and reading project metadata
Dremio's own MCP server for browsing lakehouse tables, running SQL and analysing cluster usage
Official · Dremio Python Local · stdio DatabasesData and analytics
29 popularity score ★ 53
Opens the app, which asks before it adds the server. Then replace each <NAME> in its settings with your value.
It needs DREMIOAI_DREMIO__URI, DREMIOAI_DREMIO__PAT. Replace each <NAME> with your value.
git clone https://github.com/dremio/dremio-mcp.git <REPO_DIR>
cd <REPO_DIR>
uv run dremio-mcp-server config create dremioai --uri <DREMIO_URI> --pat <DREMIO_PAT>claude mcp add dremio -e DREMIOAI_DREMIO__URI=<DREMIOAI_DREMIO__URI> -e DREMIOAI_DREMIO__PAT=<DREMIOAI_DREMIO__PAT> -- uv run --directory '<REPO_DIR>' dremio-mcp-server run{
"mcpServers": {
"dremio": {
"command": "uv",
"args": [
"run",
"--directory",
"<REPO_DIR>",
"dremio-mcp-server",
"run"
],
"env": {
"DREMIOAI_DREMIO__URI": "<DREMIOAI_DREMIO__URI>",
"DREMIOAI_DREMIO__PAT": "<DREMIOAI_DREMIO__PAT>"
}
}
}
}{
"mcpServers": {
"dremio": {
"command": "uv",
"args": [
"run",
"--directory",
"<REPO_DIR>",
"dremio-mcp-server",
"run"
],
"env": {
"DREMIOAI_DREMIO__URI": "<DREMIOAI_DREMIO__URI>",
"DREMIOAI_DREMIO__PAT": "<DREMIOAI_DREMIO__PAT>"
}
}
}
}{
"servers": {
"dremio": {
"type": "stdio",
"command": "uv",
"args": [
"run",
"--directory",
"<REPO_DIR>",
"dremio-mcp-server",
"run"
],
"env": {
"DREMIOAI_DREMIO__URI": "<DREMIOAI_DREMIO__URI>",
"DREMIOAI_DREMIO__PAT": "<DREMIOAI_DREMIO__PAT>"
}
}
}
}[mcp_servers.dremio]
command = "uv"
args = ["run", "--directory", "<REPO_DIR>", "dremio-mcp-server", "run"]
[mcp_servers.dremio.env]
DREMIOAI_DREMIO__URI = "<DREMIOAI_DREMIO__URI>"
DREMIOAI_DREMIO__PAT = "<DREMIOAI_DREMIO__PAT>"gemini mcp add --scope user -e DREMIOAI_DREMIO__URI=<DREMIOAI_DREMIO__URI> -e DREMIOAI_DREMIO__PAT=<DREMIOAI_DREMIO__PAT> dremio uv -- run --directory '<REPO_DIR>' dremio-mcp-server runDREMIOAI_DREMIO__URI |
Required: Dremio API endpoint: https://api.dremio.cloud (or prod), https://api.eu.dremio.cloud (prodemea), or your coordinator URL; can be set in config.yaml instead. |
|---|---|
DREMIOAI_DREMIO__PAT |
Required: Dremio personal access token; can also be set in config.yaml, or from a file with an @ prefix. |
DREMIOAI_TOOLS__SERVER_MODE |
Optional: Tool sets to enable: FOR_DATA_PATTERNS, FOR_SELF, FOR_PROMETHEUS, EXPERIMENTAL, comma-separated. |
JSON_LOGGING |
Optional: Set to 1 for structured JSON log output. |
Dremio MCP Server is a Python program from Dremio that connects an MCP client to a Dremio lakehouse, either Dremio Cloud (US or EMEA) or a self-managed Dremio cluster. Through it an assistant can look up table and view schemas, read table descriptions and lineage, search the catalog, and run SQL against the data.
What it offers depends on the mode set in its config file. FOR_DATA_PATTERNS is the everyday mode for exploring tables and finding patterns in data. FOR_SELF turns it on Dremio itself, with access to system tables and usage reports by engine or project. FOR_PROMETHEUS adds tools that query a Prometheus server watching the cluster. Modes can be combined, and a further set of tools passes calls through to extra tools that a Dremio server exposes, when that is enabled.
It runs in two ways. Locally, it is cloned from GitHub and started with uv as a stdio server beside a desktop client such as Claude Desktop, and a built-in config command writes both its own settings file and the Claude config. For teams, the repository ships a Dockerfile and a Helm chart that run it on Kubernetes as a streaming-HTTP service with OAuth sign-in. The repository says it is open source and not part of Dremio product support.
| Runtime | Python 3.11+ |
|---|
A Dremio Cloud project or a self-managed Dremio cluster, with a personal access token (plus the project ID for Dremio Cloud). Python 3.11 or later and the uv package manager, with a local clone of the repository. The remote option needs Docker, Kubernetes and Helm; Prometheus tools need a Prometheus endpoint.
SQL is limited to SELECT-style queries unless allow_dml is switched on; results are capped at a size the server sets, and an oversized result returns an error asking for a narrower query. Not published as a package: it runs from a cloned repository, and the Docker image is built yourself. The repository states it is not covered by Dremio product support. Some tools sit behind an experimental flag, and semantic-layer tools return nothing unless that feature is configured.
Suits Dremio users who want an assistant to explore their lakehouse catalog and query data with SQL, and Dremio administrators who want help reading system tables, job usage and Prometheus metrics. Read-only by default, so it fits analysis work; turn on allow_dml only when views or other changes are wanted. Teams can host it centrally on Kubernetes with OAuth instead of handing out personal tokens. Not useful without a Dremio deployment; for other warehouses pick a server made for that database.
RunSqlQueryGetSchemaOfTableGetDescriptionOfTableOrSchemaGetTableOrViewLineageGetUsefulSystemTableNamesSearchTableAndViewsBuildUsageReportGetRelevantMetricsGetMetricSchemaRunPromQLSearchMetricsGetTableRelationshipsDiscoverDynamicToolsCallDynamicTool