Fabric Dw vs Filesystem

A side-by-side look at the Fabric Dw and Filesystem MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Fabric Dw logoFabric DwData PlatformsMCP server for Microsoft Fabric Data Warehouses and SQL Analytics Endpoints36FairAuth: not declaredFilesystem logoFilesystemFile Systems · Local subprocess (stdio)Secure file operations with configurable access controls.85ExcellentAuth: no auth required

Verdict: choose Fabric Dw for data platforms work; choose Filesystem for file systems as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Fabric Dw logoChoose Fabric Dw when

  • You need dedicated capabilities in the Data Platforms domain.
Explore Fabric Dw

Filesystem logoChoose Filesystem when

  • You need dedicated capabilities in the File Systems domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like path, head, tail.
Explore Filesystem

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFabric Dw logoFabric DwFilesystem logoFilesystem
CategoryData PlatformsFile Systems
Quality signal36/100 · Fair85/100 · Excellent
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars1091,546
Directory activity 1 views 0 installs 0 upvotes 11 views 0 installs 0 upvotes
ToolsNot listed17

Tools & capabilities

Fabric Dw tools

No tool names declared yet. Check the project README from the listing page.

Filesystem tools 17

  • path
  • head
  • tail
  • paths
  • content
  • edits
  • oldText
  • newText
  • dryRun
  • sortBy
  • source
  • destination
  • +5 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Fabric Dw

No confirmed install command for Fabric Dw yet — follow the setup steps linked from its listing page rather than a guessed package name.

Filesystem

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem"
      ]
    }
  }
}

Frequently asked questions

Fabric Dw is categorized under Data Platforms and uses an install path we have not confirmed yet. Filesystem belongs to File Systems and uses a local stdio subprocess. Pick Fabric Dw for data platforms work and Filesystem for file systems.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Fabric Dw has no confirmed install command yet — follow its own setup instructions.

Fabric Dw has no declared pricing — check the project's own site. Filesystem is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add fabric-dw and filesystem as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Fabric Dw has a quality signal of 36/100 (Fair) with 1 views, 0 installs and 10 GitHub stars. Filesystem has 85/100 (Excellent) with 11 views, 0 installs and 91,546 GitHub stars.