Most Odoo MCP integrations I came across follow the same pattern: a separate Python process running on your machine (or in a Docker container), talking to Odoo over XML-RPC or JSON-RPC from the outside. It works, but you end up with credentials in env files, a second thing to deploy and keep alive, and no real visibility into what the AI did from inside Odoo. I wanted something different, so I built muk_mcp — an open-source addon (LGPL-3) that makes Odoo itself the MCP server. No extra process, no middleware, no RPC bridge. The /mcp endpoint lives inside the registry and runs through the same ORM as everything else. Install it, generate an MCP key from your user preferences, paste the URL into Claude Code, Claude Desktop, Cursor, Windsurf, Codex CLI, or OpenCode. The model gets 15 typed tools covering the full ORM lifecycle — model discovery, schema introspection, search, read, create, update, delete, grouped aggregation, chatter, and method execution.…