mcp-powerBI
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POWERBI_TENANT | No | Power BI tenant (e.g., vnu.edu.vn) for service principal authentication. | |
| POWERBI_CLIENT_ID | No | App client ID for service principal authentication. | |
| POWERBI_ACCESS_TOKEN | No | Power BI access token for direct authentication. | |
| POWERBI_CLIENT_SECRET | No | Client secret value for service principal authentication. | |
| POWERBI_MODELING_MCP_ARGS | No | Arguments for the Modeling MCP command. Default: --start. | |
| POWERBI_MODELING_MCP_COMMAND | No | Path to the Microsoft Power BI Modeling MCP binary. Default: npx -y @microsoft/powerbi-modeling-mcp@latest. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auth_statusA | Show which Power BI authentication mode is configured without exposing tokens. |
| start_device_loginA | Start delegated user device-code login for Power BI REST API. Use only for one-time local setup; service principal is recommended for production. |
| complete_device_loginA | Poll Microsoft for the pending device-code login and cache the token when authorization is complete. |
| list_workspacesA | List all Fabric/Power BI workspaces visible to the authenticated account through the Power BI REST API. Use this first when the user does not provide a workspace name or id. |
| list_semantic_modelsA | List semantic models in My workspace or in a specific workspace by id. Use list_workspaces first to resolve workspace ids. If workspace discovery is not authenticated and the user did not name a workspace, ask the user which workspace to use. |
| get_catalogA | Return all visible workspaces and semantic models via Power BI REST API. This is the preferred tool for open-ended questions such as 'which model should I use?' or 'what workspaces can I access?'. |
| list_semantic_models_in_workspace_via_modeling_mcpA | Use Microsoft powerbi-modeling-mcp/XMLA auth to list semantic models inside a known workspace name. This is a fallback when REST workspace discovery auth is unavailable. The workspace name must be explicit; if it is missing, ask the user instead of guessing. |
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 7 tools
Most tools have distinct purposes, but 'get_catalog' overlaps with 'list_workspaces' and 'list_semantic_models' by combining their functionality. The descriptions help differentiate, but some confusion is possible.
All names use snake_case and mostly follow a verb_noun pattern. Minor deviations include 'auth_status' (abbreviation) and the very long 'list_semantic_models_in_workspace_via_modeling_mcp', but overall consistent.
7 tools is a reasonable number for a Power BI discovery-focused server. Each tool serves a clear role without excessive redundancy.
The tool set covers authentication and read-only discovery well, but lacks any create, update, delete, or execute operations. For a full Power BI management surface, this is notably incomplete.