chanto serve exposes sessions and background runs over HTTP with server-sent events, so other machines and scripts can drive Chanto.
The API is bound to 127.0.0.1 by default and every route except /health requires Authorization: Bearer <token> (the scheme name is case-insensitive, as for every Chanto server: bearer works too) (the token is written to ~/.chanto/server.json, mode 600). Set CHANTO_SERVER_TOKEN to pin it, or CHANTO_SERVER_TOKEN_FILE to a file that holds the token (for systemd LoadCredential= and Docker/Compose secrets, so it never sits in the environment).
As an MCP server
chanto mcp-serve runs Chanto as an MCP server over stdio, so Claude Code, Codex, Cursor or any MCP client can hand it coding tasks. It offers two tools: chanto (run a task; returns the answer and a sessionId) and chanto_reply (continue that session). Verified mode is on by default, so a task only comes back "done" once the project's checks pass. Approvals can't be asked for over MCP: actions needing one are refused unless the call's mode (default acceptEdits) or your allow rules permit them. Tool activity is sent as progress notifications, and cancelling the call stops the agent.
claude mcp add chanto -- chanto mcp-serve --model qwen3:8b