Power BI Analyst MCP

io.github.mbrummerstedtPublished by GitHub account mbrummerstedtv0.1.1Updated Oct 24, 2026

Browse Power BI workspaces, run DAX queries, and page through large results.

VerifiedSTDIODesktop onlyDatabasesData & Analytics

Overview

AI-generated overview

Lets an assistant browse Power BI workspaces and run DAX queries against datasets, paging through large result sets.

What you can do
This local MCP server connects an assistant to Power BI so it can list and browse workspaces and execute DAX queries against the datasets it finds. Query results can be paged, which helps when a query returns more rows than fit in a single response. It is aimed at read-style analysis of Power BI data rather than building or editing reports.
When to use it
Worth adding when you want an assistant to explore Power BI workspaces or pull numbers from Power BI datasets with DAX during analysis. It fits analysts who already work in Power BI and want conversational querying instead of clicking through reports.
Requirements
Runs as a local process, installed from the PyPI package powerbi-analyst-mcp, so a Python environment is needed. It requires Azure AD credentials supplied through the environment variables POWERBI_CLIENT_ID and POWERBI_TENANT_ID, plus network access to Power BI. The manifest declares no authentication method, so the exact sign-in flow is not documented here.
Before you install
It asks for Azure AD identifiers (POWERBI_CLIENT_ID, POWERBI_TENANT_ID), which tie the server to your tenant and should be handled as configuration secrets. Access is governed by the permissions granted to that Azure AD application, so scope it narrowly. The description only mentions browsing and querying, but confirm whether the credentials also allow writes before pointing it at production workspaces.

Installation

In SourceWeft

  1. Open Power BI Analyst MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.