MCP server for editing Power BI Report Builder paginated reports (RDL)
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
An MCP server for editing Power BI Report Builder paginated reports (.rdl)
through Claude (Desktop, CLI, or any MCP client). 140+ tools cover the gaps
that otherwise force hand-written XML: report creation, data sources and
datasets, calculated fields, dataset and tablix filters, groupings (row,
column, matrix), sorting, charts, headers and footers, body composition,
layout containers, positioning, styling, page setup, pagination, advanced
parameters, embedded images, interactivity (actions, tooltips, document
map), transactions, and validation.
The server speaks JSON-RPC 2.0 over stdio. It opens an .rdl from disk,
mutates it in place via lxml, validates structure, and writes atomically β a
failed save never leaves a half-written report or scrubs the original.
Pre-1.0. The tool surface β tool names, inputSchema, output shapes, error
semantics β is the contract. While on 0.x, MINOR releases may include a
small breaking change with a migration note in
CHANGELOG.md; after v1.0, breaking changes require MAJOR.
See CONTRIBUTING.md for the full bump rules
adapted from SemVer for an MCP tool surface.
Pin to a MINOR while on 0.x (e.g. pbirb-mcp~=0.1) if your prompts
depend on specific tool names or schemas.
The simplest path is uv + PyPI β no clone, no venv, no install step:
uvx fetches the package into a throwaway environment, runs the
pbirb-mcp console script, and exits. The MCP server speaks JSON-RPC
over stdio, so any MCP client (Claude Desktop, Claude Code, etc.) can
spawn it directly.
For local development against this codebase instead:
Verify the binary works:
You should see a single JSON-RPC response with protocolVersion,
capabilities.tools, and serverInfo.name = "pbirb-mcp".
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Restart Claude Desktop. The hammer icon should show pbirb and the 140+ tools
listed below.
To enable file logging, add an env block β but keep it platform-appropriate.
PBIRB_MCP_LOG_FILE takes an OS-native path: a Unix path like
/tmp/pbirb-mcp.log only works on macOS/Linux. On Windows use a Windows path
(e.g. %TEMP%\\pbirb-mcp.log). See Logging. When unset, logs go to
stderr, which Claude Desktop captures in its MCP debug pane on every platform.
For development against a local checkout, swap the args for
["--from", "/absolute/path/to/pbirb-mcp", "pbirb-mcp"] so uvx runs
your working tree instead of the published version.
Or add to .mcp.json at the workspace root:
Or install it as a Claude Code plugin β one command instead of editing
config by hand (it wires up the same uvx pbirb-mcp server for you):
In any chat, ask the model:
Open
~/path/to/some-report.rdland tell me what datasets and parameters it has.
The model should call describe_report, get_datasets, and get_parameters
and summarise the result. If it doesn't, your client probably hasn't loaded
the server β check the client's MCP debug log.
The recommended flow is read first, then edit by name. Every mutating
tool addresses elements by their RDL Name attribute (Tablix name,
Textbox name, ReportParameter name, DataSet name) β never by index.
Indices break across multi-step edits.
A typical session:
Open the resulting .rdl in Report Builder; the change is visible in the
designer and renders in Preview against the bound dataset.
143 tools, grouped by RDL concern. The highlights of each group are tabled
below; the authoritative, always-current list with full schemas is the
server's tools/list output, visible to the LLM at registration time. Every
tool takes a path argument (absolute path to the .rdl).
Most mutating tools also accept an optional transaction_id so a multi-step
edit batches into a single atomic save β see Transactions
and docs/TRANSACTIONS.md.
The "what's in this report?" tools. Always the first calls when planning a multi-step edit.
| Tool | Returns |
|---|---|
describe_report | Top-level inventory: data sources, datasets, parameters, tablixes, page setup |
get_datasets / get_dataset | Full DAX command text, fields, query parameters, dataset filters (all, or one by name) |
list_data_sources / get_data_source | Data source inventory; one source's connection details |
get_parameters | Report parameters with data type, prompt, and flags (multi-value, hidden, nullable, allow-blank) |
get_tablixes | Tablix layout: columns, row/column groups, sort expressions, filters, visibility |
list_tablix_filters / list_dataset_filters | Filters in document order with stable indices |
list_body_items / list_header_items / list_footer_items | Named report items in each region |
get_textbox / get_image / get_rectangle / get_chart | Full properties of a named report item |
list_embedded_images / get_embedded_image_data | Embedded image names + MIME types; base64 bytes of one |
get_expression_reference | Cheat-sheet of common RDL expression patterns (count_where, sum_where, iif_format helpers build these) |
| Tool | What it edits |
|---|---|
set_datasource_connection | Repoint a <DataSource> at a Power BI XMLA endpoint. DataProvider=SQL (the AS provider id). |
add_data_source / remove_data_source / rename_data_source | Manage <DataSource> elements |
update_dataset_query | Replace <DataSet>/<Query>/<CommandText> with a DAX expression |
add_query_parameter | Append <QueryParameter> (e.g. =Parameters!DateFrom.Value) |
update_query_parameter | Change the value expression of an existing query parameter |
remove_query_parameter | Drop a query parameter (and clean up empty <QueryParameters>) |
add_dataset_field / remove_dataset_field | Manage <Field> entries on a dataset |
add_calculated_field / remove_calculated_field | Manage <Value>-backed calculated fields |
refresh_dataset_fields | Re-derive the <Fields> list from the query's column metadata |
add_dataset_filter / remove_dataset_filter | Filters applied at the dataset level (vs. tablix) |
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/pbirb-mcp)<a href="https://allmcps.com/mcp/pbirb-mcp"><img src="https://allmcps.com/api/badge/pbirb-mcp?style=directory" alt="Pbirb MCP on AllMCPs" /></a>