Skip to main content
Glama
sdebruyn

fabric-dw-mcp-cli

by sdebruyn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to fabric-dw-mcp-cli

No user-submitted related servers found.

    Related Servers

    • sql-server-mcp

      ahaugerud
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server for read-only SQL Server / MS Fabric queries. It authenticates as the user via Entra ID and runs one server process per tenant.
      MIT

    • mcp-fabric

      rajivdatta
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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

    • mcp-databricks

      yabur
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides MCP tools to interact with Databricks SQL warehouses, enabling metadata discovery, table reading, and DDL operations.
      -

    • Microsoft Fabric MCP Server

      Jasuni69
      F
      license
      C
      quality
      D
      maintenance
      A 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
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 123 tools

    Disambiguation3/5

    Most tools target a distinct resource and action, with detailed descriptions that help an agent choose correctly. However, load_table_from_url and import_table_from_url are near-duplicates (both COPY INTO from a URL), and execute_sql overlaps with virtually every dedicated tool. Some related clusters (list_warehouses vs. list_sql_endpoints) also require careful reading to avoid misselection.

    Naming Consistency3/5

    The dominant pattern is verb_noun and is largely readable, but destructive operations are split inconsistently between 'drop_' (drop_view, drop_procedure, drop_function) and 'delete_' (delete_table, delete_warehouse, delete_schema). The same conceptual operation is also named both load_table_from_url and import_table_from_url, breaking a strict one-verb-per-action convention.

    Tool Count1/5

    At 123 tools, this is far beyond the range where an agent can efficiently discover and select the right tool without significant overhead. Even a comprehensive warehouse management surface could be consolidated into far fewer, broader tools. The extreme count will likely cause prompt-size and selection-cost problems.

    Completeness5/5

    The surface is exhaustive for the stated domain: full lifecycle coverage for warehouses, SQL endpoints, tables, views, procedures, functions, schemas, snapshots, restore points, SQL pools, permissions, security policies, masking, auditing, and query monitoring. Any residual gap (e.g. row-level DML or ALTER TABLE) is covered by the deliberately explicit execute_sql fallback. There are no obvious dead ends.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources