Antigravity MCP Orchestrator
Related Servers
Alternatives to Antigravity MCP Orchestrator
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceActs 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.1-
- 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.82 npm220MIT
- AlicenseNot gradedqualityCmaintenanceExposes a secure OAuth2 + SSE Model Context Protocol endpoint that lets Gemini Web read a local project's files, directory trees, search results, git status/diffs, and workspace info on a read-only basis. It also pairs the browser-side automation with a local bridge daemon so prompts and answers flow both ways between Gemini Web and Google Antigravity.MIT
- AlicenseNot gradedqualityFmaintenanceBridges AI agents to a gcontext workspace in the cloud, enabling file and folder management while keeping secret values and script execution local.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Gemini Spark to securely read, edit, and search a selected local workspace, execute shell commands, and integrate development tools via MCP with user approval safeguards.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Desktop to execute tasks via the Google Antigravity CLI (agy), exposing its models, skills, plugins, and background workers as native tools.9MIT
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.