Precision MCP Server

Fixes DPI coordinate scaling for Windows desktop automation MCP servers. Exposed over MCP by the precision mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Windows DPI scaling silently breaks every MCP tool that clicks, types, or hovers on the desktop. precision-desktop detects and corrects the coordinate mismatch so your AI agent's clicks actually land where they should.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Its toolset

Everything the assistant can do here goes through one of these:

• calibrate — Compute DPI scale factors from 2+ reference points with known physical and logical coordinates
• calibrate_verify — Mark calibration as verified after confirming a test click landed correctly
• get_calibration — Read current calibration state (scale factors, verification status, age)
• convert_coordinates — Convert a coordinate pair between physical and logical systems
• find_ui_element — Find a single UI element by name using Windows UI Automation. Returns physical coordinates
• find_all_ui_elements — Find all UI elements matching a name. Returns list with physical coordinates
• list_ui_elements — List all named interactive elements (buttons, text fields, etc.) in a window
• find_window — Find a window handle (hwnd) by title substring
• health_check — Run environment checks: calibration freshness, UI Automation, companion MCP status
• patch_status — Check which DPI-aware patches are applied to the companion MCP
• Verification — After calibration, the agent should: 1. Use convert_coordinates to convert a known logical position to physical 2. Use Move-Tool to move the cursor
• Discovery — Don't know the element name? Use list_ui_elements to see what's available:

Configuration

You will need one environment variable: WINDOWS_MCP_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Windows 10/11 (uses Windows UI Automation) - Python 3.10+ - PowerShell (ships with Windows) - mcp >= 1.0.0 (MCP SDK) - MPos or similar coordinate reader (for calibration) — any tool that shows the cursor's screen position in both physical and logical coordinates. MPos is lightweight and portable (no

Caveats

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

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Precision's toolset — calibrate, calibrate_verify, get_calibration and 9 more — is a fair guide to whether it matches your workflow. It is maintained by ikoskela; 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.