Skip to content
Ennodia Ennodia

Quickstart

This page gives manual installation instructions for a Model Context Protocol (MCP) client. To use an agent for installation and configuration, see Installation for Agents.

Requirements

Section titled “Requirements”
  • Bun 1.3.14 or newer
  • An MCP client that can launch a standard input/output (stdio) server
  • At least one supported artificial intelligence (AI) command-line tool for real agent execution

See Supported Harnesses.

Install from npm

Section titled “Install from npm”

Install the stable release from npm:

Terminal window
npx -y ennodia

Ennodia requires Bun 1.3.14 or newer. npx downloads Ennodia. Bun runs it. To use Bun directly, run bunx ennodia.

The JSR package @cherninlab/ennodia exposes TypeScript modules for import. Use the npm package for the stdio MCP executable.

Local Checkout

Section titled “Local Checkout”

Use a checkout to modify Ennodia:

Terminal window
git clone https://github.com/cherninlab/ennodia
cd ennodia
bun install
bun run verify

MCP Client Config

Section titled “MCP Client Config”
{
  "mcpServers": {
    "ennodia": {
      "command": "npx",
      "args": ["-y", "ennodia"]
    }
  }
}

For a local checkout, use the source file:

{
  "mcpServers": {
    "ennodia": {
      "command": "bun",
      "args": ["run", "/absolute/path/to/ennodia/src/cli.ts"]
    }
  }
}

Replace /absolute/path/to/ennodia with your local repository path.

First Checks

Section titled “First Checks”

From the repository:

Terminal window
bun install
bun run mcp:smoke
bun run verify

From an MCP client, call ennodia_list_harnesses. Then call ennodia_estimate_budget. To inspect the route, call ennodia_plan.

Start the work with ennodia_run. This tool plans the route and starts the selected tasks. It can also compare successful outputs. It returns a run identifier (ID).

Poll ennodia_get_run with that ID. Stop when the status is succeeded, failed, or cancelled.

Expect real runs to take minutes. Compare adds a Judge pass and a Result Advisor pass after child agents finish.

Optional Team Advice

Section titled “Optional Team Advice”

For a proposed work split, call ennodia_start_plan_advice. The Plan Advisor proposes explicit harness, model, and skill assignments. It cannot execute them.

Poll ennodia_get_plan_advice. Stop when the status is ready, consumed, invalid, failed, or cancelled.

Ennodia parses the response as strict plan data. It validates the data against the frozen harness, model, and skill inventory.

To start a ready plan once, call ennodia_start_advised_plan. Pass the returned planDigest as expectedPlanDigest. Ennodia validates the current inventory and budget again before authorizing the plan. A mismatch stops the operation before any worker task starts. Authorization consumes the advice, so a second launch with the same advice fails before any worker task starts.

Compare is a separate operation after worker completion. The Judge maps the completed answers. Then the Result Advisor recommends one answer.

If Judge analysis is not available, the Result Advisor can use only the candidate outputs. The Compare result shows this condition.

Next Pages

Section titled “Next Pages”

Expected Behavior

Section titled “Expected Behavior”

An Ennodia run is visible. You can inspect:

  • selected harnesses
  • child task IDs
  • task status
  • standard output (stdout) and standard error (stderr) previews
  • elapsed time and per-task timeout
  • Compare state, if Compare was used
  • final answer or explicit failure reason

If a child tool times out or fails, Ennodia must report that state. It must not conceal the failure.