Skip to main content
Glama
segentic-lab

glovebox-mcp

by segentic-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to glovebox-mcp

No user-submitted related servers found.

    Related Servers

    • taw-computer

      tawgroup
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that provides AI agents with a full Ubuntu desktop environment inside Docker, enabling them to perform complex computer tasks like browsing, coding, testing, and GUI automation.
      36
      9
      MIT

    • luda

      0xpolarzero
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that gives AI agents local Linux desktop control through tools for screenshots, accessibility, mouse, keyboard, and reliable text input.
      36
      MIT

    • Secure Browser MCP

      pranavgawasproject
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI clients controlled access to a real headless browser with domain allowlisting, SSRF protection, per-session isolation, audit logging, and persistent cookies/state across restarts.
      2 npm
      MIT

    • Local Browser MCP

      nolanbaxter
      A
      license
      B
      quality
      A
      maintenance
      A headless, agent-controllable real browser as an MCP server that enables AI agents to navigate, click, fill, eval JavaScript, and take screenshots on localhost and allowed hosts, with no GUI required.
      27
      4
      MIT

    • computer-use-mcp

      yangweijie
      A
      license
      Not graded
      quality
      C
      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.
      362 npm
      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

    A4.4/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool has a distinct, well-defined purpose. Clicking, dragging, scrolling, typing, parsing, etc. are all separate actions without overlap. Even similar tools like click and click_element are differentiated by coordinate vs element id.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (click_element, launch_app, type_text), but a few are just verbs (click, drag, scroll, screenshot, status). However, the pattern is still readable and predictable.

    Tool Count5/5

    19 tools is well-scoped for a GUI automation server. It covers launching, controlling, inspecting, and managing instances without being overly large or too minimal.

    Completeness5/5

    The tool set covers the full lifecycle: create/close instances, list them, interact via clicks, keys, type, scroll, drag, parse screen, get screenshots, handle files, and upload. No obvious gaps for typical automation tasks.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources