01 · Records and state owned
Semantic models; tables, columns, measures, relationships, and model metadata; DAX queries; report pages, visuals, filters, and text; Power BI Project and TMDL artifacts; Desktop and Fabric workspace model connections.
Microsoft
Power BI
Included because Power BI exposes two distinct first-party MCP surfaces: a Fabric-hosted remote server for querying and interpreting existing semantic models, and a local stdio server for inspecting, creating, and modifying semantic-model artifacts in Desktop, Fabric workspaces, and Power BI Project files.
Analytics, SEO & experimentationSystem of intelligenceAgent-accessible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Remote MCP can return semantic-model schema, execute DAX, inspect report metadata, and generate DAX from natural language when eligible. Local MCP can inspect models, validate DAX, query data, and read model metadata from Desktop, Fabric workspaces, or PBIP/TMDL files.
03 · Actions and write paths
The remote server documents no model-authoring tools. The local server can create or update tables, columns, measures, relationships, and other semantic-model metadata, including bulk transactional changes against supported Desktop, Fabric workspace, and PBIP/TMDL targets.
04 · Authentication and permissions
Remote MCP uses Microsoft Entra OAuth, requires tenant enablement and Build permission on the semantic model, runs queries in the signed-in user's context, and enforces RLS for user authentication. Local MCP supports interactive Entra ID or service-principal authentication; effective operations are governed by Fabric RBAC and target-model access.
05 · Monitoring, approval, and recovery
Treat the remote endpoint as a governed query channel and the local process as an authoring tool. Use least-privilege Fabric roles, pin the intended workspace, model, or PBIP target, review generated DAX and bulk edits, and account for the AI client or model provider processing prompts and results outside Fabric's boundary.
06 · Limits and caveats
Both servers are Preview. Remote MCP is not a REST API, requires a tenant setting and Build permission, is stateless, can exceed report-metadata or context limits, and may not translate complex questions into valid DAX; Generate Query also depends on Copilot licensing or capacity. Local MCP requires a supported local runtime and has broader change risk.
First-party access
Documented surfaces
DAX semantic-model query ↗Power BI supports governed DAX queries against semantic models through REST APIs. Tenant settings, Build permission, row-level security, SSO, capacity, and service-principal limitations apply; this is not arbitrary SQL against the underlying source database.Source: Develop with the Execute DAX Queries REST APIMCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceProduct ↗Native platform experience
Agent access
MCP support
Official MCP serverMicrosoft remote and local MCP serversPreview
Support: Official MCP server
Read scope: Remote: get model schema and report metadata, execute DAX, and optionally generate DAX. Local: inspect semantic-model definitions, validate or run DAX, and read supported Desktop, Fabric workspace, and PBIP/TMDL targets.
Write scope: Remote MCP is query-only in the documented tool set. Local MCP can author and bulk-modify semantic-model objects; those operations can be destructive and must be scoped to an explicit target and transaction.
Authentication: Remote: Microsoft Entra OAuth to `https://api.fabric.microsoft.com/v1/mcp/powerbi`. Local: interactive Entra ID or service-principal authentication from a local stdio process.
Approval boundary: Remote DAX execution should disclose model, query, filters, and RLS identity. Local creation, rename, relationship, measure, or bulk model changes require a preview of the target and transaction and explicit confirmation before execution; destructive or high-volume edits should not run autonomously.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access1
Identity4
Governance4
Agent access3
UI extensibility3
Portability4
Observability3
Documentation4
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Microsoft ships them.
Single-platform patterns
- Executive metrics and semantic-model workbench
- Executive insight brief
- Experiment review board
- Anomaly investigation room
Multi-platform compositions
- Power BI + warehouse or semantic layer: executive insight brief
- Power BI + CRM or lifecycle platform + work-management system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
5 recorded sources
MCPRepresentative source
https://learn.microsoft.com/en-us/power-bi/developer/mcp/mcp-servers-overview ↗Official Microsoft docs clearly separate remote query surface from local authoring surface; both preview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://learn.microsoft.com/en-us/rest/api/power-bi/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://learn.microsoft.com/en-us/power-bi/developer/ ↗First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://powerbi.microsoft.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
DAX semantic-model queryTargeted review
Develop with the Execute DAX Queries REST API ↗Power BI supports governed DAX queries against semantic models through REST APIs. Tenant settings, Build permission, row-level security, SSO, capacity, and service-principal limitations apply; this is not arbitrary SQL…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party access review
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.