F
licenseNot graded
qualityC
maintenanceEnables autonomous coding agents to inspect Git commits, create pull requests, parse issue threads, and post reviews on GitHub repositories.
-
flotilla-mcp
Related Servers
Alternatives to flotilla-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceAn autonomous agent that automates GitHub contributions end-to-end, from issue analysis and code changes to pull requests, conflict resolution, and review updates.173Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to automate GitHub repository management, issue tracking, and commits using natural language.6 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to perform scoped, policy-enforced GitHub operations with allowlisted repositories and tools, protected branches, approval gates, dry runs, secret redaction, and a tamper-evident audit log.MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to orchestrate the full software development lifecycle on GitHub, including planning, issue creation, code review, security triage, and release readiness checks.1377 npm1MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to safely inspect, edit, and test code within a bounded repository environment to solve software engineering tasks and verify fixes.-
TDQS
A4.4/5.0
Scored across 7 tools
Disambiguation5/5
Each tool owns a distinct stage of the issue-to-PR workflow: discovery, workspace setup, file read/write, test execution, PR submission, and CI status. There is no meaningful overlap between read_file and write_file or between run_tests and check_pr_status.
Naming Consistency5/5
All seven tools follow a consistent snake_case verb_noun pattern: start_issue, read_file, write_file, run_tests, list_assigned_issues, submit_pr, check_pr_status. The naming is predictable and immediately signals what each tool does.
Tool Count5/5
Seven tools is well-scoped for the server's stated purpose of working through GitHub issues from discovery to PR submission. Each tool earns its place and there are no redundant or filler entries.
Completeness3/5
The core workflow is covered: discover issues, start an isolated workspace, edit files, run tests, submit a PR, and check CI status. However, there is no way to read issue bodies/comments or list the workspace directory structure, which leaves notable gaps for agents that need to understand requirements or navigate an unfamiliar repository. There is also no explicit abort/discard tool for abandoning work.
Maintenance
ActivitySlowing
ResponsivenessSyncing