MCP server for Power BI — workspace management, dataset operations, report export, PBIX local analysis
40 tools with consistent naming (verb_noun pattern) and descriptions present. However, descriptions are often terse (many under 100 chars) and lack LLM-optimized guidance on WHEN to use each tool. Parameter descriptions are present but minimal. Output schemas are not documented, LLMs cannot predict return structure. Error handling is generic (safeTool wrapper) with no recovery guidance. No tool annotations (readOnlyHint/destructiveHint). Composition is sound (single responsibility per tool), but many tools lack context about dependencies and chaining.
Clone a report (optionally to a different workspace/dataset)
Download a completed report export to a local file
Export a report to PDF, PPTX, or PNG. Initiates async export and returns export ID. Use get_export_status to check progress.
Export a report to file (PDF/PNG/PPTX) and download it in a single step. Handles the full export lifecycle: trigger → poll → download.
Get Power BI activity events (audit log) for a specific date. Requires admin permissions.
Get workloads configured on a capacity (typically admin-only)
Output schemas not documented. LLMs cannot predict return structure (fields, types, pagination). Forces agents to guess at response shape and risks parsing failures.
Descriptions are terse (many 30-70 chars) and lack LLM-optimized guidance. Missing WHEN to use each tool, dependencies, and prerequisites. Baseline is 194 chars; most tools are 50% shorter.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). LLMs cannot distinguish safe reads from destructive writes without explicit hints. All 40 tools lack this metadata.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | <=2025-11-25 | v2 |
List all tiles on a dashboard
Get details of a specific dataflow
Get data sources used by a dataflow
Get details of a specific dataset
Get data sources used by a dataset
Get parameters of a dataset
Get refresh history of a dataset
Get the refresh schedule for a dataset
Get tables in a Power BI push dataset (shows table schema and column definitions)
Check the status of a report export
List data sources configured on a gateway
Get details of a specific report
List all pages of a report
Get details of a specific workspace by ID
List users and their roles in a workspace
List all published Power BI apps
List all available Power BI capacities
List all dashboards in a workspace
List all dataflows in a workspace
List all datasets in a workspace
List all on-premises data gateways accessible to the user
List all reports in a workspace
List all Power BI workspaces accessible to the service principal
Analyze a local .pbix file — shows file structure, entries, and overview info. Works without Azure credentials.
Analyzuj PBIX soubor a vygeneruj intranetový prompt pro sekce Business popis, Technický popis, Filtry a Míry (bez tabulek).
Discover running local Power BI Desktop semantic model instances (Windows).
Extract semantic model metadata (tables, columns, measures, relationships, partitions) from running Power BI Desktop local model (Windows).
Extract report layout from a .pbix file — shows pages, visual count, and visual types
Extract Power Query (M) code from a .pbix file — shows all data transformation queries
Rebind a report to a different dataset
Admin API: scan workspace metadata (datasets, reports, dashboards). Requires admin permissions.
Trigger an on-demand refresh of a dataflow
Trigger an on-demand refresh of a dataset (Pro: max 8/day on shared capacity)
Update parameter values of a dataset
Error handling is generic (safeTool wrapper). No recovery guidance, categorization (retryable vs fatal), or actionable error messages. Agents cannot self-correct on failures.
Tool composition lacks chaining metadata. E.g., export_report returns exportId, but no hint that get_export_status and download_export follow. Agents must infer multi-step workflows.