Antigravity MCP Orchestrator
Related Servers
Alternatives to Antigravity MCP Orchestrator
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables Antigravity IDE to delegate coding, debugging, and architecture work to an already logged-in Gemini, Claude, ChatGPT, or DeepSeek web session, then applies the returned changes directly to workspace files over a local WebSocket bridge.5GPL 3.0
- AlicenseCqualityBmaintenanceConnect Google Antigravity 2, VS Code, Cursor and Claude Code to Gemini Notebooks (formerly NotebookLM, both personal and Google Cloud Enterprise). Exposes 21 MCP tools for workspace notebook binding, grounded Q&A with citations, Fast and Deep Research, bi-directional file sync, and Studio artifact generation.217MIT
- FlicenseNot gradedqualityDmaintenanceActs as a programmatic bridge for the Google Antigravity Python SDK, enabling real-time AI agent swarms, bidirectional tool proxying, and Human-in-the-Loop execution safety.2-
- AlicenseNot gradedqualityBmaintenanceAntigravity Link is an MCP server and mobile companion for Google's Antigravity IDE. It captures live snapshots of the Antigravity chat UI via Chrome DevTools Protocol and serves them to a mobile web client. From your phone you can send messages, upload files, stop AI generation, switch instances, and read task/walkthrough/plan documents. Exposes 9 MCP tools and a full OpenAPI 3.1 spec.38 npm222MIT
- AlicenseNot gradedqualityCmaintenanceEnables Google Gemini to autonomously read, write, search, and patch code files and run whitelisted developer commands inside a sandboxed local workspace for edit-and-verify coding workflows.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables Codex and Claude Code to connect over an authenticated local HTTP endpoint to a logged-in Antigravity CLI, allowing shared workspace-authorized task execution and result handling without opening the Antigravity IDE.3,159 npm7MIT
TDQS
Scored across 18 tools
Each tool largely targets a distinct resource or action (plugins, skills, rules, conversations, artifacts, workspaces, commands, workflow orchestration), with clear list/get/search/create distinctions. Minor potential confusion exists between get_antigravity_status and list_known_workspaces for workspace discovery, and between list_skills and search_skills for finding skills, but boundaries are generally clear.
All tool names use a consistent snake_case verb_noun pattern: get_, list_, set_, search_, execute_, create_, orchestrate_. There are no deviations or mixed conventions.
18 tools for an orchestrator covering multiple resource types (plugins, skills, rules, conversations, artifacts, workspaces, commands, workflow) is somewhat heavy but reasonable. Each resource has a small, focused set of operations, though some list/get pairs could arguably be consolidated.
The surface provides good discovery and read coverage, plus create operations for skills and rules. However, update and delete operations are missing for skills and rules, and there is no lifecycle management for conversations, artifacts, or workspaces, leaving notable gaps for full management.