Connect Microsoft Power BI to Claude Code

Have Claude refresh datasets and manage workspaces in Microsoft Power BI. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Microsoft Power BI to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Microsoft Power BI, you add a Microsoft Power BI MCP server: a small hosted service that exposes Microsoft Power BI's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Microsoft Power BI account. No API keys pasted into config files.

claude mcp add --transport http power-bi https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Microsoft Power BI once connected?

Full read-write Power BI access lets Claude trigger a dataset refresh, push rows into a streaming or push dataset, manage workspace membership, take over or rebind a dataset, and clone reports into another workspace. The maintenance work that used to mean clicking through the service happens where your dashboards already live, once you approve.

Trigger a refresh on a specific dataset and report the result
Push rows into a push or streaming dataset through the REST API
Add or remove a user from a workspace at a chosen access level
Take over and rebind a dataset to a different data source connection
Create a new workspace and assign reports or datasets to it
Clone a report into another workspace under a new name

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Microsoft Power BI access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Microsoft Power BI API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Microsoft Power BI changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Microsoft Power BI connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Microsoft Power BI connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Microsoft Power BI account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Microsoft Power BI's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Microsoft Power BI?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Microsoft Power BI account it signs in with. Revoking access is one click in Microsoft Power BI.

More on the Microsoft Power BI connector

Microsoft Power BI connector for claude.ai Tableau + Claude Code BigQuery + Claude Code Snowflake + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us