Skip to main content
Glama
Sign In
desktop-touch-mcp

desktop-touch-mcp

by Harusame64
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to desktop-touch-mcp

  • Glasswarp

    Glasswarpofficial

    glasswarp
    A
    license
    A
    quality
    C
    maintenance
    Allow AI agents to see and control a real Windows PC you own: observe (UIA + screenshots), click/type/drag/scroll, launch apps, owner Live View. BYOH — your machine, your key.
    16
    Apache 2.0

Related Servers

  • winauto-mcp

    PingPong2534
    F
    license
    Not graded
    quality
    B
    maintenance
    MCP server that lets an LLM see and drive any running Windows app: attach a window, screenshot it, read its UI Automation tree, and send clicks, typed text, and key presses with pixel coordinates.
    -

  • helix-pilot

    tsunamayo7
    A
    license
    Not graded
    quality
    C
    maintenance
    GUI automation MCP server that enables AI agents to see and control the Windows desktop using a local Vision LLM (Ollama), supporting screenshot analysis, mouse/keyboard actions, and autonomous task execution.
    5
    MIT

  • OpenEyes

    yangpeng366
    A
    license
    Not graded
    quality
    B
    maintenance
    MCP server providing AI-friendly computer-use primitives (capture, detect, click) to let LLM agents drive desktop GUI applications on Windows, macOS, and Linux.
    2
    MIT

  • da-mcp

    cioinside
    A
    license
    A
    quality
    C
    maintenance
    Cross-platform desktop automation MCP server that lets AI agents capture screenshots, run OCR with UI-element classification, control mouse/keyboard, and launch programs on Linux, macOS, and Windows.
    20
    1
    MIT

  • pywinauto-mcp

    sandraschi
    A
    license
    Not graded
    quality
    A
    maintenance
    A Windows computer use agent — FastMCP server that gives AI assistants hands on the real desktop: windows, UI elements, mouse, keyboard, screenshots, OCR, shortcuts, dialogs, and outcome verification.
    52
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 30 tools

Disambiguation4/5

Most tools have clearly separated contexts: browser_click targets DOM elements, click_element uses UIA in native apps, and mouse_click uses screen coordinates. However, browser_locate, browser_search, browser_overview, screenshot, and workspace_snapshot overlap around discovery/observation, and the set still relies heavily on lengthy descriptions to prevent misselection.

Naming Consistency3/5

There is a recognizable browser_* prefix and some verb_noun names like focus_window, click_element, and notification_show, but many tools are bare nouns such as keyboard, clipboard, terminal, excel, and scroll. The convention is mixed, though still generally readable.

Tool Count2/5

At 30 tools, the set is large for a desktop automation server and includes many narrow variants. Several tools could likely be consolidated, especially around screenshot management, browser discovery, and observation, making the surface feel heavy.

Completeness4/5

Coverage is broad: browser automation, native UIA interaction, terminal control, clipboard, screenshots, waiting/macros, credentials, and Excel VBA are all represented. Minor gaps remain, notably missing explicit native discovery/set-value tools referenced by descriptions, limited browser tab management, and a narrow Excel API beyond VBA.

Maintenance

ActivityActive
ResponsivenessUsually handled

Resources