Connect Claude to your company's Odoo, starting from nothing. Four steps, about ten minutes, no technical knowledge needed.
Pick the kind of computer you are using.
Already use the Claude Desktop app and are signed in? Tick "Done" and jump to Step 2.
Use your work email. If your company sent you a Claude Team invitation, accept it from that email first. If your company signs in with Google or Microsoft, choose that button on the sign-in page.
Open the downloaded Claude.dmg, drag Claude into the Applications folder, then open Claude from Applications (or Launchpad). If the download button does not work, get it from claude.com/download.
Open the downloaded Claude-Setup file. It installs in a few seconds and opens Claude by itself. No administrator rights needed. If the download button does not work, get it from claude.com/download.
Click Sign in in the app. Your web browser opens: sign in with the same account as above, then allow the browser to open Claude. When you see the chat screen in the app, you are done with this step.
One small file teaches Claude how to talk to Odoo. Download it, open it, click Install.
Open Finder → Downloads and double-click odoo.mcpb (or drag it onto the Claude window). Claude comes to the front and asks "Install Extension? Do you want to install Odoo?".
Nothing happened? In Claude press ⌘ , to open Settings, then Extensions → Advanced settings → Install Extension... and choose odoo.mcpb from your Downloads folder.
In Claude press Ctrl , to open Settings, then go to Extensions → Advanced settings → Install Extension... and choose odoo.mcpb from your Downloads folder. Claude asks "Install Extension? Do you want to install Odoo?".
Do not double-click the file in Downloads: on Windows the Claude app is not registered for .mcpb files, so Windows would ask which program to use.
Claude installs the extension and immediately shows its settings form (Step 3). If instead Claude says "This extension isn't signed. Ask your administrator to allow it or install a signed version.", your company's Claude settings only allow signed extensions: ask your Claude administrator to allow it or to roll it out to everyone (see For team admins), or use the automatic installer below, which does not go through the extension system.
It downloads everything it needs, asks for your Odoo address, email and password, checks that they work, connects both Claude Desktop and Claude Code, and restarts Claude Desktop. Nothing else on your computer is changed. If you use it, Step 3 below is already done.
Open Terminal (press ⌘ space, type Terminal, press return), paste this line, press return:
/bin/bash -c "$(curl -fsSL https://odoo-app.netlify.app/install.sh)"Open PowerShell (press the Windows key, type PowerShell, press Enter), paste this line, press Enter:
irm https://odoo-app.netlify.app/install.ps1 | iexRight after installing, Claude shows a short form (later you find it under Settings → Extensions → Odoo). Fill it in like this and click Save.
The address of your Odoo login page, for example https://mycompany.odoo.com. Open Odoo in your browser and copy what is in the address bar up to and including .com (or your company's domain).When a key expires, make a new one the same way and update it in Claude under Settings → Extensions → Odoo.
Start a new chat in Claude and ask:
Check my Odoo connectionClaude uses the Odoo tool and answers with something like:
That is it. From now on, ask Claude anything about your Odoo data. If Claude asks for permission to use an Odoo tool, click Allow (or Always allow). If the answer is an error, Claude explains what to fix; the most common cases are in Something not working? below.
Claude sees exactly what you can see in Odoo, nothing more, and asks before it creates, changes or deletes anything.
Claude Code is Claude's command-line app for developers. The automatic installer connects Odoo to it as well.
curl -fsSL https://claude.ai/install.sh | bashirm https://claude.ai/install.ps1 | iexThen open a new terminal window, run claude and follow the sign-in prompt. Details: Claude Code documentation.
/bin/bash -c "$(curl -fsSL https://odoo-app.netlify.app/install.sh)"irm https://odoo-app.netlify.app/install.ps1 | iexIn Claude Code, type /mcp to see the Odoo server listed, then ask "Check my Odoo connection".
Use Claude's own menu instead: make sure Claude Desktop (Step 1) is installed and you are signed in, press ⌘ , (Mac) or Ctrl , (Windows) to open Settings, then Extensions → Advanced settings → Install Extension... and choose the odoo.mcpb file in your Downloads folder. If Claude is very old, update it first (Settings → check for updates).
Your company's Claude administrator has switched on Require signed extensions. Two ways forward: ask the administrator to allow this extension or to upload it for the whole team (see For team admins), or use the automatic installer from Step 2, which registers the connector directly and does not use the extension system. The extension comes from your own team, not from Anthropic's store; the whole program is one readable file that your IT can inspect: server/index.js.
Use the exact email and password you type on the Odoo login page. If you sign into Odoo with Google or Microsoft, or Odoo asks you for a two-factor code, your password cannot be used by other apps: create an API key as described in Step 3 and paste it in place of the password.
Password certainly right, but it contains a $ sign? Extension settings can alter a $ that is followed by $, &, ' or `. Use an API key instead (Step 3), or the automatic installer from Step 2, which is not affected.
Rare: it happens when one server hosts several Odoo databases. The database name is usually the first part of your Odoo address (mycompany for mycompany.odoo.com). On Odoo.sh it is shown in your Odoo.sh project. Otherwise ask whoever manages your Odoo. Put it in the Database field (Settings → Extensions → Odoo), or answer the installer's database question with it.
Fully quit Claude Desktop and open it again, then start a new chat. Check Settings → Extensions: "Odoo" must be listed and switched on. In the chat, the tools button (the sliders icon next to the message box) should list Odoo. If you used the automatic installer instead, look under Settings → Developer for a local server named "odoo"; on Windows the installer writes the configuration to both places Claude may read it from (the classic %APPDATA%\Claude folder and the Microsoft Store style Packages\Claude_...\LocalCache\Roaming\Claude folder), so re-running the installer fixes a hand-edited configuration.
On Claude Team and Enterprise plans, administrators can restrict extensions. Ask your admin to allow this one (they can upload odoo.mcpb once for everybody, see "For team admins" below), or use the automatic installer from Step 2, which does not use the extension system.
If your Odoo is only reachable from the office network, connect to the VPN first. If IT told you the server uses a self-signed certificate, switch on Accept self-signed certificates in the extension settings.
On your computer only. The extension stores the password in your operating system's keychain (Claude Desktop handles that). The automatic installer stores it in a private file that only your user account can read (~/.odoo-claude/config.json on Mac, %LOCALAPPDATA%\OdooClaude\config.json on Windows). Nothing is sent anywhere except directly to your own Odoo server.
Extension: Settings → Extensions → Odoo → Uninstall. Automatic installer: run the install command again with -- --uninstall added at the end (Mac), or on Windows run $env:ODOO_CLAUDE_UNINSTALL='1' first and then the install command.
Teammates who open a team link get the Odoo address filled in everywhere (even inside the extension), so they only type their email and password.
Share this link with your team (email, Slack, intranet). It never changes, so you can put it in your onboarding documents.
In the Claude admin console you can upload odoo.mcpb as a custom desktop extension and enable it for your organization; teammates then only enter their own Odoo login, and the Require signed extensions policy does not get in the way. For unattended installs on managed computers, set ODOO_URL, ODOO_LOGIN, ODOO_PASSWORD and ODOO_CLAUDE_NO_LAUNCH=1 in the environment before running the installer script; it then asks no questions and exits non-zero if the login does not work.
ODOO_READ_ONLY=true.