coeus
OfficialRelated Servers
Alternatives to coeus
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA unified developer toolkit for AI-assisted workflows. Task timing, doc drift detection, env validation, secret scanning, port conflict resolution, AI context generation, and license auditing — one MCP server, one install.73MIT
- AlicenseNot gradedqualityDmaintenanceEnables spec-driven development workflows with AI assistants, providing tools for managing specification lifecycles, task dependencies, code navigation, testing, and automated reviews through a unified CLI and MCP interface.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI coding environments to enforce engineering governance through MCP tools and resources for init, check, route, and review workflows.12 npm2MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for AI DevTool workflow, exposing tools and resources for code review, repository chat, and repository operations.1-
- AlicenseNot gradedqualityAmaintenanceEnables local AI models to be used through MCP, exposing tools for coding assistance, code review, model listing, status checks, and benchmarking.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceProvides MCP tools for AI agents to classify changes into autonomous or human review lanes, and to run shadow simulations over backlogs without shipping anything.MIT
TDQS
Scored across 59 tools
Multiple tools overlap heavily: `coeus_review_bundle`, `coeus_git_diff_review`, and `coeus_review_pr` are explicit aliases of `coeus_review`, while `coeus_review_code` and the design-review pair blur boundaries further. The analyze/summarize/explain/codebase-map cluster and the diagnostics cluster (stats, healthcheck, runtime_diagnostics, capabilities) also make tool selection ambiguous. An agent would frequently need extra context to avoid picking a near-duplicate.
All tools share the `coeus_` prefix and snake_case, which keeps the set readable, but verb/noun ordering is inconsistent: `generate_commit` contrasts with `pixel_art_generate`, and review aliases use `review_pr`, `git_diff_review`, and `review_bundle` interchangeably. Noun-only names such as `stats`, `version`, and `healthcheck` add to the mixed pattern.
At 59 tools, this server far exceeds the 25+ 'too many' threshold, and much of the bulk comes from aliases and specialty pipelines like frontend design and pixel art rather than core capabilities. The core ask/model/route functionality needs only a handful of tools, so the set should be consolidated significantly.
Across its broad intended scope, the server covers many workflows: ask/route, code review, tests, refactoring, docs, planning, web fetch/search, conversations, and pixel/frontend pipelines. However, provider/model configuration operations are missing (only list and diagnostics exist), several apparent duplicates are aliases rather than new capabilities, and some workflows depend on external backends. These gaps are work-aroundable but noticeable.