OpenMouse MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mouse_moveA | Move the active mouse cursor along a human-like curved path. Browser coordinates use CSS viewport pixels; Windows coordinates use physical desktop pixels. Out-of-range move targets are clamped to the surface. |
| mouse_clickA | Move to x/y if supplied, then perform one left/right click or a left double click. |
| mouse_dragA | Drag from one point to another using a human-like curved path. |
| mouse_scrollA | Scroll up or down at the current cursor location. One click is one wheel notch. |
| mouse_positionA | Read the current virtual browser cursor or real Windows cursor position. |
| mouse_screenshotA | Capture the active local browser tab, the cloud browser, or the full Windows desktop. The text content includes image/viewport dimensions and the coordinate space. Use that metadata to map a visual target into mouse tool coordinates. |
| computer_observeA | Capture the active desktop/browser and return richer context. On Windows this includes the active window, taskbar rectangles, monitors and visible application windows. Use this before visual targeting and again for verification. |
| browser_openA | Fast path for opening a known http:// or https:// URL. On Windows this launches the default browser, Edge, or Chrome directly without screenshots or mouse movement. In cloud mode it navigates the embedded Playwright browser and blocks private addresses by default. |
| app_openA | Fast path for local applications. Focuses an existing running window, or launches a known executable/Start Menu application. Supports aliases such as feishu, notepad, explorer, cmd, powershell, calculator, edge, and chrome. |
| mouse_stopA | Immediately cancel the current mouse action, drain queued mouse actions, release held buttons, and send stop to the browser companion. |
| mouse_statusA | Read automatic routing state, browser companion freshness, viewport, platform, and consecutive failure count. This does not move the mouse. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools are cleanly separated: browser_open vs app_open split on URL vs executable, and the mouse_* family divides cleanly into action (move/click/drag/scroll), read (position/status), and control (stop). The only real overlap is computer_observe vs mouse_screenshot, both of which capture the active desktop/browser, though descriptions differentiate structural metadata from image capture.
Eight of eleven tools follow a uniform resource_action pattern with the mouse_ prefix, and browser_open/app_open extend the same pattern to other resources. computer_observe is the one outlier in prefix family naming, but it remains readable and unambiguous.
Eleven tools sit squarely in the well-scoped range for a desktop/browser automation server. Each mouse primitive (move, click, drag, scroll, stop, position, status, screenshot) earns its place without redundancy.
The pointer surface is thorough, but there is no keyboard/typing or key-press tool, which severely limits any workflow requiring text entry, form filling, or shortcuts in the browser or apps. Browser coverage also stops at opening a URL, with no navigation, tab, or element-query operations, leaving agents at dead ends for interactive pages.