MCP Server

Running --startup-mode mcp-stdio turns the device into a Model Context Protocol server, offering a static whitelist of read-only tools to local AI assistants.

Design

• Built on the official rmcp SDK over stdio.
• Exposes a static whitelist of read-only context tools — by construction, there are no execute, write, or control tools ("undefined means unreachable").
• There is no lcxl_diagnose tool: full AI diagnosis is orchestrated by the central signaling brain, not by a device. The MCP surface is purely read-only context for a local AI assistant; it never dials a model or captures the screen.

Why a Separate Mode?

The MCP surface is intentionally narrower than the in-session diagnostic agent. Model inference, screen capturing, and any control/execution tools are completely excluded to keep the attack surface minimal for local AI assistants.

Running It

cargo run -- --startup-mode mcp-stdio

stdout is reserved

In mcp-stdio mode, stdin/stdout carry MCP JSON-RPC. The server must never log to stdout in this mode — doing so corrupts the protocol stream.

Connecting an AI Assistant

Point any MCP-capable client at the command above as a stdio server. The client will discover the read-only context-tool whitelist; no additional configuration grants write, execute, or diagnosis access, because those tools do not exist.

See also the AI Security Model for how the MCP surface fits the overall trust boundary.