Model Context Protocol (MCP) server for Microsoft Fabric - exposes Fabric operations as MCP tools for AI agents
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"ms-fabric-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# ms-fabric-mcp-server [](https://pypi.org/project/ms-fabric-mcp-server/) [](https://pypi.org/project/ms-fabric-mcp-server/) [](https://opensource.org/licenses/MIT) [](https://github.com/bablulawrence/ms-fabric-mcp-server/actions/workflows/tests.yml) A Model Context Protocol (MCP) server for Microsoft Fabric. Exposes Fabric operations (workspaces, notebooks, SQL, Livy, pipelines, jobs) as MCP tools that AI agents can invoke. > ⚠️ **Warning**: This package is intended for **development environments only** and should not be used in production. It includes tools that can perform destructive operations (e.g., `delete_item`, `delete_lakehouse_file`, `delete_activity_from_pipeline`) and execute arbitrary code via Livy Spark sessions. Always review AI-generated tool calls before execution. ## Quick Start The fastest way to use this MCP server is with `uvx`: ```bash uvx ms-fabric-mcp-server ``` ## Installation ```bash # Using uv (recommended) uv pip install ms-fabric-mcp-server # Using pip pip install ms-fabric-mcp-server # With SQL support (requires pyodbc) pip install ms-fabric-mcp-server[sql] # With OpenTelemetry tracing pip install ms-fabric-mcp-server[sql,telemetry] ``` ## Authentication Uses **DefaultAzureCredential** from `azure-identity` - no explicit credential configuration needed. This automatically tries multiple authentication methods: 1. Environment credentials (`AZURE_CLIENT_ID`, `AZURE_TENANT_ID`, `AZURE_CLIENT_SECRET`) 2. Managed Identity (when running on Azure) 3. Azure CLI credentials (`az login`) 4. VS Code credentials 5. Azure PowerShell credentials **No Fabric-specific auth environment variables are needed** - it just works if you're…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.