Power BI Local MCP
Related Servers
Alternatives to Power BI Local MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables natural language interaction with Power BI Desktop via MCP, allowing DAX authoring, measure optimization, and model inspection.MIT
- AlicenseBqualityCmaintenanceEnables MCP-compatible AI clients to build and modify Power BI reports through natural language, including pages, visuals, themes, filters, and formatting using local PBIR files without REST API keys or the Power BI service.57MIT
- FlicenseAqualityCmaintenanceEnables natural-language interaction with Power BI REST API through MCP tools, allowing GenAI applications to access approved business intelligence capabilities and analytics.28-
- AlicenseBqualityDmaintenanceBuild Power BI reports with natural language through an MCP server that connects AI assistants to Power BI's PBIR file format for creating pages, visuals, themes, and filters locally.85721MIT
- AlicenseNot gradedqualityBmaintenanceEnables generating Power BI .pbit dashboards from CSV files or live SQL databases using plain-English prompts and optional reference-image layouts, with local-only processing and MCP tools for Claude Desktop.MIT
- AlicenseNot gradedqualityCmaintenanceEnables an AI assistant to build Power BI projects end to end: data modeling (tables, DAX measures, relationships, calculation groups, roles, field parameters) against an open Power BI Desktop via TOM/XMLA, and reports (pages, visuals, formatting, bookmarks, themes) as PBIR files in a .pbip project. Every visual is cross-checked against the real model before being written, so generated dashboards don't break on open.MIT
TDQS
Scored across 5 tools
Each tool targets a distinct phase: scaffolding a demo project, inspecting, adding visuals, editing layout, and validating. The only mild overlap is between create_retail_demo and create_dashboard, since both 'create' report content, but the descriptions make clear one builds a whole synthetic PBIP and the other extends an existing one.
All five tools follow a strict verb_noun snake_case pattern (create_retail_demo, inspect_project, create_dashboard, edit_layout, validate_report). No mixed conventions or vague one-word names.
Five tools is a tight, well-scoped set for a local PBIP manipulation server, and each tool maps to a distinct step in the workflow (scaffold, inspect, build, edit, validate). Nothing feels redundant or padded.
The surface covers a reasonable lifecycle (inspect -> create -> edit -> validate), but there are notable gaps: no way to create a blank/non-retail project, no visual deletion or generic visual creation, and no page-level operations. Agents needing anything beyond layout tweaks or the canned KPI dashboard will hit a dead end.