aviator-mcp
Related Servers
Alternatives to aviator-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables enqueuing coding-agent branches and managing a local-first merge train with gated validation, explicit approval, and atomic Git ref updates through MCP.250 PyPI7MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to sign in, list workspaces, and inspect workspace-scoped review findings and hosted runs. It can also prepare and, after explicit user confirmation, start or rerun an existing hosted pull-request review without exposing raw diffs, full reports, artifacts, credentials, or prompt text.2 npm-
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients to list workspaces, inspect concise workspace-scoped review findings and hosted run summaries, and prepare—or, after explicit user confirmation, start or rerun—a hosted pull-request review without exposing raw diffs, artifacts, or credentials.2 npmMIT
- AlicenseCqualityCmaintenanceEnables any MCP client to triage cloud agents, projects, conversations, transcripts, pull requests, and files, including listing agents, reading transcripts, following runs, and sending follow-ups, using an API key or browser sign-in.29MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients such as editors to start and monitor missions, run the self-healing demo, list departments and blueprints, and approve tasks through the backend API. It also lets trusted departments discover and invoke explicitly granted external stdio or Streamable HTTP tools.1MIT
- FlicenseNot gradedqualityAmaintenanceEnables an MCP client to sign in and inspect workspace-scoped review findings and hosted runs, and to prepare, then start or rerun after explicit confirmation, an existing hosted code review for a pull request. It exposes only concise summaries, never raw diffs, full reports, artifacts, credentials, or prompt text.2 npm-
TDQS
Scored across 14 tools
Most tools target clearly separate concerns (queue ops, PR status, bot/batch inspection, config, analytics, pause). Minor overlap exists between get_bot_pr, get_pr_status, and get_bisection_status, all of which surface batch/bot PR information during failure investigation, and refresh_or_sync_pr bundles two distinct actions into one tool.
Nearly all tools follow a consistent snake_case verb_noun pattern (get_pr_status, list_queued_prs, queue_pr, dequeue_pr, update_config). The only deviation is the compound-verb refresh_or_sync_pr, which is readable but breaks the single-verb convention.
14 tools is well within the well-scoped 3-15 range and each tool maps to a distinct merge-queue operation. No evident filler or redundant tools.
The surface covers the core lifecycle: queue/dequeue, status inspection, bisection/batch diagnostics, repo listing, queue stats, config get/update, analytics, pause, and backport. Gaps remain around per-PR skip-line/priority options (dequeue mentions clearing them but nothing sets them) and there is no way to inspect individual PR CI checks or batch contents beyond the bot PR summary.