Skip to main content
Glama
cherninlab

Ennodia

Official
by cherninlab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Ennodia

No user-submitted related servers found.

    Related Servers

    • agentloop

      luckeyfaraday
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI agents to run a deterministic orchestration loop with decomposition, subagent execution, and review feedback across multiple LLM backends.
      60
      MIT

    • Agent Harness Kit

      Busra530
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a provider-agnostic MCP server that runs structured multi-agent workflows by owning task claims, action logs, handoffs, and server-side health gates over a shared filesystem and database. It enables coordinated Explorer, Consultant, Builder, and Reviewer roles with tracked specifications and audited completion evidence.
      29 npm
      MIT

    • Agent Harness Kit

      Ngoc7225
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a provider-agnostic MCP server that coordinates structured multi-agent workflows, owning task claims, action logs, handoffs, and server-side health gates for coding agents. It enables tracked specs, tasks, reviews, and verified completion across Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode.
      29 npm
      MIT

    • moo-tasks

      shekarsiri
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for agentic task orchestration and management, enabling AI agents to create goals, plan tasks with acceptance criteria, track dependencies, request human input, and provide proof of completion.
      20 npm
      3
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct lifecycle role: list_harnesses/list_skills are discovery, run starts work, get_run reads status, history reads past receipts, cancel_run stops work. The only mild overlap is get_run vs history (live vs persisted) and run vs list_harnesses routing guidance, but descriptions clarify these boundaries.

    Naming Consistency4/5

    All tools use the ennodia_ prefix with snake_case verb_noun naming, which is highly consistent. Minor deviation: ennodia_run is a bare verb with no noun, while others include an object (enumodia_list_harnesses, ennodia_get_run).

    Tool Count5/5

    Six tools is well-scoped for an orchestration server, covering discovery, execution, polling, history, and cancellation without redundancy. Each tool earns its place in the run lifecycle.

    Completeness4/5

    The lifecycle is well covered: discover harnesses/skills, start run, poll, cancel, and read history. Minor gap: no explicit tool for listing or retrieving an in-progress run's result beyond polling, but get_run with waitMs handles terminal results adequately.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources