WinBridgeAgent MCP Server

Open-source Windows MCP server for AI assistants. File, clipboard, screenshot, process & power mgmt.

Local serverstdio

What is the WinBridgeAgent MCP server?

Most browser automation work still happens through a UI a human drives. WinBridgeAgent MCP server moves it into the conversation instead. Open-source Windows MCP server for AI assistants. File, clipboard, screenshot, process & power mgmt.

The short version

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.

The tools it exposes

The server publishes 8 tools. What each one is for:

  • Core — The Core tool exposed by this server
  • Cursor — 1. Open SettingsMCP 2. Click Add new MCP server 3. Fill in: - Name: winbridgeagent - Type: http - URL
  • Windsurf — The Windsurf tool exposed by this server
  • OpenClaw — 1. Open SettingsMCP Servers 2. Click Add 3. Set: - Name: winbridgeagent - Transport: HTTP - URL: http://:35182
  • Endpoints — The Endpoints tool exposed by this server
  • Examples — The Examples tool exposed by this server
  • Prerequisites — The Prerequisites tool exposed by this server
  • Build — The Build tool exposed by this server

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What it needs from you

  • macOS (Apple Silicon or Intel) - CMake 3.20+ - MinGW-w64 cross-compilation toolchain

How it compares

This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. WinBridgeAgent's toolset — Core, Cursor, Windsurf and 5 more — is a fair guide to whether it matches your workflow. It is maintained by codyard; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
CoreThe Core tool exposed by this server.
Cursor1. Open **Settings** → **MCP** 2. Click **Add new MCP server** 3. Fill in: - **Name**: winbridgeagent - **Type**: http - **URL**: http://<windows-ip>:35182
WindsurfThe Windsurf tool exposed by this server.
OpenClaw1. Open **Settings** → **MCP Servers** 2. Click **Add** 3. Set: - **Name**: winbridgeagent - **Transport**: HTTP - **URL**: http://<windows-ip>:35182
EndpointsThe Endpoints tool exposed by this server.
ExamplesThe Examples tool exposed by this server.
PrerequisitesThe Prerequisites tool exposed by this server.
BuildThe Build tool exposed by this server.

How to install the WinBridgeAgent MCP server

{
    "mcpServers": {
        "winbridgeagent": {
            "url": "http://<windows-ip>:35182",
            "transport": "http"
        }
    }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • macOS (Apple Silicon or Intel) - CMake 3.20+ - MinGW-w64 cross-compilation toolchain

Example prompts to try

  • Use WinBridgeAgent to Core.
  • Use WinBridgeAgent to Cursor.
  • Use WinBridgeAgent to Windsurf.

Frequently asked questions

It connects WinBridgeAgent to MCP-compatible AI assistants such as Claude and Cursor, exposing 8 tools (Core, Cursor, Windsurf, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with WinBridgeAgent directly.