video1.0<iframe src="https://www.loom.com/embed/53ed60793dba447591b062ddd121a298" frameborder="0" width="1620" height="1215" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>12151620Loomhttps://www.loom.com12151620https://cdn.loom.com/sessions/thumbnails/53ed60793dba447591b062ddd121a298-00769bb8f9165971.gif698.965This Loom demonstrates using an MCP server as a safer alternative to Odoo XMLRPC API keys for agentic workflows. It explains that Odoo API keys are bound to users and can be risky for agents, so an organization-wide connector authenticates via Entra and routes requests through an MCP server that declares what an agent can do. The demo shows registering an Odoo API key via a key vault, uploading a spreadsheet with 25 tasks, and having Claude create and then mark all tasks as complete. It also highlights configurable gatekeeping at the MCP level, including enabling read, create, and update for tasks while restricting delete, plus limiting other model actions.