Microsoft Fabric MCP Server

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
• Docker
• Usage
• Getting Started
• What can you do with the Fabric MCP Server?
• Capacity Discovery
• Catalog Discovery
• Fabric Item Types & APIs
• Resource Definitions & Schemas
• Best Practices & Examples
• Development Workflows
• Workspace Metadata
• Available Tools
• Namespace Filtering
• API Documentation & Best Practices
• OneLake Data Operations
• OneLake Security — Data Access Roles
• OneLake Shortcuts
• OneLake Settings
• Core Fabric Operations
• Jobs
• 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

The manual configuration examples use mcpServers as the root object. In Visual Studio and Visual Studio Code, use servers instead.

When using the VS Code extension, fabricMcp.enabledServices selects from core, jobs, docs, onelake, and datafactory. Leave the list empty to enable all toolsets. Select both core and jobs for workflows combining item or definition operations with job submission, cancellation, instance listing/lookup, or schedule listing/creation/updates; selecting only core does not expose Jobs. If an existing setting contains publicapis, replace it with docs or clear the list; saved settings are not migrated automatically.

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:

Manual setup instructions

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

Option 1: Configure using the .NET tool (NuGet)

• Install the .NET 10 SDK or later. Verify it with dotnet --version.
• Install the published Microsoft.Fabric.Mcp tool:

powershell dotnet tool install --global Microsoft.Fabric.Mcp --source https://api.nuget.org/v3/index.json

• Ensure the .NET global tools directory is on the PATH available to your MCP client, then configure mcp.json:

json { "mcpServers": { "Fabric MCP Server": { "command": "fabmcp", "args": [ "server", "start", "--mode", "all" ], "type": "stdio" } } }

Alternatively, .NET 10 supports running the published package on demand with dnx, without a permanent tool installation:

dnx Microsoft.Fabric.Mcp --source https://api.nuget.org/v3/index.json -- server start --mode all

Both commands use the latest published stable package unless you specify a version. To pin a released version, use --version with dotnet tool install, or Microsoft.Fabric.Mcp@ with dnx.

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

• Install a supported Node.js LTS version 22.0.0 or later, with npm and npx available on your system PATH. Verify your installation with node --version, npm --version, and npx --version.
• Configure the mcp.json file with the following:

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

Build from source (contributors)

Building the repository is a separate development workflow, not required to use the published packages:

git clone https://github.com/microsoft/mcp.git

cd mcp dotnet build servers/Fabric.Mcp.Server/src/Fabric.Mcp.Server.csproj --configuration Release

Use the built servers/Fabric.Mcp.Server/src/bin/Release/fabmcp executable as your MCP client's command, with ["server", "start", "--mode", "all"] as its arguments. On Windows, use backslashes and the .exe extension.

Client-Specific 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 Document