Fabric Analytics MCP Server

MCP server for Microsoft Fabric Analytics with Synapse-to-Fabric migration - enables LLMs to access, analyze, and migrate workloads to Microsoft Fabric. That is what the fabric analytics mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

A comprehensive Model Context Protocol (MCP) server that provides analytics capabilities and tools for interacting with Microsoft Fabric data platform. This server enables AI assistants like Claude to seamlessly access, analyze, and monitor Microsoft Fabric resources through standardized MCP protocols, bringing the power of Microsoft Fabric directly to your AI conversations.

The tools it exposes

The server publishes 4 tools. What each one is for:

• fabric_list_synapse_workspaces — List all Synapse workspaces in your Azure subscription
• fabric_discover_synapse_workspace — Inventory notebooks, pipelines, linked services, and Spark jobs from Synapse
• fabric_transform_notebooks — Transform Synapse notebooks to Fabric format (mssparkutils → notebookutils)
• fabric_migrate_synapse_to_fabric — Complete end-to-end migration with discovery, transformation, and provisioning

What it needs from you

Configuration is passed through the environment: FABRIC_AUTH_METHOD, FABRIC_TOKEN, FABRIC_WORKSPACE_ID, ENABLE_HEALTH_SERVER, ACR_NAME, FABRIC_CLIENT_ID, FABRIC_CLIENT_SECRET, FABRIC_TENANT_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

Among the payments and commerce options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Fabric Analytics MCP's toolset — fabric_list_synapse_workspaces, fabric_discover_synapse_workspace, fabric_transform_notebooks and 1 more — is a fair guide to whether it matches your workflow. It is maintained by santhoshravindran7; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Fabric Analytics MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.