Horizun PBI MCP

Build and fix Power BI reports by describing what you want. Ask in plain language; the server runs the DAX, edits the model, writes the report pages — and checks its own work afterwards.

v2.0.2 · 134 tools · Windows · Python 3.10+ · Claude Code, Codex, any MCP client

Install

No repository clone, manual DLL download or .mcp.json editing is required. Pick the line that matches you.

Claude Code

claude plugin marketplace add HorizunGroup/horizun-pbi-mcp
claude plugin install horizun-pbi-mcp@horizun

Codex

codex plugin marketplace add HorizunGroup/horizun-pbi-mcp

Then open /plugins, pick the Horizun marketplace and install horizun-pbi-mcp.

Or just ask the agent — easiest of all

Paste this into Claude Code or Codex and let it install itself:

Install Horizun PBI MCP from HorizunGroup/horizun-pbi-mcp. Complete the runtime setup, watch pbi_install_status until it reports ready, restart the session, and confirm the 134 pbi_* tools are available.

A brand-new Windows PC

One paste in PowerShell installs the prerequisites first — version-pinned and SHA-256 verified, no administrator rights. See docs/INSTALL.md.

Finishing up

The first setup downloads the runtime and takes a few minutes. Run pbi_install_status until it says ready, then restart your client once so the tools load. If anything looks stuck, docs/INSTALL.md covers repair and offline installs.

Related MCP server: Semantic Model MCP Server

Your first minute

1. Open Power BI Desktop with any report.

2. Ask: "List the Power BI models that are open and connect to the first one."

3. Ask: "Run a read-only DAX query that returns revenue by month for this year."

If step 2 answers, everything works.

Things worth asking for

Audit this PBIP project and explain the highest-risk issues before changing anything.

This measure returns blank for December. Find out why.

Create a report page from this specification, validate it, and show me the layout.

Document every measure in the model and export it to Excel.

What it provides

See the tool catalog for all 134 tools and their risk classifications.

Why it is safe to point at real work

• Local-first: Power BI Desktop communication stays on localhost.

• No telemetry, and the MCP server needs no account.

• Project writes stay inside the active project directory.

• Every project write makes a backup and is re-read to confirm it landed.

• Destructive tools require confirm=true.

• JSON writes are atomic; invalid JSON is never written over good JSON.

• Downloaded runtime components are version-pinned and SHA-256 verified.

• Logs go to stderr or files, so stdout stays a clean JSON-RPC channel.

Full guarantees and failure behavior: security model and recovery guide. Report vulnerabilities privately as described in SECURITY.md.

Requirements

• Windows 10 or 11.

• Python 3.10 or newer.

• Power BI Desktop — only for the live layer (DAX, refresh, capture, render checks).

• A .pbip project with PBIR enabled, for report-file authoring.

• Node.js 20+ only for the optional Microsoft PBIR validator.

Claude Code, Codex and Power BI Desktop are external programs; this project does not install them. Without Desktop the .pbip tools still work — the live tools do not.

Known limits

• Power BI does not expose pages or visuals through its live local endpoint, so those are edited in PBIR files while Desktop is safely closed.

• mode="both" is disabled for dual live/disk writes: Desktop being open and a PBIP project being safe to edit are mutually exclusive states.

• The server does not publish to or refresh the Power BI Service.

• Three PBIR schemas referenced by Power BI are not published by Microsoft; affected writes fail closed instead of guessing.

Documentation

Development

git clone https://github.com/HorizunGroup/horizun-pbi-mcp.git
cd horizun-pbi-mcp
python -m pip install -e .
python scripts/fetch_libs.py
python scripts/fetch_pbir_schemas.py
python scripts/doctor.py

Before opening a pull request:

python -m pytest -q
python scripts/doctor.py
python -m tests.contract_utils

The MCP contract is frozen and checked against tests/golden/tools_v1.json. Real .pbix, .pbip, credentials, DLLs, outputs and backups are never committed. See AGENTS.md for the repository invariants.

License

Apache License 2.0. See LICENSE and NOTICE.

MCP Registry

This package is the one published under the server name below. The registry reads this line from the README of the PyPI package to confirm that whoever publishes the metadata also owns the package, so it has to live here rather than in .mcp/server.json alone.

mcp-name: io.github.HorizunGroup/horizun-pbi-mcp