A production-grade Windows Developer MCP Server for LM Studio and other MCP-compatible AI clients
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"windows-developer-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Windows Developer MCP Server [](https://glama.ai/mcp/servers) [](https://github.com/peeyushcodes/windows-developer-mcp/actions) [](LICENSE) [](https://python.org) [](https://github.com/jlowin/fastmcp) [](https://github.com/astral-sh/ruff) [](https://github.com/detachhead/basedpyright) **Windows Developer MCP** gives AI assistants (**Claude Desktop**, **LM Studio**, **Cursor**, etc.) safe, native developer superpowers on Windows — including terminal execution, Git/GitHub integration, Docker management, filesystem operations, and AI project diagnostics. --- ## ⚡ 1-Minute Quick Start ### Step 1: Install `uv` If you don't have `uv` installed, open PowerShell and run: ```powershell powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex" ``` ### Step 2: Configure Your AI Client #### 🤖 Claude Desktop Setup Edit `%APPDATA%\Claude\claude_desktop_config.json`: ```json { "mcpServers": { "windows-developer-mcp": { "command": "uv", "args": [ "--directory", "C:\\path\\to\\windows-developer-mcp", "run", "windows-developer-mcp" ], "env": { "MCP_SERVER__PROFILE": "developer", "MCP_WORKSPACE__PATH": "C:\\path\\to\\your\\project" } }…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.