agent-bridge
Related Servers
Alternatives to agent-bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceLets 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.4MIT
- AlicenseBqualityDmaintenanceEnables AI agents to control Windows desktop applications by wrapping Codex's Computer Use capability.1311MIT
- AlicenseNot gradedqualityFmaintenanceEnables 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
- AlicenseAqualityAmaintenanceEnables ChatGPT or other MCP clients to control native Codex sessions on Windows, providing tools for thread management, turns, observation, steering, and responding to approvals.739MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to see, find, and click real UI elements on Windows with sub-pixel accuracy across mixed-DPI multi-monitor setups, even in apps that expose no accessibility tree, by routing requests across Win32, UIA, OCR, and pixel/template backends. Also provides window control, clipboard and recipe-driven automation, quiet clicks that avoid moving the cursor or changing focus, and built-in setup/diagnostic tooling for Claude Code, Claude Desktop, and Codex.MIT
TDQS
Scored across 7 tools
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.
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.
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.
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.