MCP server for editing Power BI PBIP report visualisations
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"powerbi-report-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# powerbi-report-mcp An [MCP](https://modelcontextprotocol.io) server for reading and editing the **report/visual layer of Power BI PBIP projects** — pages, visuals, field bindings, formatting, and themes — directly on disk, so AI assistants can build and restyle reports alongside you. It pairs with Microsoft's official [powerbi-modeling-mcp](https://www.npmjs.com/package/@microsoft/powerbi-modeling-mcp) (semantic model: tables, measures, relationships); this server deliberately never touches the semantic model. ## Features - **37 tools** covering connections, pages, visuals, field wells, format patching, themes, report settings, and style profiles. - **Implicit active report** — `connection_name` is optional on every tool; the most recently opened/used report is the default target. - **Git-style undo** — every edit is snapshotted per connection; `undo()` rolls back one step at a time (no redo), and `list_history()` shows the undo stack. - **Atomic writes** — files are written via temp-file rename so Power BI Desktop never sees a half-written JSON file. - **Schema-validated models** — Pydantic models mirror Microsoft's published PBIP JSON schemas, with a discriminated union per visual family. - **Style profiles** — capture fonts, colours, borders, and canvas size in a reusable JSON profile and distil it into a report, page, or single visual with `apply_style`; only the parts relevant to the scope are applied. - **Extension visual types** — register custom/AppSource visuals at runtime with the `register_visual_extension` tool; usable immediately, no restart. - **stdio and HTTP transports** — spawned per client (stdio, default) or one instance serving many clients via `--transport http`, with each client in its own isolated session. ## Quick start Requires [uv](https://docs.astral.sh/uv/) (Python 3.12+ is fetched automatically). Two officially supported ways to run it: **Usage — PyPI, stdio** (recommended for normal use): ```json { "po…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.