BI Portal Report Builder MCP Server
Related Servers
Alternatives to BI Portal Report Builder MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for managing Microsoft Fabric Reports with lifecycle management, filtering, and content manipulation.8-
- AlicenseNot gradedqualityAmaintenanceMCP server for creating, editing, and evaluating Power BI (.pbix/.pbit) files without Power BI Desktop. Supports 101 tools including report creation, data sources, DAX measures, and file manipulation.5,681 PyPI21MIT
- FlicenseAqualityDmaintenanceAn MCP server that connects Claude and other MCP clients to Microsoft Power BI via its REST API using a Service Principal, enabling natural language queries to list workspaces, run DAX queries, refresh datasets, and explore reports.7-
- AlicenseNot gradedqualityDmaintenanceA self-hosted MCP server that proxies MCP clients to Power BI, using your own Entra tenant and Azure subscription. It enables DAX queries, workspace listing, and dataset management while preserving user-specific row-level security.2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for building and inspecting Power BI report visuals by editing PBIR files on disk, enabling page, chart, slicer, and layout management.MIT
- AlicenseAqualityCmaintenanceMCP server for Oracle Fusion BI Publisher that lets AI agents run queries, reports, and manage catalog objects via a secure, scoped interface.5MIT
TDQS
Scored across 8 tools
Each tool occupies a distinct role in the dataset-query-draft-submit-view pipeline. The two view tools are clearly separated by dashboard_kind, and list_datasets vs run_explore_query are unambiguous as metadata listing vs live querying.
All tool names follow a consistent lowercase snake_case verb-first pattern (list_, run_, create_, update_, get_, submit_, view_). The compound noun suffixes for the two dashboard viewers are descriptive and predictable.
Eight tools cover the core report-builder workflow without redundancy or bloat. Each tool maps to a meaningful step in the process, making the set well-scoped for its domain.
The core workflow is covered: discover datasets, preview queries, create/update/fetch/submit reports, and view saved results. However, there is no list_reports tool to enumerate existing drafts or reports, and no delete/discard operation, which leaves tangible lifecycle gaps.