Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Open-source Windows MCP server for AI assistants. File, clipboard, screenshot, process & power mgmt.
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.
The maker has not listed install details in the registry. See the maker’s README below.
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 7, 2026
The registry name was verified with the GitHub account codyard, which owns the repo
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 (0.5.0) reached the registry 9 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code.
In the same category: Spec Driven Development, Remote Desktop Commander, MCP Server Autocad Lisp Helper
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.
High-precision static analysis and debug server for AutoCAD AutoLISP (.lsp) files.
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.
中文文档
WinBridgeAgent is an open-source Windows local capability service that implements the Model Context Protocol (MCP) standard, providing traceable Windows system operations for AI assistants such as Claude Desktop, OpenAI, etc.
In addition to the open-source edition, WinBridgeAgent Pro is now available as a free download.
The Pro edition is designed for users who need a more complete Windows Agent/Node experience, with ongoing improvements toward a more production-ready Windows node (closer to the OpenClaw Node experience).
Key enhancement areas (ongoing) include:
See details and download here:
+------------------------------------------------------+
| Local Area Network (LAN) | | | | +--------------------+ | | | MCP Client | | | | (OpenClaw / Agent) | | | | - LLM reasoning | | | | - Tool planning | | | +---------+----------+ | | | MCP Protocol (HTTP/SSE) | | | | | +---------v------------------------------------+ | | | Windows PC | | | | | | | | +--------------------------------------+ | | | | | WinBridgeAgent | | | | | | (Local Tray MCP Server) | | | | | | | | | | | | - MCP Server (localhost / LAN) | | | | | | - Policy & Permission Guard | | | | | | - Tool Execution Layer | | | | | | - Audit & Logging | | | | | +-----------+--------------------------+ | | | | | | | | | +--------v--------+ | | | | | Windows System | | | | | | APIs / Resources| | | | | | (FS / Screen / | | | | | | Clipboard / | | | | | | Process etc.) | | | | | +-----------------+ | | | | | | | +----------------------------------------------+ | | | +------------------------------------------------------+
Optional External Dependencies:
WinBridgeAgent is published on the MCP Registry as io.github.codyard/winbridgeagent. MCP clients that support the registry can install it directly.
WinBridgeAgent-x64.exe (64-bit) or WinBridgeAgent-x86.exe (32-bit)For OpenClaw + Windows node setup, see windows-node-install.en.md.
WinBridgeAgent works with any MCP-compatible client. Below are setup instructions for popular clients.
Note: Replace
with the IP address of the Windows PC running WinBridgeAgent (e.g.192.168.1.100). Uselocalhostonly if the MCP client runs on the same Windows machine.
Edit claude_desktop_config.json:
%APPDATA%\Claude\claude_desktop_config.json~/Library/Application Support/Claude/claude_desktop_config.json{
"mcpServers": { "winbridgeagent": { "url": "http:// :35182", "transport": "http" } } }
winbridgeagenthttphttp:// :35182Or edit .cursor/mcp.json in your project root:
{
"mcpServers": { "winbridgeagent": { "url": "http:// :35182", "transport": "http" } } }
Edit ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": { "winbridgeagent": { "serverUrl": "http:// :35182" } } }
winbridgeagentHTTPhttp:// :35182For a step-by-step Windows node deployment walkthrough (including mcporter pairing), see windows-node-install.en.md.
http:// :35182Edit cline_mcp_settings.json in your VS Code settings:
{
"mcpServers": { "winbridgeagent": { "url": "http:// :35182", "transportType": "http" } } }
Any MCP client that supports HTTP transport can connect using:
http:// :351822024-11-05The server listens on the configured port (default 35182).
Open-source edition: No Bearer Token authentication required. All API endpoints are directly accessible.
| Method | Path | Description |
|---|---|---|
| GET | / | API endpoint list |
| GET | /health | Health check |
| GET | /status | Server status and info |
| GET | /disks | List all disk drives |
| GET | /list?path= | List directory contents |
| GET | /read?path= | Read file content |
| GET | /search?path= &query= | Search file content |
| GET | /clipboard | Read clipboard |
| PUT | /clipboard | Write clipboard |
| GET | /screenshot | Take screenshot |
| GET | /windows | List all windows |
| GET | /processes | List all processes |
| POST | /execute | Execute command |
| GET | /exit | Shutdown server |
| POST | /mcp/initialize | MCP initialize |
| POST | /mcp/tools/list | MCP list tools |
| POST | /mcp/tools/call | MCP call tool |
Replace
below with the actual IP of your Windows PC (or uselocalhostif testing on the same machine).
# Server status
curl http:// :35182/health
curl http:// :35182/disks
curl "http:// :35182/list?path=C:\\"
curl "http:// :35182/read?path=C:\\test.txt"
curl "http:// :35182/search?path=C:\\test.txt&query=keyword"
curl http:// :35182/clipboard
curl -X PUT -H "Content-Type: application/json" \ -d '{"content":"Hello World"}' http:// :35182/clipboard
curl http:// :35182/screenshot
curl http:// :35182/windows
curl http:// :35182/processes
curl -X POST -H "Content-Type: application/json" \ -d '{"command":"echo Hello"}' http:// :35182/execute
curl -X POST -H "Content-Type: application/json" \ -d '{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}' \ http:// :35182/mcp/initialize
curl -X POST -H "Content-Type: application/json" \ -d '{}' http:// :35182/mcp/tools/list
curl -X POST -H "Content-Type: application/json" \ -d '{"name":"list_windows","arguments":{}}' \ http:// :35182/mcp/tools/call
curl http:// :35182/exit
If you have multiple computers with WinBridgeAgent installed on your LAN, configure your MCP client to manage them:
{
"mcpServers": { "winbridge-test": { "url": "http://192.168.31.3:35182", "description": "Test PC" }, "winbridge-office": { "url": "http://192.168.31.4:35182", "description": "Office PC" } } }
See [Multi-Computer Setup Guide](docs/MULTI_COMPUTER_
Only the beginning is shown; read the rest in the repo