Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP tools for interacting with Microsoft Fabric
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"microsoft-fabric": {
"command": "npx",
"args": [
"-y",
"@microsoft/fabric-mcp",
"server",
"start"
]
}
}
}Run this in your terminal
claude mcp add microsoft-fabric -- npx -y @microsoft/fabric-mcp server startPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"microsoft-fabric": {
"command": "npx",
"args": [
"-y",
"@microsoft/fabric-mcp",
"server",
"start"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"microsoft-fabric": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@microsoft/fabric-mcp",
"server",
"start"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain microsoft.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.4.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need .NET, Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Apify MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A local-first Model Context Protocol (MCP) server that provides AI agents with comprehensive access to Microsoft Fabric's public APIs, item definitions, and best practices. Documentation tools use bundled specifications without connecting to live Fabric environments; operational tools call Fabric APIs using the configured identity.
Microsoft Fabric MCP Server gives your AI agents the knowledge they need to generate robust, production-ready code for Microsoft Fabric, alongside authenticated tools for working with Fabric resources.
Key capabilities:
The manual configuration examples use mcpServers as the root object. In Visual Studio and Visual Studio Code, use servers instead.
When using the VS Code extension, fabricMcp.enabledServices selects from core, jobs, docs, onelake, and datafactory. Leave the list empty to enable all toolsets. Select both core and jobs for workflows combining item or definition operations with job submission, cancellation, instance listing/lookup, or schedule listing/creation/updates; selecting only core does not expose Jobs. If an existing setting contains publicapis, replace it with docs or clear the list; saved settings are not migrated automatically.
Start using Fabric MCP with your favorite IDE. We recommend VS Code:
Compatible with both the Stable and Insiders builds of VS Code.
Fabric MCP Server can also be configured across other IDEs, CLIs, and MCP clients:
Manual setup instructions
Use one of the following options to configure your mcp.json:
dotnet --version.powershell dotnet tool install --global Microsoft.Fabric.Mcp --source https://api.nuget.org/v3/index.json
PATH available to your MCP client, then configure mcp.json:json { "mcpServers": { "Fabric MCP Server": { "command": "fabmcp", "args": [ "server", "start", "--mode", "all" ], "type": "stdio" } } }
Alternatively, .NET 10 supports running the published package on demand with dnx, without a permanent tool installation:
dnx Microsoft.Fabric.Mcp --source https://api.nuget.org/v3/index.json -- server start --mode all
Both commands use the latest published stable package unless you specify a version. To pin a released version, use --version with dotnet tool install, or Microsoft.Fabric.Mcp@ with dnx.
npm and npx available on your system PATH. Verify your installation with node --version, npm --version, and npx --version.mcp.json file with the following:json { "mcpServers": { "fabric-mcp-server": { "command": "npx", "args": [ "-y", "@microsoft/fabric-mcp@latest", "server", "start", "--mode", "all" ] } } }
Building the repository is a separate development workflow, not required to use the published packages:
git clone https://github.com/microsoft/mcp.git
cd mcp dotnet build servers/Fabric.Mcp.Server/src/Fabric.Mcp.Server.csproj --configuration Release
Use the built servers/Fabric.Mcp.Server/src/bin/Release/fabmcp executable as your MCP client's command, with ["server", "start", "--mode", "all"] as its arguments. On Windows, use backslashes and the .exe extension.
Client-Specific Configuration
| IDE | File Location | Documentation Link |
|---|---|---|
| Claude Code | ~/.claude.json or .mcp.json (project) | Claude Code MCP Configuration |
| Claude Desktop | ~/.claude/claude_desktop_config.json (macOS) %APPDATA%\Claude\claude_desktop_config.json (Windows) | Claude Desktop MCP Setup | | Cursor | ~/.cursor/mcp.json or .cursor/mcp.json | [Cursor MCP Document
Only the beginning is shown; read the rest in the repo