Skip to main content
Glama
Sign In
agent-bridge

agent-bridge

by MarchGho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to agent-bridge

No user-submitted related servers found.

    Related Servers

    • local-agent-mcp

      OlehHavrilko
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Code on Windows to read the foreground window's UI Automation tree as structured text and then act on it with real, human-like SendInput mouse and keyboard events. It drives desktop apps through a perceive-decide-act loop without screenshots, a vision model, or any locally hosted LLM.
      MIT

    • NexusWindows for Claude

      pironjulien
      A
      license
      A
      quality
      F
      maintenance
      Lets Claude Desktop and Claude Code inspect and drive Windows desktop applications in the background, including clicking, typing, launching, and verifying results, while the user keeps their mouse, keyboard, and foreground window.
      7
      176 PyPI
      4
      MIT

    • chatgpt-desktop-mcp

      kevinrss01
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables other agents to list, read, start, and steer Codex chats in the macOS ChatGPT desktop app, including sending follow-ups, choosing model/reasoning/speed, interrupting work, and answering approvals. It can run locally or behind bearer-token-protected tunnels for remote monitoring and control.
      40 npm
      MIT

    • win-computer-use

      Regigicas
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables Claude Code to control a Windows desktop via screenshots, mouse, keyboard, and window/display enumeration, reusing the native binding from the Claude desktop app.
      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.6/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a distinct resource+action: list_projects vs list_chats vs read_chat are clearly layered by scope, and send_message/wait_reply form a complementary pair rather than overlapping. codex_goal and codex_generate_image are Codex-specific but clearly named, though a few tools (read_chat vs list_chats) require reading descriptions to fully separate.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (list_projects, list_chats, read_chat, send_message, wait_reply). The codex_* prefix on codex_goal and codex_generate_image is a sensible namespace convention rather than a break, giving mostly consistent naming.

    Tool Count5/5

    7 tools is well-scoped for an agent-bridge: it covers discovery, messaging, waiting, and two Codex-specific extras without bloat. Each tool earns its place in the bridging workflow.

    Completeness4/5

    Core lifecycle is covered: list projects/chats, read, send, wait for reply, plus goal control and image generation. Creation is implicitly handled by send_message with an empty chat, but there is no explicit project creation, chat deletion/close, or job cancellation—minor gaps agents can mostly work around.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources