Agent Loom
Related Servers
Alternatives to Agent Loom
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables ChatGPT to securely control remote development servers over OAuth-protected MCP, exposing workspace-bounded tools for file editing, command execution, Git operations, and running Codex or GitHub Copilot subagents.521 npm2MIT
- AlicenseAqualityCmaintenanceAn MCP server that splits coding work between ChatGPT web (planning, review) and Codex CLI (implementation), enabling agentic workflows over a local repo with risk-gated execution and safety rails.23MIT
- FlicenseNot gradedqualityBmaintenanceCentralized multi-project state & handoff MCP server that lets AI agents save checkpoints in one session and resume in another with minimal token overhead, including git snapshots and code-graph integration.-
- AlicenseAqualityBmaintenanceA centralized MCP hub for managing multiple coding agents across projects, enabling parallel, non-blocking dispatch and orchestration from any MCP-capable client.195MIT
- AlicenseNot gradedqualityBmaintenanceA local MCP bridge that lets ChatGPT chat mode operate the user's own computer, running project, file, and shell tasks through a local executor and returning progress and results to the conversation. It also coordinates Codex sessions (persistent or one-off) and other agent CLIs as sub-agents.MIT
- AlicenseNot gradedqualityBmaintenanceCoordinates parallel Claude Code agents on shared repositories and orchestrates multiple Claude subscriptions, enabling live session handoff, conflict detection, and remote terminal control.7 npmMIT
TDQS
Scored across 13 tools
Most tools are clearly separated by purpose: tree/search/read handle inspection, write/edit/apply_patch handle distinct modification styles, and bash/show_changes are explicitly kept apart from git/file review. The only mild overlap is between write, edit, and apply_patch, but their descriptions provide clear boundaries, and pi/codex are differentiated by agent name.
The tool names are readable and consistently lowercase/snake_case, but they mix bare verbs (write, read, edit, search), noun-like commands (tree, bash, workspace), and verb_noun forms (view_image, import_file, show_changes). This is a mixed convention rather than a predictable pattern.
Thirteen tools is a reasonable, well-scoped count for a coding workspace server. Each tool addresses a distinct operational need such as file editing, search, verification, change review, workspace routing, or persistent agent interaction, without feeling bloated.
The set covers core file operations, search, verification, change review, and persistent agent workflows well. However, there are notable gaps: no file delete/remove tool, and the workspace description references a discover capability that is not exposed in the tool list, which creates a potential dead end.