No user-submitted related servers found.
Scored across 105 tools
The generic item/job tools (fabric_get_item, fabric_delete_item, fabric_run_job, fabric_get_item_definition) overlap directly with type-specific tools (fabric_get_lakehouse, fabric_delete_lakehouse, fabric_run_notebook, fabric_get_notebook_definition), so an agent can easily select the wrong one for the same resource and action. Descriptions help in some cases, but the boundaries between generic and type-specific tools are repeatedly unclear.
Tools consistently use the fabric_ prefix and mostly follow a verb_noun snake_case pattern (list/get/create/update/delete/run). Minor inconsistencies exist, such as domain-prefixed names like fabric_onelake_* and fabric_git_*, add vs create for role assignments, and generic vs type-specific definition/run tools.
105 tools is an extreme count for an MCP tool surface, far beyond even the 25+ threshold. Many tools duplicate generic item operations (list_items vs list_lakehouses, delete_item vs delete_lakehouse, etc.), which inflates the count without adding proportional coherence.
The server covers most major Fabric domains—workspaces, lakehouses, warehouses, notebooks, pipelines, semantic models, shortcuts, Git, deployment pipelines, and jobs—and the generic item tools fill many lifecycle gaps. Some areas remain asymmetric (connections/gateways/capacities are mostly read/list-only, reports/semantic models lack direct create/update), but agents can often work around these via generic tools.