Wren MCP Server

Wren MCP server exists for a simple reason — assistants are far more useful when they can act on Wren directly instead of describing what you should do. Wren Engine CLI and Python SDK — semantic SQL layer for 20+ data sources.

What you get

Generative BI (GenBI) is business intelligence produced by AI agents: instead of manually building charts, an agent generates governed SQL, deploys a dashboard, and shares it — grounded in an AI context layer so the output is trustworthy, not just plausible. Wren AI is the open-source GenBI engine.

• Generative BI, end to end. — Wren does governed text-to-SQL — and goes beyond it: generate the answer, deploy the dashboard, share the URL, all driven by the agents you already use
• Knowledge management built in. — Business meaning, approved definitions, and proven examples are captured as a reviewable, version-controlled semantic layer (MDL), not buried in prompts
• Open by default. — Open-sourced core, SDK, and skills under the Apache-2.0 license
• Correctness as primitives. — Rich schema retrieval, dry-plan validation, structured errors with hints, value profiling, eval runner. The agent orchestrates; the trace lives in its reasoning
• Sits on top of your existing stack. — Warehouse, transformation pipelines, your existing semantic layer. Not another tool to maintain

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Wren is connected, these are the calls the assistant has available:

• Engine — Apache DataFusion based, 22+ data sources (BigQuery, Snowflake, PostgreSQL, ClickHouse, Amazon Redshift, Databricks, DuckDB, and more)
• End-to — end correctness primitives**: value profiling, rich retrieval, structured errors, golden eval runner
• Agent — native distribution**: first-class SDKs across major agent frameworks; see GitHub Discussions for
• Row — and column-level security (RLS / CLS)** and access control with users & groups

Configuration and credentials

You will need one environment variable: HF_ENDPOINT. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the wren mcp server does with a few real requests.

Choosing this one

This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Wren's toolset — Engine, End-to, Agent and 1 more — is a fair guide to whether it matches your workflow.

This entry was verified against Wren's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.