sub-antigravity
Related Servers
Alternatives to sub-antigravity
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients such as Claude Code, Codex, and Cursor to dispatch background subagent jobs to the Antigravity IDE's local agent engine and collect results asynchronously. Jobs run through the IDE's authenticated session without an API key, with optional Gemini REST fallback and on-disk job history.6MIT
- AlicenseNot gradedqualityFmaintenanceEnables MCP-compatible clients like Codex to delegate tasks to the Antigravity CLI, using ConPTY on Windows to reliably capture responses.2MIT
- AlicenseBqualityAmaintenanceAn MCP bridge that lets Codex delegate long-running agent work to the Antigravity CLI, providing observable and resumable tool-based execution with project scoping.14177 PyPI11MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible coding agents to run the local Antigravity CLI as a coding agent, manage conversation context and common options, and inspect usage, quota, models, version, help, and read-only slash commands.17 npmMIT
- AlicenseAqualityBmaintenanceLets MCP clients delegate tasks to the Google Antigravity CLI, including starting and continuing conversations and listing models, while returning structured results over stdio.327 npmApache 2.0
- FlicenseNot gradedqualityCmaintenanceActs as a local stdio MCP service that lets Codex delegate implementation tasks to Antigravity CLI while conserving tokens; it returns compact review packets with changed files, diff stats, and run history for Codex to review and iterate.-
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: delegate starts a job, job manages a running or completed job, and check inspects environment configuration. There is no meaningful overlap in purpose.
All tools share the antigravity_ prefix and use snake_case, but antigravity_job breaks the verb-led pattern established by antigravity_delegate and antigravity_check. The convention is still readable and predictable.
Three tools is a well-scoped set for a delegated job system: start, manage, and check environment. Each tool earns its place without unnecessary redundancy.
The core lifecycle of starting, waiting on, retrieving, and canceling delegated jobs is covered, along with environment discovery. A list-all-jobs operation is absent but is not clearly required for the server's stated purpose.