Bridge MCP Server

Visual Desktop Bridge - Give any AI full control over Windows to automate apps and inputs.

Local serverstdioPython

What is the Bridge MCP MCP server?

Bridge MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Visual Desktop Bridge - Give any AI full control over Windows to automate apps and inputs.

What you get

Bridge MCP v2.0 stores agent registrations in a persistent JSON file:

What the assistant can call

Once Bridge MCP is connected, these are the calls the assistant has available:

  • desktop — //screenshot/latest - Current screenshot
  • file — ///{path} - Read any desktop file
  • automate_desktop_task — Step-by-step task automation
  • debug_error — Interactive error debugging
  • web_automation — Playwright web workflows
  • app_launch — Launch an application
  • app_switch — Switch to open app
  • app_close — Close an application
  • app_list — List all open apps
  • click — Click at coordinates
  • double_click — Double-click
  • right_click — Right-click

Setting it up

Installation goes through your MCP client rather than a global install: point it at fastmcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Choosing this one

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. Bridge MCP's toolset — desktop, file, automate_desktop_task and 11 more — is a fair guide to whether it matches your workflow. It is maintained by BarhamAgha1; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Bridge MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • 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.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Bridge MCP.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the bridge mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
desktop//screenshot/latest - Current screenshot
file///{path} - Read any desktop file
automate_desktop_taskStep-by-step task automation
debug_errorInteractive error debugging
web_automationPlaywright web workflows
app_launchLaunch an application
app_switchSwitch to open app
app_closeClose an application
app_listList all open apps
clickClick at coordinates
double_clickDouble-click
right_clickRight-click
type_textType text
press_keyPress a key

How to install the Bridge MCP MCP server

{
  "mcpServers": {
    "bridge": {
      "command": "uvx",
      "args": ["fastmcp"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Bridge MCP to desktop.
  • Use Bridge MCP to file.
  • Use Bridge MCP to automate desktop task.

Frequently asked questions

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