Skip to content

audit: no MCP / --json / programmatic interface for any CLI surface #126

@forkwright

Description

@forkwright

Context

Area

crates/akroasis/src/cli.rs + workspace MCP/JSON-RPC surface.

Severity

medium — agent-first surface contract gap.

Evidence

  • grep -rn "mcp\|jsonrpc\|json-rpc\|tower_service\|handle_request" crates/ --include="*.rs" → 0 results.
  • crates/akroasis/src/cli.rs defines no --json global flag; no machine-readable output format.
  • ~/dev/kanon/crates/basanos/standards/STANDARDS.md:939 — "--json emits the same report for agents."
  • Fleet MCP-canonical-surface policy: every CLI surface should have a programmatic equivalent (kanon#270, #251).

Conflict

Fleet standards require agent-first interfaces. The binary is purely human-targeted TTY output with no MCP server, no JSON-RPC, no --json flag.

Why it matters

Agent automation cannot drive akroasis without screen-scraping println! output. Every other fleet binary is migrating toward MCP parity (kanon, aletheia); akroasis lacks the substrate.

Done criteria

  • Add a --json flag to all CLI commands (or expose an MCP server) so agents can invoke and parse results.
  • Document which surface (HTTP/MCP/JSON CLI) is canonical for programmatic use.

Source

Kimi L1+L2 audit pipeline 2026-04-25.

Provenance

Originally filed on the kanon forge as issue #12 on 2026-04-25T20:15:18.511890323-05:00[America/Chicago]. Recovered from 2026-05-09 pre-brick restic backup. Forge URL no longer reachable post firmware brick.

Severity

P3

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions