Skip to main content
Glama
Sign In
codex-computer-use-mcp

codex-computer-use-mcp

by tmustier
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to codex-computer-use-mcp

No user-submitted related servers found.

    Related Servers

    • Klyk

      legetdev
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI agents real OS-level control of macOS, enabling them to click real buttons, type real keys, and observe rendered screens just like a human would.
      1
      MIT

    • openchatx-mcp

      WealthyV
      A
      license
      Not graded
      quality
      B
      maintenance
      Turns ChatGPT into a local agent runtime on macOS, enabling shell execution, file editing, MCP server aggregation, tool discovery, and provider-backed subagents through a single MCP connection.
      394
      MIT

    • Mac MCP

      bulutarkan
      A
      license
      Not graded
      quality
      A
      maintenance
      Open-source, local macOS MCP server for AI agents. Automate background Safari/Chrome tabs, native apps, files and shell with scoped permissions, optional approvals and delegated coding agents.
      96
      MIT

    • open-subagent-mcp

      g2zz
      A
      license
      A
      quality
      D
      maintenance
      A local MCP server that delegates tasks to a subagent runtime via OpenAI-compatible interfaces, enabling file operations, command execution, and rollback of local file changes.
      5
      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

    C2.6/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have largely separable roles: js executes JavaScript in the persistent session, js_reset clears that session state, and computer_use_status reports readiness. js and js_reset are adjacent but the reset semantics are clear enough that misselection is unlikely.

    Naming Consistency3/5

    Names mix a bare noun (js) with a prefixed snake_case pair (js_reset) and a differently-prefixed tool (computer_use_status), so there is no single predictable verb_noun pattern. Each name is still readable on its own.

    Tool Count3/5

    Three tools is thin for a computer-use automation server, and two of them are essentially session plumbing around one general-purpose JS evaluation escape hatch. It is defensible as a minimal surface but feels under-built.

    Completeness3/5

    The generic js tool can reach almost any operation, but there is no way to set codexPath or trigger installation/recovery even though the descriptions explicitly tell users to edit config.json manually. Status is read-only, so the 'not ready' dead end has no in-band fix.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources