Install the fabric-dw MCP server¶

fabric-dw-mcp is an MCP server that exposes Fabric Data Warehouse administration as tools your AI assistant can call. Pick your client below.

TL;DR — uvx¶

The recommended runner is uvx, which fetches and runs the published package on demand without any global install:

uvx fabric-dw-mcp

Every client snippet below configures uvx fabric-dw-mcp as the entry point, so your AI tool always picks up the latest published version. Pin a version with uvx fabric-dw-mcp@2026.6.0 if you need reproducibility.

You will also need an Azure credential the server can use to call the Fabric REST and SQL APIs. Set the FABRIC_AUTH environment variable to select a source:

FABRIC_AUTH=default (default) — delegates to azure-identity DefaultAzureCredential, which tries environment variables, Workload/Managed Identity, Azure CLI, Azure Developer CLI, Azure PowerShell, and interactive browser in order. See Authentication for the full chain.
FABRIC_AUTH=sp plus AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET for service-principal auth.
FABRIC_AUTH=interactive to force browser sign-in.

Claude Code¶

Source: https://code.claude.com/docs/en/mcp

Add the server at user scope (available in all your projects):

claude mcp add --scope user \
  --env FABRIC_AUTH=default \
  fabric-dw -- uvx fabric-dw-mcp

For service-principal auth, pass the extra variables:

claude mcp add --scope user \
  --env FABRIC_AUTH=sp \
  --env AZURE_TENANT_ID=<tenant-id> \
  --env AZURE_CLIENT_ID=<client-id> \
  --env AZURE_CLIENT_SECRET=<client-secret> \
  fabric-dw -- uvx fabric-dw-mcp

To share the server configuration with your team instead, use --scope project. Claude Code writes a .mcp.json file to the project root; check that file into version control. Scope reference:

Scope	Stored in	Shared
`local` (default)	`~/.claude.json`	No
`project`	`.mcp.json` in project root	Yes, via VCS
`user`	`~/.claude.json`	No

The equivalent .mcp.json snippet (project scope, default auth):

{
  "mcpServers": {
    "fabric-dw": {
      "command": "uvx",
      "args": ["fabric-dw-mcp"],
      "env": {
        "FABRIC_AUTH": "default"
      }
    }
  }
}

After adding, verify with /mcp inside a Claude Code session. You should see 22 tools including list_workspaces, get_warehouse, kill_session, and clear_cache.

Cursor¶

Source: https://learn.microsoft.com/microsoft-cloud/dev/dev-proxy/how-to/use-mcp-server?WT.mc_id=MVP_310840#configure-the-mcp-server

Add this snippet to ~/.cursor/mcp.json (global, all projects) or .cursor/mcp.json in a specific project root:

{
  "mcpServers": {
    "fabric-dw": {
      "command": "uvx",
      "args": ["fabric-dw-mcp"],
      "env": {
        "FABRIC_AUTH": "default"
      }
    }
  }
}

For service-principal auth:

{
  "mcpServers": {
    "fabric-dw": {
      "command": "uvx",
      "args": ["fabric-dw-mcp"],
      "env": {
        "FABRIC_AUTH": "sp",
        "AZURE_TENANT_ID": "<tenant-id>",
        "AZURE_CLIENT_ID": "<client-id>",
        "AZURE_CLIENT_SECRET": "<client-secret>"
      }
    }
  }
}

Restart Cursor after saving. Open Settings → MCP to confirm the server status.

GitHub Copilot¶

VS Code¶

Source: https://code.visualstudio.com/docs/copilot/customization/mcp-servers

Add the server in .vscode/mcp.json (workspace-level, check into VCS) or open the Command Palette and run MCP: Open User Configuration for a user-level file:

{
  "servers": {
    "fabric-dw": {
      "type": "stdio",
      "command": "uvx",
      "args": ["fabric-dw-mcp"],
      "env": {
        "FABRIC_AUTH": "default"
      }
    }
  }
}

For service-principal auth:

{
  "servers": {
    "fabric-dw": {
      "type": "stdio",
      "command": "uvx",
      "args": ["fabric-dw-mcp"],
      "env": {
        "FABRIC_AUTH": "sp",
        "AZURE_TENANT_ID": "<tenant-id>",
        "AZURE_CLIENT_ID": "<client-id>",
        "AZURE_CLIENT_SECRET": "<client-secret>"
      }
    }
  }
}

VS Code Copilot MCP support

MCP support in VS Code Copilot is generally available as of VS Code 1.99 (April 2025). Use Agent mode in Copilot Chat to access MCP tools; they are not available in Ask or Edit modes.

After saving, open GitHub Copilot Chat, switch to Agent mode, and click the tools icon to confirm fabric-dw appears.

CLI¶

Source: https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers

The Copilot CLI (gh copilot) stores its MCP configuration separately from VS Code. Add the server to ~/.copilot/mcp-config.json (user-level, applies to all sessions):

{
  "mcpServers": {
    "fabric-dw": {
      "type": "stdio",
      "command": "uvx",
      "args": ["fabric-dw-mcp"],
      "env": {
        "FABRIC_AUTH": "default"
      }
    }
  }
}

For service-principal auth:

{
  "mcpServers": {
    "fabric-dw": {
      "type": "stdio",
      "command": "uvx",
      "args": ["fabric-dw-mcp"],
      "env": {
        "FABRIC_AUTH": "sp",
        "AZURE_TENANT_ID": "<tenant-id>",
        "AZURE_CLIENT_ID": "<client-id>",
        "AZURE_CLIENT_SECRET": "<client-secret>"
      }
    }
  }
}

You can also add the server interactively without editing the file: start the CLI, enter /mcp add, choose STDIO as the server type, set the command to uvx fabric-dw-mcp, and add FABRIC_AUTH=default as an environment variable.

To share the configuration with a project instead of setting it globally, add a .mcp.json file (or .github/mcp.json) in the project root with the same mcpServers block. Project-level configuration takes precedence over user-level when server names conflict.

Desktop (preview)¶

Source: https://docs.github.com/en/copilot/how-tos/github-copilot-app/customize-github-copilot-app

Technical preview

The GitHub Copilot desktop app is in technical preview and subject to change. The configuration approach described here reflects the current state of the preview.

The GitHub Copilot desktop app is built on top of Copilot CLI and shares the same MCP configuration. Any MCP servers you have added to ~/.copilot/mcp-config.json for the CLI are automatically available in the desktop app. No separate config file is needed.

To add or manage MCP servers directly from the desktop app, open Settings → MCP Servers. The app provides a catalog of popular servers and accepts custom server definitions without requiring manual file edits.

To register fabric-dw-mcp via the settings UI, choose Add custom server, select STDIO as the type, set the command to uvx, the arguments to fabric-dw-mcp, and add FABRIC_AUTH=default as an environment variable. The app writes the result to ~/.copilot/mcp-config.json using the same format shown in the CLI section above.

Continue¶

Source: https://docs.continue.dev/customize/deep-dives/mcp

Create .continue/mcpServers/fabric-dw.yaml in your workspace root (or ~/.continue/mcpServers/fabric-dw.yaml for a global config):

name: fabric-dw
version: 0.0.1
schema: v1
mcpServers:
  - name: fabric-dw
    type: stdio
    command: uvx
    args:
      - fabric-dw-mcp
    env:
      FABRIC_AUTH: default

For service-principal auth, replace the env block:

    env:
      FABRIC_AUTH: sp
      AZURE_TENANT_ID: <tenant-id>
      AZURE_CLIENT_ID: <client-id>
      AZURE_CLIENT_SECRET: <client-secret>

Note

MCP servers are only available in Agent mode in Continue. Switch to Agent mode in the chat panel before invoking tools.

Alternatively, if you prefer to stay in JSON and already have a .continue/config.json, add to the top-level mcpServers array:

{
  "mcpServers": [
    {
      "name": "fabric-dw",
      "type": "stdio",
      "command": "uvx",
      "args": ["fabric-dw-mcp"],
      "env": {
        "FABRIC_AUTH": "default"
      }
    }
  ]
}

Codex CLI¶

Source: https://developers.openai.com/codex/mcp

Add to ~/.codex/config.toml (global) or .codex/config.toml in a project directory:

[mcp_servers.fabric-dw]
command = "uvx"
args = ["fabric-dw-mcp"]

[mcp_servers.fabric-dw.env]
FABRIC_AUTH = "default"

For service-principal auth:

[mcp_servers.fabric-dw]
command = "uvx"
args = ["fabric-dw-mcp"]

[mcp_servers.fabric-dw.env]
FABRIC_AUTH = "sp"
AZURE_TENANT_ID = "<tenant-id>"
AZURE_CLIENT_ID = "<client-id>"
AZURE_CLIENT_SECRET = "<client-secret>"

If you prefer to read secrets from the environment rather than hard-coding them in the config file, use env_vars to pass through variables that are already set in your shell:

[mcp_servers.fabric-dw]
command = "uvx"
args = ["fabric-dw-mcp"]
env_vars = ["FABRIC_AUTH", "AZURE_TENANT_ID", "AZURE_CLIENT_ID", "AZURE_CLIENT_SECRET"]

Codex picks up config changes on the next invocation; no explicit reload is needed.

Verifying¶

After configuring your client, restart it and ask the assistant to list its available tools. You should see entries like list_workspaces, get_warehouse, kill_session, clear_cache, and 18 others (22 tools total).

Troubleshooting¶

Permission denied calling Fabric: run az account show and confirm your account has at least Workspace Contributor on the target Fabric workspace.
uv: command not found: install uv from https://docs.astral.sh/uv/.
uvx: command not found: uvx ships with uv — install uv and it will be available.
Server hangs at startup: the server is likely waiting for a credential to be resolved. Ensure your Azure credential is set up (see Authentication) before starting your assistant.
Tools not visible in Copilot Chat: ensure you are in Agent mode, not Ask or Edit mode.
Tools not visible in Continue: ensure you are in Agent mode.

For a more complete reference of error messages and resolutions, see the Troubleshooting page.