Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Microsoft Fabric provides two complementary Model Context Protocol (MCP) servers that enable AI agents to interact with Fabric using natural language. Choose the cloud-hosted Core server for quick access to Fabric workspaces and items, or the local Pro-Dev server for development workflows with file system access and extensibility.
What is Model Context Protocol
Model Context Protocol (MCP) is an open standard that enables AI agents to securely access external data sources and services through a unified interface. MCP moves AI interactions beyond conversation to actual system control, allowing agents to read data, perform operations, and automate workflows.
Key benefits
- Standardized interface — One protocol works across all AI agents (VS Code with GitHub Copilot, Claude Desktop, and custom agents)
- Secure by design — Built-in authentication, role-based access control (RBAC), and audit trails protect your enterprise data
- Typed operations — Defined schemas for inputs and outputs reduce errors and improve reliability
- Discoverable capabilities — AI agents explore available operations automatically, adapting to what you can access
How it works
When you ask an AI agent a question about Fabric:
- The agent analyzes your prompt to understand your intent.
- The agent discovers available MCP tools and selects the appropriate operation.
- The MCP server authenticates your request and validates your permissions.
- The server calls the Fabric API on your behalf.
- The agent interprets the API response and provides a natural language answer.
What is Fabric Core MCP Server
Fabric Core MCP Server is a remote, cloud-hosted endpoint that exposes Fabric's public APIs as typed MCP tools. Any MCP-compatible AI agent can connect to it without installing software — just add the server URL and authenticate with your Microsoft Entra ID account.
Note
Fabric Core MCP Server is currently in preview. Features and configuration may change before general availability.
Key characteristics:
- Cloud-hosted — No local installation required. Connect by pointing your AI agent to the server URL.
- API-driven — Each MCP tool maps to a Fabric REST API for workspaces, items, permissions, and more.
- OAuth 2.0 authentication — Automatic authentication through Microsoft Entra ID using your existing credentials.
- RBAC enforced — Every operation respects your Fabric role assignments (Admin, Member, Contributor, or Viewer). You can only access resources you're authorized to use.
- Audit logged — All actions are recorded in Fabric audit logs with your user identity.
What is Fabric Pro-Dev MCP Server
Fabric Pro-Dev MCP Server is a local, development-focused MCP server that runs as a subprocess on your machine. It provides AI agents with access to Fabric API documentation, OneLake data operations, and core Fabric item creation — alongside access to your local file system.
Key characteristics:
- Local subprocess architecture — Runs on your machine whenever your AI agent needs it, no cloud dependency.
- File system integration — Read/write local files and configurations as part of development workflows.
- Development tooling — API specs, best practices, and OneLake operations optimized for building Fabric solutions.
- Open source — Extend and customize for your workflows on GitHub.
- Offline capable — Documentation and best practice tools work without a live Fabric connection.
Compare servers
| Feature | Core (cloud) | Pro-Dev (local) |
|---|---|---|
| Workspace management | Yes | — |
| Item CRUD | Yes | Create only |
| Permission management | Yes | — |
| Folder management | Yes | — |
| OneLake file operations | — | Yes |
| API docs & specs (offline) | — | Yes |
| Installation required | No | Yes (Node.js) |
| Authentication | OAuth 2.0 (Entra ID) | Local credentials |
| Audit logging | Yes | — |
| Open source | No | Yes |
Tip
You can use both servers simultaneously. Configure your AI agent to connect to both Core (for cloud operations) and Pro-Dev (for local development tasks).
Security and compliance
Both Fabric MCP servers maintain enterprise security standards:
- Authentication required — All operations require valid credentials
- RBAC enforced — You can only access resources you're authorized to use
- No privilege escalation — Servers don't grant additional permissions beyond what you have in Fabric
- Token-based — Short-lived access tokens with automatic refresh
For details on authentication flows and troubleshooting, see Get started with Core or Get started with Pro-Dev.
Related content
- Core MCP Server overview — Architecture, scenarios, and limitations
- Core MCP tools reference — All Core server tools and example workflows
- Pro-Dev MCP Server overview — Architecture and capabilities
- Pro-Dev MCP tools reference — All Pro-Dev server tools and example workflows
- Model Context Protocol specification — MCP standard
- Microsoft Fabric REST API — Fabric API reference
- Microsoft MCP Servers — Other Microsoft MCP implementations