Connect your Odoo to Claude, ChatGPT & any AI — in minutes
MCP Connector links any AI client that supports the Model Context Protocol directly to your Odoo database. Install the free module, configure it once (about 5 minutes), and give your team a single connector link — no shared passwords, no per-user setup. Access is orchestrated by role and email, and works from desktop, web and mobile AI apps.
Google OAuth sign-in • role-based API keys • live two-way link
Run your ERP in plain language
Once connected, anyone on your team just asks their AI assistant — it does the work directly in Odoo, within their own permissions.
Instant analytics
“Show revenue by salesperson this quarter and flag anyone below target.”
Create quotations
“Draft a quote for ACME: 10× Product A, 5× Product B, 15% discount.”
Client follow-ups
“List customers with no activity in 30 days and log a follow-up task.”
Stock & expiry review
“Which lots expire within 30 days, how many units, and in which warehouse?”
Orchestrate access by role & email
Define roles in the module and map each one to a set of Google emails. Whoever signs in gets exactly the permissions of the matching Odoo user — nothing more. Add or remove people by editing a list, never by handing out credentials.
Six processes, about five minutes
Follow the processes in order. Each step below has the exact screenshot from the real interface.
Install the free module
Add MCP Connector to the Odoo database you want to expose to your AI client, then open it to create your first connection.
Install & activate
Go to Apps, find MCP Connector and install it in the database you want to access through MCP.

Create a new connection
Open MCP Connector → Connectors and click New to start a new MCP registration.

Create Google OAuth credentials
The connector uses Google sign-in to authenticate your users. Create an OAuth client at console.cloud.google.com and copy its Client ID & Secret. You will add the redirect URLs later, in Process 5, once the module generates them.
Open APIs & Services
In the Google Cloud console, open APIs & Services from Quick access.

Go to Credentials
In the left menu, select Credentials.

Create credentials
Click + Create credentials at the top.

Choose OAuth client ID
Select OAuth client ID from the dropdown.

Application type: Web application
Set Application type to Web application.

Name it & create
Give the client any name (e.g. “Odoo MCP Connector”) and click Create. Leave the origin/redirect URIs empty for now — you will paste them in Process 5.

Copy Client ID & Secret
Copy the Client ID and Client Secret and paste them into the matching fields of the MCP Connector module in Odoo. Store the secret safely — it is shown only once.

Generate an Odoo API key
Each role connects to Odoo with its own API key, generated by the Odoo user that role represents. Repeat this process for every role (admin, sales, read-only, …).
Open My Preferences
Click your avatar (top-right) and choose My Preferences.

Security → Add API Key
Open the Security tab and click Add API Key.

Confirm your password
The user creating the key must enter their Odoo login password to confirm.

Name it & set validity
Give the key a clear name and choose an expiration — a Persistent Key is recommended so the connection does not expire.

Generate the key
Click Generate key.

Copy the key into the module
Copy the generated key and paste it into the Odoo API Key field of the matching role in the MCP Connector module. It is shown only once.

Configure & register the connector
Fill in the registration form with everything you gathered, add your roles, and register.
Name, Google keys & Odoo instance
Give the connector a name, paste the Google Client ID / Secret from Process 2, and set the Odoo URL and Database — use the green “Use this instance” / “Use current DB” shortcuts to auto-fill the current database.

Add roles: API key + email
In Access Roles, add a line per role with its role name, its Odoo API key (from Process 3) and the email(s) allowed to use it. This is how you map who gets which permissions.

Click Register
Press Register in the top-left corner. The status changes to Registered and your personal MCP instance is provisioned.

Authorize the URLs in Google
After registration the module generates three URLs. Copy two of them into your Google OAuth client so sign-in is trusted, then re-register.
Copy the generated URLs
The Registration Result now shows Google Origin URL, Google Callback URL and AI Connector URL. Use the copy buttons.

Paste them into Google Console
In your OAuth client: put the Google Origin URL into Authorized JavaScript origins, and the Google Callback URL into Authorized redirect URIs. Save.

Re-register
Back in Odoo, click Re-register to apply everything. Copy the AI Connector URL — that is the link you share with your team.

Connect your AI client & sign in
Shown here in Claude — the flow is the same in ChatGPT or any MCP-compatible client. Just paste the AI Connector URL and sign in with Google.
Add a custom connector
Open Settings → Connectors, then Add → Add custom connector.

Add name & connector URL
Give it any name and paste the AI Connector URL into the MCP / HTTPS URL field.

Connect
Click Connect to start the sign-in.

Allow access
Sign in with Google and click Allow Access. Only emails you listed in a role can connect — and each works within that role’s Odoo permissions. Done!

You’re live
Your AI client now works with your Odoo from desktop, web and mobile. Add or remove people any time by editing role emails and re-registering — no new setup on their side.
Safe access, on your terms
Google OAuth only
No valid Google account in a role = no access. Every request is authenticated.
Real Odoo permissions
Each person acts as their mapped Odoo user — the AI never gets super-access.
Data stays in Odoo
The connector is a gateway to your API. We don’t copy or store your database.
Isolated per tenant
Each customer runs on a dedicated, isolated instance over HTTPS.
What you need
A running Odoo, a Google Cloud project, and an MCP-capable AI client. That’s it.
Odoo
Community or Enterprise — on-premise, Odoo.sh or self-hostedOdoo API key
One per role you want to exposeGoogle Cloud project
For the OAuth client (sign-in)MCP AI client
Claude, ChatGPT or any client supporting custom MCP connectorsFrequently asked questions
Do I have to give people my Odoo password?
No. You share one connector link. Users sign in with Google; access is decided by their email and its role — no credentials are handed out.
Does it work with ChatGPT too?
Yes. Any AI client that supports custom MCP connectors works — Claude, ChatGPT and others. The connector URL is the same.
Can I limit someone to read-only?
Yes. Point a role at an Odoo user that has read-only rights and add their email — the AI can then only read for that person.
Are custom modules supported?
Yes. The connector reads model and field structure directly from your Odoo, so custom models and fields work out of the box.
Where does my data live?
In your Odoo. The connector proxies authorized API calls; it does not keep a copy of your database.
Someone joined or left — what do I do?
Edit the role’s email list and press Re-register. Access updates instantly with no work on the user’s side.
Give your team an AI line to Odoo
Install the free MCP Connector, spend five minutes on setup, and share one secure link.
Free module • ~5 min setup • Community & Enterprise • Claude, ChatGPT & any MCP client
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module