MCP overview
DRE MCP connects an AI client to reviewed reporting logic and documented data through the Model Context Protocol. The agent can find and run an exposed report, refine its saved result, or explore allowed tables. Each result identifies its origin.
The current companion is dre-mcp 0.1.0-rc.1, a personal-mode release candidate requiring DRE 0.4.1 or later. It runs locally over stdio and uses your existing DRE connections. MCP is separately licensed; DRE core remains open source under GPL-3.0.
Start here
Section titled “Start here”- Install and connect: install the companion, review its licence, validate the project and configure a client.
- Configuration and scope: decide which reports and tables the agent can use.
- Tools and provenance: understand verified, derived and exploratory results.
- AI-ready reports: describe business meaning, inputs and example questions.
A complete MCP example project includes sources, reviewed SQL, typed inputs and optional configuration. Exposure starts disabled for owner review. The recorded MCP demo shows report execution, saved-result refinement and exploratory SQL.
Three kinds of answer
Section titled “Three kinds of answer”| Result | Where the numbers come from | What to review |
|---|---|---|
| Verified report | An explicitly exposed report’s reviewed SQL | Inputs, period, compiled SQL and the report’s business scope |
| Derived from verified result | Structured operations over a saved report result, using DRE’s DuckDB plugin | The source run and the filters, sorting or aggregation applied |
| Exploratory (unverified) | A new structured query over allowed tables | The rendered SQL, joins, assumptions and underlying data |
“Verified” identifies the reviewed report path. It does not guarantee that the business logic or an agent’s interpretation is correct. Report relationships and upstream comments provide context; they do not verify a new query.
How it fits your stack
Section titled “How it fits your stack”DRE and its installed plugins handle connections and query execution. The MCP companion uses DRE’s CLI and manifest; it embeds no database engine or database driver. Saved-result refinement requires the DuckDB plugin, including when the original report reads from another database.
Table and column comments come from your upstream pipeline. A well-documented dbt project or another pipeline helps; DRE adds report purpose, inputs and reviewed SQL to that context.
Current scope
Section titled “Current scope”- Local stdio transport, using the current user’s DRE connections.
- Live catalog support for DuckDB, PostgreSQL and Databricks.
- Report-related tables exposed by default when their report is exposed; extra tables and schemas require explicit configuration.
- Structured exploration on a single connection. Cross-connection joins and arbitrary model-authored SQL are outside this RC.
- Compatible MCP Apps hosts can display result cards and downloads. Other clients receive structured results and resource links; test your chosen client’s support.
Team transport, authentication and a hosted service are outside this RC. See licensing for the companion’s early-access terms, or contact us about preview access.