Connect Odoo to Claude in four clicks

Name: Connect Odoo to Claude in 4 Clicks — OAuth Setup, No XML-RPC
Uploaded: 2026-07-08T00:00:00+00:00
Duration: 1 min 16 s
Description: A short setup video showing the OAuth path into Odoo. Instead of copying API keys between systems, each user authorises through an OAuth client and gets their own governed connection, credentials, and audit trail. Ends with the connection live and answering queries.

Most Odoo AI integrations fail at the configuration step: JSON config files, copied secrets, and an XML-RPC bridge that breaks when credentials rotate. This video shows the alternative — an OAuth handshake that takes four clicks and leaves each user with their own governed connection.

1:16 · Published 8 July 2026 · KSROlabs

The zero-config OAuth handshake end to end: four clicks from a fresh Odoo instance to Claude querying it, with no API keys to copy and no legacy XML-RPC.

Jump to

Watch on YouTube ↗

What happens in this video

A short setup video showing the OAuth path into Odoo. Instead of copying API keys between systems, each user authorises through an OAuth client and gets their own governed connection, credentials, and audit trail. Ends with the connection live and answering queries.

0:00
The integration bottleneck
Why most Odoo-to-AI setups stall: hand-written configuration, secrets copied between systems, and brittle XML-RPC bridges that have to be rebuilt whenever access changes.
0:22
The four-click zero-config setup
The connection is added from the AI client, pointed at your Odoo instance, and authorised. There is no config file to edit and no key to paste into a second system.
0:36
OAuth handshake and security
Odoo issues the authorisation itself, so the AI client holds a revocable grant rather than a static secret. Each user who connects gets their own client, their own credentials, and their own entry in the audit trail.
0:52
Live architecture initialisation
The client discovers the available tools from the MCP endpoint and the connection goes live against real data.
1:05
Summary and deployment
What the finished setup looks like, and how to roll it out to the rest of a team.

What you can do after watching

Complete the OAuth handshake without hand-editing config files
Give each teammate their own credentials instead of a shared key
Skip legacy XML-RPC pipelines entirely

Odoo MCP Server →Book a live demo

Questions about this demo

Is OAuth better than an API key for connecting AI to Odoo?

For teams, yes. An API key is a shared static secret — anyone holding it acts as the same identity, and rotating it breaks every workflow at once. With OAuth each user authorises their own connection, so access can be granted and revoked per person and the audit log shows who actually made each request. Scoped API keys remain the better fit for unattended machine integrations.

Do I still need XML-RPC to connect AI tools to Odoo?

No. The MCP endpoint replaces the XML-RPC bridge for AI clients. MCP exposes typed, discoverable tools that the model can call directly, so there is no custom mapping layer to build and maintain.

How long does the setup actually take?

The connection itself is four clicks — the full recording is just over a minute, unedited. Rolling it out to a team means each person repeating the same authorisation under their own Odoo login.