Skip to main content
Glama
Sign In
phimage

mcp-computer-use

by phimage
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-computer-use

No user-submitted related servers found.

    Related Servers

    • claude-workman

      AdvisorAGI
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to control a Linux/X11 desktop like a human: see the screen, move the mouse, click UI elements via the accessibility tree, type text, and manage windows.
      MIT

    • Tato Runtime

      ryanlcruz
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP-speaking AI agents to operate a desktop and browser through structured UI inspection, mouse/keyboard gestures, tab-scoped browsing, and approved local screen recording with editing.
      3
      1
      MIT

    • computer-use-mcp

      yangweijie
      A
      license
      Not graded
      quality
      D
      maintenance
      A framework-agnostic computer-use MCP server that exposes core desktop operations (screen capture, mouse, keyboard, and file access) as standard MCP tools, enabling any MCP-compatible agent to drive a computer.
      2,647 npm
      MIT

    • AgentDeskLink

      Takayuki-Ishimaru
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to observe and control local browsers and desktop applications over MCP, including reading UI elements and differences, capturing images, and performing permitted clicks, typing, selections, scrolling, and multi-window operations.
      16
      2
      MIT

    • Computer-Controller-Bridg

      Dobona
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients on Windows to control the local mouse, keyboard, and screen understanding via MCP stdio, allowing automated workflows like viewing the screen, locating elements, clicking, typing, and verifying results.
      1
      Apache 2.0
    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

    A4.5/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool there is no possibility of mistaking it for another tool. The tool internally distinguishes capture, click, type, scroll, and drag through its action parameter, so the surface is unambiguous.

    Naming Consistency4/5

    The single tool name 'computer_use' is clear and descriptive, though it does not follow a verb_noun pattern. There is no inconsistent naming across the set because only one name exists.

    Tool Count3/5

    One tool is borderline for such a broad domain, but it deliberately consolidates all computer-use actions behind a single action parameter. This keeps the count minimal, though splitting actions into separate tools could improve discoverability.

    Completeness4/5

    The tool covers the core GUI automation lifecycle: capture, click, type, scroll, drag, and verification via re-capture. Minor operations like explicit right-click or file upload are not named, but the overall workflow is practical and mostly complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources