Powerbi MCP Server

If you already use Powerbi, the powerbi mcp server is the piece that lets your assistant work with it directly. Power BI Modeling MCP Server - Node.js client package for installing and running the Power BI Modeling MCP server.

What the server does

The Power BI Modeling MCP Server implements the MCP specification to create a seamless connection between AI agents and Power BI semantic models. This project is in Public Preview and implementation may significantly change prior to our General Availability.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• connection_operations — Connect to Power BI Desktop or Fabric workspaces
• database_operations — Manage semantic models - connect, create, update, list databases, import/export TMDL folders, deploy to Fabric
• transaction_operations — Control database transactions (begin, commit, rollback, get status)
• model_operations — Work with the overall model (get, create, update, refresh, get stats, rename)
• table_operations — Manage tables (create, update, delete, get, list, refresh, rename)
• column_operations — Manage individual table columns (create, update, delete, get, list, rename)
• measure_operations — Manage individual DAX measures (create, update, delete, get, list, rename, move between tables)
• relationship_operations — Handle relationships between tables (create, update, delete, activate/deactivate, find)
• dax_query_operations — Execute and validate DAX queries against the model
• trace_operations — Perform trace operations on semantic model to capture and analyze Analysis Services events
• partition_operations — Manage table partitions (create, update, delete, refresh specific partitions)
• user_hierarchy_operations — Work with user-defined hierarchies (create, update, delete levels, reorder)

Credentials and setup notes

Configuration is passed through the environment: PBI_MODELING_MCP_ACCESS_TOKEN, AZURE_CLIENT_ID, AZURE_TENANT_ID, AZURE_CLIENT_SECRET, AZURE_CLIENT_CERTIFICATE_PATH, ACCESS_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Powerbi.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Powerbi's toolset — connection_operations, database_operations, transaction_operations and 11 more — is a fair guide to whether it matches your workflow. It is maintained by microsoft1es; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Powerbi's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.