agy-profiles
Related Servers
Alternatives to agy-profiles
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to launch, supervise, inspect, cancel, and clean up autonomous coding jobs executed by the Google Antigravity CLI in isolated git worktrees and branches, with optional verification, review, and security auditing.Apache 2.0
- AlicenseBqualityBmaintenanceEnables MCP clients such as Claude Code and Cursor to delegate long multi-step coding tasks to Google Antigravity CLI, generate read-only plans and code reviews, digest large codebases, and manage background sessions in isolated git worktrees.1543 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to securely inspect, modify, and manage local projects with trusted filesystem access, safe Git operations, controlled task execution, and developer runtime process management over stdio or HTTP.4Apache 2.0
- AlicenseAqualityBmaintenanceWraps Google Antigravity CLI into 11 typed MCP tools, enabling any MCP client to invoke agy for code review, prototyping, execution, and long-running tasks.1173 PyPI26MIT
- AlicenseNot gradedqualityBmaintenanceEnables Codex or Claude Code to orchestrate persistent Antigravity CLI workers as independent implementers and testers within restricted workspace roots. It supports asynchronous task dispatch, progress polling, result inspection, follow-up messages, and cancellation with bounded, audited local event logging.34 npm4MIT
TDQS
Scored across 13 tools
Profile lifecycle operations are clearly distinct: list, inspect, create, update, launch, stop, repair, clone, delete. Launcher build/remove are separate macOS app management tools. The only mild overlap is system_doctor versus obligations_verify, both diagnostic/security-oriented, but their descriptions distinguish host inspection from security control self-checks.
All tools use snake_case and a predictable resource_action pattern: profile_*, launcher_*, system_doctor, obligations_verify. The convention is consistent across the entire set and easy to parse.
13 tools is well within a reasonable range for a sandbox profile management server. Each tool covers a distinct lifecycle, launcher, or diagnostic responsibility, with no obviously redundant entries.
The surface covers full profile lifecycle: list, inspect, create, update, launch, stop, repair, clone, and delete. Launcher creation/removal and system/security verification are also included, leaving no obvious CRUD or operational gaps.