← Explore all mcp servers

DATA AND ANALYTICS / Microsoft

Power BI Authoring MCP Server

Local stdio server that queries and edits Power BI semantic models in Power BI Desktop, Fabric workspaces or PBIP folders. It writes by default; --readonly prevents write operations.

“It cannot modify other types of Power BI metadata, such as report pages or semantic model elements like diagram layouts.”

01 / THE REASONING

Why this made the selection.

  • The README's settings table documents --readonly, a safe mode that prevents any write operations to the semantic model, and says the default --readwrite asks for confirmation before applying an edit, once per database.
  • The README's tools table lists 21 tools by name (its text also describes an accept_eula tool) and documents interactive or service-principal authentication and a host allowlist (PBI_MODELING_MCP_ALLOWED_CONNECTION_HOSTS) for non-Power BI XMLA endpoints.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • README.md at 2b25defb975169ffb573195cc0ff8006835b8a6e: installation, EULA acceptance, tools, prompts, settings, limitations, licence and data-privacy sections
  • LICENSE at the same commit: MIT, Copyright (c) Microsoft Corporation
  • EULA.txt at the same commit: Microsoft Software License Terms, scope of licence
  • Repository root listing at the same commit: no package.json and no server source

Our findings

  • --start is required to start the MCP server.
  • --readonly is documented; default --readwrite includes a confirmation prompt once per database.
  • npm tooling blocks other calls until explicit EULA acceptance. In an interactive session the agent can call accept_eula after the user authorizes it, and the acceptance is saved locally.
  • README states semantic-model Write permission is required; the read-only switch does not establish a weaker account permission requirement.
  • README and LICENSE disagree: LICENSE is MIT, while the README says use of the software is subject to EULA.txt, which forbids distributing the software. This record therefore sets redistribution to false; it previously said MIT with redistribution.
  • The README lists 21 tools: connection, database, transaction, model, table, column, measure, relationship, dax_query, trace, partition, user_hierarchy, calculation_group, security_role, perspective, named_expression, function, culture, object_translation, calendar and query_group operations.
  • Authentication is --authmode interactive (default) or serviceprincipal, using AZURE_CLIENT_ID, AZURE_TENANT_ID and a client secret or certificate. The README says the server sends access tokens to the hosts it connects to.
  • The repository contains no package.json or source, so no implementation language is recorded; the previous JavaScript entry was not supported by a file. The README distributes the server as the npm package and as powerbi-modeling-mcp.exe inside a VSIX.
  • configExample is the README's npx block at this commit, which has no client wrapper key. The README gives no one-line shell command, so install.command is null; the previous command and configExample added --readonly, which the README block does not contain.
  • Health on 2026-10-13: repository not archived, default-branch HEAD was this commit, GitHub reports MIT.

Not established by this review

  • The pinned documentation and selected source files were reviewed; the external server was not executed by this review.
  • No authenticated service requests, account mutations, tenant access controls, or end-to-end MCP client setup were tested.
  • A repository revision does not pin an unversioned or @latest registry package; resolved package provenance and runtime permission enforcement remain unverified.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. The README gives no one-line shell command. Add its npx block (args -y, @microsoft/powerbi-modeling-mcp@latest, --start) to the client, or install the VS Code extension.
  2. Add --readonly to args for inspection only; the README documents it as the mode that prevents any write operations.
  3. Review EULA.txt and accept it through the server only if you agree.
  4. Connect to the intended Desktop file, Fabric workspace or PBIP folder with Write permission on the model.

Before you start

  • Node.js
  • Explicit acceptance of the Power BI Authoring MCP Server EULA
  • Write permission on the semantic model

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "powerbi-authoring-local": {
    "type": "stdio",
    "command": "npx",
    "args": [
      "-y",
      "@microsoft/powerbi-modeling-mcp@latest",
      "--start"
    ]
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. Server documentation ↗Checked

    https://github.com/microsoft/powerbi-modeling-mcp/blob/2b25defb975169ffb573195cc0ff8006835b8a6e/README.md

    Supports: upstreamDescription, configExample, tools, settings, limitations, access, transports

  2. https://github.com/microsoft/powerbi-modeling-mcp/blob/2b25defb975169ffb573195cc0ff8006835b8a6e/EULA.txt

    Supports: license, no distribution of the software

  3. Repository licence ↗Checked

    https://github.com/microsoft/powerbi-modeling-mcp/blob/2b25defb975169ffb573195cc0ff8006835b8a6e/LICENSE

    Supports: MIT text for the repository

Evidence & Ask