Skip to main content
Glama
Sign In
coeus

coeus

Official
by soryko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to coeus

No user-submitted related servers found.

    Related Servers

    • Agent Harness Kit

      Suzuki1440
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding providers to run structured multi-agent workflows with document-backed specifications, tracked tasks, handoffs, health gates, and completion evidence. It exposes MCP tools for coordinating use cases, specs, implementation, review, and repair across supported providers.
      29 npm
      MIT

    • WhenLabs/When

      WhenLabs-org
      A
      license
      A
      quality
      D
      maintenance
      A 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.
      7
      4
      MIT

    • Foundry MCP

      foundry-works
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      4
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.6/5.0

    Scored across 59 tools

    Disambiguation2/5

    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.

    Naming Consistency3/5

    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.

    Tool Count1/5

    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.

    Completeness3/5

    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.

    Resources