Docs / Architecture Learn
Agent Integration
How agents consume EKOS through MCP without touching source systems.
- Transports: stdio, TCP (NDJSON), Streamable HTTP. Through the web console, an agent connects to
/mcp/<tenant>/<project>with an API token; the console lists and forwards only the tools the token's role allows, and audits every call. - A per-call read scope limits what an agent sees of a project; under a restricting scope only the tools that read solely through the ledger are served.
- Tools are described with input schemas so agents know how to call them; tool descriptions steer usage (e.g. "use 2–3 keywords").
- Agents never receive credentials or raw enterprise data beyond what was compiled and redacted.
ekos_identity_reviewandekos_architecture_revieware the only ledger writes besides the gated ClickHouse audit, and they append events that cite who decided.ekos_session_note(opt-in) writes only to an inbox file, never the ledger. No tool can make a review decision, sign off or approve.
Tool catalogue: MCP Tools.