Skip to main content
Kernel CLI runs as a stdio MCP server. MCP is an access path over the same OS capabilities as the CLI, not a second automation engine.

Canonical MCP reference

The current setup command, safety boundary, raw-tool model, and computer_use facade are maintained in the Kernel CLI reference.

Start the Server

Use the mcp subcommand:
Client configuration:
Direct kernel-cli mcp is raw capability. Mutating tools do not inherit the NIIA OTP gate merely because they are called through MCP.

Two Tool Shapes

Start with MCP health_report to inspect the live permission and capability state. Use raw targets and act when precise Kernel CLI handles are the right contract. The computer_use facade can return structured elements alongside image content and can reuse element handles across actions. It is a compatibility surface over Kernel CLI’s capabilities: the usage shape may be familiar, but the underlying architecture remains Kernel CLI’s own.

CLI, MCP, and connector.json

connector.json can pass command results and guards between phases. The MCP facade owns MCP-specific element tokens. NIIA owns human authorization. These contracts complement one another; they are not interchangeable.

Recording

Kernel CLI can record mutating MCP tool calls for audit and controlled replay. That trajectory is not a video. Add a visual recorder separately when the proof must include on-screen pixels.

Continue Reading

Kernel CLI Reference

MCP setup, tool shapes, health reporting, recording, and raw-capability safety.

Kernel CLI Workflows

Configure a client and choose between raw tools and the compatibility facade.