What problem does it solve? Container agents in NanoClaw cannot call local models running in the Atomic Chat desktop app, forcing all work through the primary LLM even when a cheaper local model would suffice. ## Core Features & Use Cases - MCP Server Registration: Copies a stdio-based MCP server into the agent-runner tree and registers it in index.ts so the agent gains atomic_chat_list_models and atomic_chat_generate tools. - Env Forwarding: Adds a host-side helper that passes ATOMIC_CHAT_HOST and ATOMIC_CHAT_API_KEY into the container as Docker -e arguments. - Wiring Tests: Ships structural tests that verify the registration entry and the buildContainerArgs call actually exist, catching drift when edits are removed. - Use Case: Ask the agent to "use atomic chat to summarize this document" and it lists available local models, then generates a response via Atomic Chat's OpenAI-compatible API on port 1337. ## Quick Start Ask the agent to add the Atomic Chat tool so it can call local models, then verify by sending "use atomic chat to tell me the capital of France".