Interfaces and Core
Current Shape
Section titled “Current Shape”| Name | Status | What it means |
|---|---|---|
| Ennodia MCP | Available | The shipped MCP tool interface for agents. Use this today. |
| Ennodia Core | Available | Shared orchestration behavior behind the MCP and IO surfaces. |
Ennodia MCP
Section titled “Ennodia MCP”Ennodia MCP is the supported public surface in the current release. It exposes
tools such as ennodia_list_harnesses, ennodia_estimate_budget,
ennodia_run, ennodia_get_run, and ennodia_start_compare. Each tool is a
schema plus one Core call — nothing more.
Use MCP when a primary agent should ask installed local agent CLIs for help.
Ennodia Core
Section titled “Ennodia Core”Core is responsible for:
- discovering supported local harnesses
- planning routes with caller-provided categories or keyword fallback
- estimating preflight budgets and enforcing local caps on that estimate
- starting child tasks through thin adapters
- capturing status, output, failures, and timing
- resolving compositional slices and reporting Compare readiness
- comparing successful outputs when requested
Ennodia IO
Section titled “Ennodia IO”Ennodia IO is a local app interface. Start the HTTP server with:
npx -y @cherninlab/ennodia-ioSee Ennodia IO for supported fields, rejected features, local binding defaults, and auth behavior.