Power BI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workspacesA | List all Power BI workspaces (groups) accessible to the caller. |
| list_datasetsA | List datasets, optionally scoped to a workspace (group) ID. |
| list_reportsB | List reports, optionally scoped to a workspace (group) ID. |
| list_dashboardsA | List dashboards, optionally scoped to a workspace (group) ID. |
| refresh_datasetB | Trigger a dataset refresh. |
| get_dataset_refresh_historyB | Return the refresh history entries for a dataset (most recent first). |
| execute_dax_queryB | Execute a DAX query against a dataset and return tabular results. |
| export_reportB | Start an export job for a report. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct resource or action: workspaces, datasets, reports, dashboards, dataset refresh, refresh history, DAX query, and report export. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (e.g., list_workspaces, refresh_dataset, execute_dax_query). The style is uniform and predictable.
Eight tools is a well-scoped set for a Power BI server focused on listing resources and performing common actions like refresh, query, and export. No redundant tools.
The surface covers listing and key actions (refresh, query, export), but lacks get-by-id operations and any create/update/delete tools. This is a notable gap for full lifecycle management, though the server appears oriented toward read and operational tasks.