Microsoft Fabric MCP Server

A local-first Model Context Protocol (MCP) server that provides AI agents with comprehensive access to Microsoft Fabric's public APIs, item definitions, and best practices. Documentation tools use bundled specifications without connecting to live Fabric environments; operational tools call Fabric APIs using the configured identity.

Table of Contents

• Overview
• Installation
• IDE
• VS Code (Recommended)
• Manual Setup
• Usage
• Getting Started
• What can you do with the Fabric MCP Server?
• Catalog Discovery
• Fabric Item Types & APIs
• Resource Definitions & Schemas
• Best Practices & Examples
• Development Workflows
• Workspace Metadata
• Available Tools
• API Documentation & Best Practices
• OneLake Data Operations
• OneLake Security — Data Access Roles
• OneLake Shortcuts
• OneLake Settings
• Core Fabric Operations
• Data Factory Operations
• Support and Reference
• Documentation
• Feedback and Support
• Security
• Data Collection
• Contributing
• Code of Conduct
• License

Overview

Microsoft Fabric MCP Server gives your AI agents the knowledge they need to generate robust, production-ready code for Microsoft Fabric, alongside authenticated tools for working with Fabric resources.

Key capabilities:

• Complete API Context: Full OpenAPI specifications for all supported Fabric item types
• Item Definition Knowledge: JSON schemas for every Fabric item type (Lakehouses, pipelines, semantic models, notebooks, etc.)
• Built-in Best Practices: Embedded guidance on pagination, error handling, and recommended patterns
• Local-First Documentation: Documentation tools read bundled resources locally; operational tools access Fabric under the configured identity
• Workspace Metadata Updates: Rename a known workspace or update or clear its description without changing other properties
• Data Factory Integration: Pipeline and Dataflow Gen2 management with M query execution

Installation

IDE

Start using Fabric MCP with your favorite IDE. We recommend VS Code:

VS Code (Recommended)

Compatible with both the Stable and Insiders builds of VS Code.

1. Install the GitHub Copilot Chat extension.
2. Install the Fabric MCP Server extension.

Manual Setup

Fabric MCP Server can also be configured across other IDEs, CLIs, and MCP clients:

Use one of the following options to configure your mcp.json:

#### Option 1: Configure using .NET (build from source)

• You must have the latest .NET 10 SDK LTS installed.

To verify the .NET version, run: dotnet --version

• Clone and build the repository:

    git clone https://github.com/microsoft/mcp.git
    cd mcp
    dotnet build servers/Fabric.Mcp.Server/src/Fabric.Mcp.Server.csproj --configuration Release

• Configure the mcp.json file with the following:

    {
        "mcpServers": {
            "Fabric MCP Server": {
                "command": "/path/to/repo/servers/Fabric.Mcp.Server/src/bin/Release/fabmcp",
                "args": [
                    "server",
                    "start"
                ],
                "type": "stdio"
            }
        }
    }

Platform Notes: - macOS/Linux: Use the path as-is - Windows: Use backslashes and add .exe extension: C:\path\to\repo\servers\Fabric.Mcp.Server\src\bin\Release\fabmcp.exe

#### Option 2: Configure using Node.js (npm/npx)

• To use Fabric MCP server from node one must have Node.js (LTS) installed and available on your system PATH — this provides both npm and npx. We recommend the latest Node.js LTS version. To verify your installation run: node --version, npm --version, and npx --version.
• Configure the mcp.json file with the following:

    {
        "mcpServers": {
            "fabric-mcp-server": {
            "command": "npx",
            "args": [
                "-y",
                "@microsoft/fabric-mcp@latest",
                "server",
                "start",
                "--mode",
                "all"
                ]
            }
        }
    }

Note: When manually configuring Visual Studio and Visual Studio Code, use servers instead of mcpServers as the root object.

Client-Specific Configuration | IDE | File Location | Documentation Link | |-----|---------------|-------------------| | Claude Code | ~/.claude.json or .mcp.json (project) | Claude Code MCP Configuration | | Claude Desktop | ~/.claude/claude_desktop_config.json (macOS)%APPDATA%\Claude\claude_desktop_config.json (Windows) | Claude Desktop MCP Setup | | Cursor | ~/.cursor/mcp.json or .cursor/mcp.json | Cursor MCP Documentation | | VS Code | .vscode/mcp.json (workspace)settings.json (user) | VS Code MCP Documentation | | Windsurf | ~/.codeium/windsurf/mcp_config.json | Windsurf Cascade MCP Integration |

Usage

Getting Started

1. Open GitHub Copilot in VS Code and switch to Agent mode.
2. Click refresh on the tools list

• You should see the Fabric MCP Server in the list of tools

1. Try a prompt that uses Fabric context, such as What Fabric item types are available?

• The agent should be able to use the Fabric MCP Server tools to complete your query

1. Check out the Microsoft Fabric documentation and review the troubleshooting guide for commonly asked questions
2. We're building this in the open. Your feedback is much appreciated!

• Open an issue in the public repository

What can you do with the Fabric MCP Server?

The Fabric MCP Server supercharges your agents with Microsoft Fabric context. Here are some prompts you can try:

Capacity Discovery

• "List Fabric capacities where I am an administrator or contributor"
• "Show the IDs, SKUs, regions, and states of my accessible Fabric capacities"
• "Get the next page of Fabric capacities using the continuation token from the previous response"

core_list-capacities returns exactly one page of capacity metadata in capacities, with continuationToken and continuationUri when supplied by Fabric. Pass the token unchanged through --continuation-token to request another page. Returned URIs are metadata only and are never followed; the tool does not retrieve all pages automatically.

The Fabric List Capacities API lists capacities where the calling principal is an administrator or contributor. It supports users, service principals, and managed identities. Delegated calls require Capacity.Read.All or Capacity.ReadWrite.All; this is not an Azure subscription inventory and takes no subscription parameter.

Catalog Discovery

• "Search the OneLake catalog for items related to 'sales revenue'"
• "Find a Lakehouse with 'customer' in the name across my workspaces"