antigravity-workers
Related Servers
Alternatives to antigravity-workers
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables Codex to delegate bounded tasks to multiple AI model workers through a persistent OpenCode 2 service, with isolated Git worktrees and safe patch review and application.-
- AlicenseNot gradedqualityBmaintenanceEnables delegating bounded tasks from Codex to Claude Code, including read-only reviews, isolated branch edits, long-running background work, and approval handling.184 npmMIT
- AlicenseAqualityAmaintenanceEnables Claude Code and Claude Desktop to delegate token-heavy tasks to Antigravity headless subagents, offloading file edits, test runs, and exploration while preserving Claude's context window.1217 npm1MIT
- AlicenseAqualityCmaintenanceEnables Claude to delegate tasks to external coding agents (Codex or Antigravity) for independent reviews, separate quota usage, and async processing.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables Codex to offload expensive code reading, editing, and checking to a worker agent via Claude Code, supporting async jobs and long-running tasks.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to delegate complex coding tasks, refactorings, and automated code reviews to OpenAI Codex and Google Antigravity CLIs, running them autonomously in YOLO mode with process supervision.6MIT
TDQS
Scored across 23 tools
Most tools are clearly separated by domain (account, models, media, runs, teams), but start_media_analysis vs start_analysis vs start_review vs start_edit could cause some confusion since all are 'start' actions on different worker types. The descriptions help distinguish them, though the media vs analysis boundary is slightly less obvious.
The naming is mostly consistent with verb_noun patterns: get_account, list_models, start_analysis, get_run, cancel_run, apply_run. Minor deviations exist: 'doctor' is a noun-only command, and 'team_dashboard' is noun-first rather than verb_noun, but the overall pattern is predictable.
23 tools is on the higher end but appropriate for a server covering account info, model listing, media generation/analysis, async runs, and multi-agent teams. Each tool serves a distinct operational purpose, though a few could be consolidated (e.g., team_dashboard vs get_team).
The surface covers the main lifecycle: starting runs, reading runs, continuing, cancelling, and applying edits; teams can be started, read, messaged, cancelled, and resumed. Minor gaps include no explicit tool for listing models' details beyond routes, no media cancellation, and no direct team result artifact listing, but core workflows are covered.