
SQL and semantic layer for your lakehouse data
Visit WebsiteFreemiumVisit Website
Tracked since2026
0 reviews trackedWhat is Dremio MCP?
Dremio is a lakehouse query engine that puts a SQL and semantic layer over data sitting in object storage and external sources. The official MCP server connects an AI client to a Dremio Cloud or Dremio Software deployment so an agent can find the right dataset and query it, instead of depending on a person to navigate the catalog and hand over a table path first.
The server exposes catalog discovery, so an agent can walk sources, spaces, folders, tables, and views and read their column schemas and types. Semantic search runs over dataset names, descriptions, and wiki documentation, which is how an agent locates the correct table when it does not know where the data lives. SQL execution submits a query to the Dremio engine and returns job status plus structured result rows, and job metadata explains how a query ran, which matters when an assistant needs to say why a result was slow or which reflection served it.
Connections use a personal access token, so the agent sees only what that user is entitled to under Dremio access policies, including row and column level rules. It targets analysts and data engineers who want an assistant to answer ad hoc questions over the lakehouse, and teams building agents that need governed SQL access to a semantic layer rather than a raw warehouse credential.
Key Features
Walk the catalog of sources, spaces, folders, tables and views with column schemasSemantic search over dataset names, descriptions and wiki documentationRun SQL against the Dremio engine and return structured result rowsTrack job status and read job metadata to explain query behaviorWorks against both Dremio Cloud and Dremio Software deploymentsPersonal access token auth that honors row and column level access policies
Pricing
Freemium
Dremio MCP offers a generous free tier with optional paid upgrades for advanced features.
Reviews

$99Free with your review
Write a reviewReview Dremio MCP, get a free AI guide
Share your experience and we will send you Improve Your Thinking Patterns Using ChatGPT, free.
Best Dremio MCP Alternatives
Top alternatives based on features, pricing, and user needs.
Still deciding?
Most buyers shortlist 2 or 3 tools before committing. Pull a side-by-side comparison or browse the full alternatives shortlist below.
Explore More
Dremio MCP FAQ
How does Dremio MCP help an AI agent find the right dataset without a human guiding it?
Dremio MCP exposes catalog discovery so an agent can walk sources, spaces, folders, tables, and views and read their column schemas and types. It also runs semantic search over dataset names, descriptions, and wiki documentation, which lets the agent locate the correct table even when it does not know where the data lives. This removes the need for a person to navigate the catalog and hand over a table path first.
How does Dremio MCP compare to Trino for governed SQL access?
Unlike Trino, which typically requires a raw warehouse credential and manual catalog navigation, Dremio MCP connects an AI client to a Dremio Cloud or Dremio Software deployment using a personal access token. This means the agent sees only what that user is entitled to under Dremio access policies, including row and column level rules, providing a governed semantic layer over the lakehouse. Trino does not inherently provide that same level of integrated semantic layer and access policy enforcement.
What are the main limitations or trade-offs of using Dremio MCP?
Dremio MCP requires a Dremio Cloud or Dremio Software deployment to connect to, so it does not work standalone against object storage or external sources without that engine. The agent's data visibility is strictly limited by the personal access token's user permissions, which means it cannot access datasets the user cannot see. Additionally, SQL execution depends on the Dremio engine's performance and configuration, so slow queries may still return job metadata explaining why, but the underlying speed is not controlled by the MCP server.
Which teams or users benefit most from adopting Dremio MCP?
Dremio MCP targets analysts and data engineers who want an assistant to answer ad hoc questions over the lakehouse. It also fits teams building agents that need governed SQL access to a semantic layer rather than a raw warehouse credential, ensuring compliance with existing access policies.
How is Dremio MCP priced?
Dremio MCP is available on a free tier, with paid plans for more usage and features. The free tier allows basic access, while paid plans scale with increased query volume and additional capabilities.
Can Dremio MCP explain why a query was slow or which reflection served it?
Yes, Dremio MCP returns job metadata that explains how a query ran, which matters when an assistant needs to say why a result was slow or which reflection served it. This metadata is part of the SQL execution response, providing structured insight into query performance.
Does Dremio MCP support row and column level security for AI agents?
Yes, Dremio MCP uses a personal access token for connections, so the agent sees only what that user is entitled to under Dremio access policies, including row and column level rules. This ensures that even when an AI agent queries data, it respects the same security boundaries as the human user.
What kind of data can an agent discover and query through Dremio MCP?
An agent can discover sources, spaces, folders, tables, and views, and read their column schemas and types. It can also run semantic search over dataset names, descriptions, and wiki documentation to find the right table. Once found, the agent can submit SQL queries to the Dremio engine and receive structured result rows plus job status.
Source: docs.dremio.com