agy-agent-mcp
Related Servers
Alternatives to agy-agent-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables a local Codex chat to ask a second opinion, review staged, unstaged, or revision-based diffs, and delegate coding tasks to the Antigravity CLI running in isolated or disposable workspaces. Supports starting, polling, retrieving, and cancelling tasks with returned answers, diffs, changed-file lists, exit codes, and time/output limits, while never auto-applying returned patches.81MIT
- AlicenseBqualityAmaintenanceEnables delegating coding tasks to the official Antigravity CLI from any MCP client, with task listing, model selection, streamed event tracking, cancellation, and resumable sessions. Runs each task against an isolated copy of the repository so results can be previewed, tested, and only integrated into the original after explicit user confirmation.2363 npmMIT
- AlicenseAqualityCmaintenanceEnables AI harnesses to delegate code analysis, modification, testing, and long-running tasks to the locally installed Antigravity CLI via stdio MCP, with job status tracking and conversation continuity.3MIT
- 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.14 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables STDIO-compatible AI assistants to queue coding work onto the official Google Antigravity CLI and track status, read reports or patches, query capabilities, or cancel running tasks without blocking. Supports trusted direct execution plus optional isolated or read-only modes depending on the platform.MIT
- 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 5 tools
Each tool has a clearly distinct purpose: general_task (writable coding delegation) vs explore_task (read-only plan mode) are separated by their mode posture, watch_task tails transcripts, and list_models/list_agents are unambiguous lookup helpers. No two tools compete for the same action.
All five names use snake_case with a consistent verb/noun shape (general_task, explore_task, watch_task, list_models, list_agents). The two list_* helpers and three *_task delegation tools form a predictable pattern.
Five tools is well-scoped for a delegation server: two delegation entry points, one monitoring tool, and two parameter-lookup helpers. Every tool earns its place with no redundant surface.
The core lifecycle of delegating, exploring, and observing tasks is covered, and resumable conversation_id implies continuation. However there is no explicit cancel/abort tool for an in-flight run and no task history/listing beyond 'latest run', which are minor but real gaps.