Microsoft Fabric MCP Server Extension for Visual Studio Code

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. The Fabric MCP Server packages complete OpenAPI specifications into a single context layer for AI-assisted development—without connecting to live Fabric environments.

Table of Contents

• Overview
• Installation
• Usage
  • Getting Started
  • What can you do with the Fabric MCP Server?
  • Available Tools
• Support and Reference
  • Documentation
  • Feedback and Support
  • Security
  • Data Collection
  • Contributing
  • Code of Conduct

Overview

Microsoft Fabric MCP Server gives your AI agents the knowledge they need to generate robust, production-ready code for Microsoft Fabric—all without directly accessing your environment.

Key capabilities:

• Complete API Context: Full OpenAPI specifications for all supported Fabric workloads
• 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 Security: Runs entirely on your machine—never connects to your Fabric environment

Installation

• Install the Fabric MCP Server Visual Studio Code extension
• Start (or Auto-Start) the MCP Server

  VS Code (version 1.103 or above): You can configure MCP servers to start automatically using the chat.mcp.autostart setting.

  Enable Autostart

  1. Open Settings in VS Code.
  2. Search for chat.mcp.autostart.
  3. Select newAndOutdated to automatically start MCP servers without manual refresh.

  Manual Start (if autostart is off)

  1. Open Command Palette (Ctrl+Shift+P / Cmd+Shift+P).
  2. Run MCP: List Servers.
  3. Select Fabric MCP Server, then click Start Server.
  4. Check That It's Running
     • Go to the Output tab in VS Code.
     • Look for log messages confirming the server started successfully.
• (Optional) Configure server behavior in VS Code settings (search for "Fabric MCP") You're all set! Fabric MCP Server is now ready to help you work smarter with Microsoft Fabric in VS Code.

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
3. Try a prompt that uses Fabric context, such as What Fabric workload types are available?
   • The agent should be able to use the Fabric MCP Server tools to complete your query
4. Check out the Microsoft Fabric documentation and review the troubleshooting guide for commonly asked questions
5. 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:

📊 Fabric Workloads & APIs

• "What are the available Fabric workload types I can work with?"
• "Show me the OpenAPI operations for 'notebook' and give a sample creation body"
• "Get the platform-level API specifications for Microsoft Fabric"
• "List all supported Fabric item types"

🏗️ Resource Definitions & Schemas

• "Create a Lakehouse resource definition with a schema that enforces a string column and a datetime column"
• "Show me the JSON schema for a Data Pipeline item definition"
• "Generate a Semantic Model configuration with sample measures"
• "What properties are required for creating a KQL Database?"

📝 Best Practices & Examples

• "Show me best practices for handling API throttling in Fabric"
• "How should I implement retry logic for Fabric API rate limits?"
• "List recommended retry/backoff behavior for Fabric APIs when rate-limited"
• "Show me best practices for authenticating with Fabric APIs"
• "Get example request/response payloads for creating a Notebook"
• "What are the pagination patterns for Fabric REST APIs?"

🔧 Development Workflows

• "Generate a data pipeline configuration with sample data sources"
• "Help me scaffold a Fabric workspace with Lakehouse and notebooks"
• "Show me how to handle long-running operations in Fabric APIs"
• "What's the recommended error handling pattern for Fabric API calls?"

OneLake (onelake)

All commands accept either GUID identifiers (--workspace-id, --item-id) or friendly names (--workspace, --item), with the exception of onelake item create, which currently requires GUID identifiers. Friendly-name items must be provided as <itemName>.<itemType> (for example, SalesLakehouse.lakehouse). Use dotnet run -- onelake --help (or fabmcp onelake --help for published builds) to inspect the complete option set before scripting.

Support and Reference

Documentation

• See the Microsoft Fabric documentation to learn about the Microsoft Fabric platform.
• For MCP server-specific troubleshooting, see the Troubleshooting Guide.

Feedback and Support

• Check the Troubleshooting guide to diagnose and resolve common issues.
• We're building this in the open. Your feedback is much appreciated!
  • 👉 Open an issue in the public GitHub repository — we'd love to hear from you!

Security

The Fabric MCP Server is a local-first tool that runs entirely on your machine. It provides API specifications, schemas, and best practices without connecting to live Microsoft Fabric environments.

MCP as a phenomenon is very novel and cutting-edge. As with all new technology standards, consider doing a security review to ensure any systems that integrate with MCP servers follow all regulations and standards your system is expected to adhere to.

Data Collection

The software may collect information about you and your use of the software and send it to Microsoft. Microsoft may use this information to provide services and improve our products and services. You may turn off the telemetry by following the instructions here.

Contributing

We welcome contributions to the Fabric MCP Server! Whether you're fixing bugs, adding new features, or improving documentation, your contributions are welcome.

Please read our Contributing Guide for guidelines on:

• 🛠️ Setting up your development environment
• ✨ Adding new commands
• 📝 Code style and testing requirements
• 🔄 Making pull requests

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information, see the Code of Conduct FAQ or contact open@microsoft.com with any additional questions or comments.

License

This project is licensed under the MIT License — see the LICENSE file for details.