mcp-fabric-api
Related Servers
Alternatives to mcp-fabric-api
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA Python-based MCP server that enables interaction with Microsoft Fabric APIs for managing workspaces, lakehouses, warehouses, and tables through natural language.17-
- AlicenseNot gradedqualityCmaintenanceMCP server for managing Microsoft Fabric notebooks and Dataflow Gen2 via the Fabric REST API. Supports reading, creating, updating, running, and deleting items within workspaces.MIT
- AlicenseNot gradedqualityDmaintenanceThe Fabric-Analytics-MCP server enables AI agents to interact directly with Microsoft Fabric using natural language. It transforms complex data engineering tasks—such as workspace management, data exploration, and job execution—into intuitive, conversational workflows for LLMs like Claude or GitHub7 npm110MIT
- AlicenseNot gradedqualityCmaintenanceRemote and centralized MCP server that enables AI models to interact with Microsoft Fabric (workspaces and items) via the Fabric Core REST API, using delegated OAuth 2.1 authentication with Microsoft Entra ID so each user's permissions and restrictions are respected.GPL 3.0
- FlicenseCqualityDmaintenanceA Python MCP server that lets you manage Microsoft Fabric through natural language in Claude Code or Claude Desktop, with 77+ tools covering workspaces, lakehouses, warehouses, SQL, DAX, semantic models, notebooks, pipelines, OneLake, and Microsoft Graph.83-
- FlicenseNot gradedqualityDmaintenanceMCP server for reading and analyzing Fabric semantic models. Supports getting model definitions and executing DAX queries against Power BI datasets.17-
TDQS
Scored across 219 tools
Most tools are clearly distinguished by a resource prefix and action verb, making the majority of the 219 tools easy to tell apart. Some ambiguity exists around SQL endpoint access (sql_endpoint_get vs lakehouse_get_sql_endpoint vs warehouse_get_sql_endpoint) and semantic model definition format variants (get_bim vs get_tmdl vs get_details), but the descriptions largely resolve these cases.
The naming convention is highly consistent throughout: resource_action in snake_case, with predictable verbs like list, get, create, update, delete, run, and cancel. Even format-specific variants like semantic_model_create_bim vs semantic_model_create_tmdl follow the same structural pattern. This makes the tool surface very predictable despite its size.
219 tools is an extreme count that far exceeds the 3-15 tool range considered well-scoped and exceeds the 50+ threshold for extreme mismatch. Even for a broad Microsoft Fabric API, this single server creates severe context bloat, high selection overhead, and poor agent usability. The surface should be split into multiple focused MCP servers or dramatically consolidated.
The tool set covers a very broad Fabric domain: CRUD for nearly every item type, definition management, run/status/cancel operations, git integration, deployment pipelines, environment management, and auth. Minor gaps exist, such as missing dataflow_update_definition and graphql_api_update_definition, but these can be worked around with recreate or direct API usage. No critical dead ends block common workflows.