Everything you need, in one place.

Get started in about five minutes

erpAIbridge has two halves: a desktop AI agent that runs on your computer, and our hosted MCP server that gives it safe access to Odoo. You install the first and simply point it at the second — there is no server for you to run and nothing to install inside Odoo.

1. Get your access token

   Fill in the short form on the contact page. You'll get an email with your personal token (it starts with trial_), the server address, and your download links. Lost the email? Submit the same address again and it returns the same token rather than creating a new one.

2. Install the desktop agent

   Download and install the agent for Windows or macOS using the link in your email. This is the app you actually chat with — it runs locally on your machine, and your Odoo data is never stored in it.

3. Add your own AI provider key

   Open Settings → Providers → API keys and paste a key from OpenAI, Anthropic (Claude), OpenRouter or any supported provider. This is what people mean by "bring your own key" (BYOK): erpAIbridge's trial covers the Odoo connection only — the AI model itself is a separate account you already have or can create in a couple of minutes on that provider's own site. You stay in control of which model runs and what it costs, and the key is stored only on your own computer — it never passes through our servers.

4. Connect erpAIbridge

   Go to Capabilities → MCP → Add server and paste the configuration below, replacing the token with your own. If the app asks for the URL and token as separate fields, use the two values directly.

   MCP server configurationCopy

   {
     "mcpServers": {
       "odoo-bridge": {
         "url": "https://demo.odooaibridge.com/mcp",
         "headers": {
           "Authorization": "Bearer trial_YOUR_TOKEN_HERE"
         }
       }
     }
   }

5. Ask your first question

   Start a new chat and type "List our customers in India." If you get a real answer back, everything is wired up correctly. Out of the box you're talking to our sample Odoo full of demo data — so you can try anything, including changes, without touching real records.

Connect your own Odoo instance

There are four ways to use your own data, differing in one important way: where your Odoo credentials live. Pick the one that matches how careful your organisation needs to be — the honest one-line version is: hosted is for trying it, local is for trusting it. For a side-by-side showcase see all four options; the setup steps for each are below.

Why the split? ChatGPT's connectors can only call a hosted server — that's an OpenAI constraint. Claude Desktop, Cursor and Gemini can also run the bridge as a local process, so for those clients nothing ever needs to touch our infrastructure. Whichever path you choose, the blast radius is bounded the same way: create a dedicated Odoo user with only the access you want the AI to have, and revoke its API key in Odoo at any time.

Path 1 — Hosted connect (recommended for evaluation)

Keep using our hosted server and the token you already have — you simply tell it which Odoo to talk to. Nothing changes in your AI client. This is the fastest path and the only one that works with ChatGPT. We recommend it for evaluating against your data with a scoped user; when you move to production, switch to a private path below or a private deployment — same tools, no credentials held by us.

Step 0 — create a limited Odoo user (2 minutes, worth it)

Don't connect an admin account. In Odoo: Settings → Users → New, give it read access to just the apps you want to test (say Sales and Invoicing), and sign in as that user for the next step. Odoo's own record rules then bound everything the AI can ever see or do — no matter what.

Then create an API key for that user

An API key is safer than a password: it is scoped to one user, and you can revoke it at any time without changing anyone's login.

1. Signed in as that limited user, click the avatar (top-right) → My Profile → Account Security tab.
2. Choose New API Key, name it something like erpAIbridge, and copy the key. Odoo shows it only once.
3. Note your database name — on Odoo Online it is usually the first part of your address, for example mycompany in mycompany.odoo.com.

Then connect it here

Paste your details below. We verify them against your Odoo before saving anything, so a typo fails here with a clear message rather than halfway through a chat.

That's it. Start a new chat and ask something you know the answer to — "How many customers do we have?" — to confirm you're seeing your own records. Disconnect at any time to delete your stored credentials and return to the sample database.

Prefer to do it from a terminal?

curl -X POST https://odooaibridge.com/api/connect-odoo \
  -H "Authorization: Bearer trial_YOUR_TOKEN_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "odoo_url": "https://mycompany.odoo.com",
    "odoo_db": "mycompany",
    "odoo_login": "[email protected]",
    "odoo_api_key": "YOUR_ODOO_API_KEY"
  }'

How your credentials are handled

• Encrypted at rest. Your Odoo API key is encrypted before it is written to disk, never stored as plain text, and never shown back to you or anyone else.
• Only for your token. Each request is served using the connection attached to the calling token, so your data is only ever reachable with your own key.
• Yours to remove. Disconnecting deletes the stored credentials. Revoking the API key inside Odoo cuts access instantly and independently of us.
• Scoped by Odoo itself. We sign in as the user you nominate, so that user's permissions and record rules bound everything the agent can do.

Path 2 — Desktop agent (fully local, no terminal)

The erpAIbridge desktop app runs the bridge on your own machine and stores your Odoo connection in your operating system's keychain (Apple Keychain / Windows Credential Locker). Nothing reaches our servers, your Odoo needn't be on the internet, and there's no config file to edit — a screen in the app does it for you. This is the easiest fully-local option.

1. Create a limited Odoo API key

   As above (Step 0 + the API-key steps) — a dedicated read-only user is the safest choice.

2. Open Capabilities → MCP in the app

   At the top of the server list you'll see the Connect your own Odoo — fully local & private card. Click Connect…

3. Enter your details and verify

   Fill in your Odoo URL, database, login, API key and erpAIbridge licence, then Verify & connect. The app checks the credentials against your Odoo and, on success, stores the credentials and licence encrypted in your keychain — never in a file, never on our servers. It registers a licensed local connection automatically and pauses the hosted demo, so only one Odoo is ever active.

4. Start a new chat

   Ask about your data — the agent now uses your Odoo. Disconnect on the same card erases the credentials from your keychain and switches back to the demo.

Add your AI provider key under Settings → Providers → API keys as usual — the app brings the Odoo connection, you bring the AI. Odoo workflow skill packs and cron blueprints are delivered by the connected bridge and require the skills feature on paid licences; proprietary prompt files are not installed on your machine.

Path 3 — Self-hosted bridge (Claude, Cursor, Gemini — credentials never leave your machine)

Prefer to keep using Claude Desktop, Cursor or Gemini? erpAIbridge is a single small program. Instead of using our hosted copy, your MCP client starts it on your own machine as a local process: your AI client talks to the local bridge, the bridge talks to your Odoo, and your URL, database, login and API key exist only in your own configuration. We never see them — there is nothing on our side to trust. Works with Claude Desktop, Cursor, VS Code and Gemini CLI (ChatGPT can't launch local processes — that's the one client that needs Path 1). Your Odoo can be on a private network; internet exposure isn't needed.

The private self-host package is the compiled, source-free erpAIbridge image — no Python source of ours, machine-bound licence, hardened container. To get it, choose “Private MCP” on the signup form. We review the request, then email you a secure download link, a licence key (starts with ob1.), and the install steps below. Already have a licence? Fetch the package any time with your token:

curl -X POST https://odooaibridge.com/api/self-host-download \
  -H "Content-Type: application/json" \
  -d '{"license": "ob1.YOUR_LICENSE_TOKEN"}'
# → returns a time-limited download link for the compiled image bundle

docker load < odoobridge-selfhost-*.tar.gz          # load the compiled image
odoo-bridge-admin activate --bundle license.bundle   # verify + install your licence
# .env:  BRIDGE_MACHINE_ID=$(cat /etc/machine-id)     # bind to this host
docker compose -f docker-compose.protected.yml up -d # digest-pinned, hardened
curl http://localhost:8072/health

The licence is machine-bound — it runs on the host it was activated for, and the audit trail, before/after values and dashboards all stay on your infrastructure. Migrating hardware? Run odoo-bridge-admin activation-request and send us the fingerprint; we re-issue free.

Prefer to keep it single-user on Claude Desktop / Cursor / Gemini instead of a team container? Use the same licence with a local config block:

{
  "mcpServers": {
    "odoo": {
      "command": "odoo-bridge",
      "env": {
        "BRIDGE_TRANSPORT": "stdio",
        "ODOO_URL": "https://odoo.internal.mycompany.com",
        "ODOO_DB": "mycompany",
        "ODOO_USER": "[email protected]",
        "ODOO_API_KEY": "YOUR_ODOO_API_KEY",
        "BRIDGE_LICENSE": "ob1.YOUR_LICENSE_TOKEN"
      }
    }
  }
}

Cursor and VS Code use the same command/env block in their MCP settings; Gemini CLI takes it in ~/.gemini/settings.json under mcpServers. Running it for a whole team instead? The same package runs as a small always-on container inside your network — your clients then use its private URL. Both variants are covered in the guide that comes with the package.

Path 4 — Enterprise deployment

For company-wide, governed use — a private, secure MCP server inside your infrastructure (on-premise, private cloud, dedicated appliance or air-gapped), with role-based access, a complete audit trail and AI-provider independence. See erpAIbridge Enterprise, or talk to us and we'll scope and deploy it with you.

Ask your Odoo from WhatsApp

Link WhatsApp once and you can ask the same questions from your phone — "what did we invoice yesterday?", "is the Patio Umbrella back in stock?" — without opening the app. The assistant replies in your own Message yourself chat, and it only ever reads that chat.

Link it

Keep this page open while you scan — the code refreshes every few seconds until your phone picks it up.

Your erpAIbridge token

The same token from your welcome email.

Link WhatsApp Unlink

On your phone: WhatsApp → Settings → Linked devices → Link a device, then scan this.

Then try it

Open WhatsApp, go to the chat with yourself, and send "how many open quotations do we have?". Send help at any time for the short command list, or unlink to disconnect from your phone.

Configuration reference

What you set in the desktop agent

What we control on the server

These are set for you on the hosted service. They matter because they explain what the agent will and won't agree to do — and they're the same switches you'd set yourself if you self-host.

Need a different combination for a client — extra models, specific actions allow-listed, deletes enabled under supervision? That's a normal request. Tell us what you need.

If you self-host instead

erpAIbridge is one stateless container. You point it at your Odoo with environment variables and run it next to your other services — useful when Odoo isn't reachable from the internet, or policy requires everything to stay inside your network.

ODOO_URL=https://mycompany.odoo.com
ODOO_DB=mycompany
[email protected]
ODOO_API_KEY=your_odoo_api_key

BRIDGE_API_KEY=pick_a_long_random_secret   # what your agent sends as Bearer
BRIDGE_ENABLE_WRITES=1                     # writes off unless set
BRIDGE_WRITE_CONFIRMATION=elicit           # ask a human before saving

The container then serves MCP on port 8072 at /mcp, with /health for monitoring. Contact us for the image and licence terms.

What to test, and what you should see

Copy any of these straight into the chat. They're grouped so you can work through every capability deliberately — and see the safety behaviour as clearly as the useful behaviour. Use your own wording too; plain language is the point.

What it can do

Everything below works in plain language — these are capabilities, not commands you have to memorise.

Why it's safe to point at real data

This is the question every finance and IT team asks, so here is the honest mechanical answer — these are structural properties, not promises about the AI behaving well.

• Reading can't write. The read path has no write capability at all, so no clever prompt can turn a question into a change.
• Changes are drafted, not applied. Every create or update is previewed and waits for a person to approve it. You see exactly what will change before it does.
• Deleting is off. Not discouraged — disabled. Where it is ever enabled, it is limited to named models and still requires approval.
• Actions are allow-listed. The agent can only run operations we have explicitly permitted, such as confirming a quotation. It cannot execute arbitrary code in Odoo.
• Odoo's own permissions apply. We sign in as a real Odoo user, so that user's access rights and record rules govern everything. The agent is never a super-user.
• Duplicate protection. If the AI calls the same write twice, the second is recognised and skipped instead of creating a duplicate record.
• Everything is logged. Each call is recorded with who, which tool and the outcome — on the hosted service that log holds field names only, never your record values.

Reviewing what the agent did — the audit trail

Every action through erpAIbridge is recorded, and you can review it three ways:

• Ask in chat. "What did you change on Acme last week?" — the agent reads its own trail and answers with a timeline. Works in any connected AI client.
• Open the viewer. A built-in web page (no install) with the full timeline — filter by user, record or date, and export CSV. In the desktop agent, click View audit trail on your Odoo connection card; on the hosted service, open demo.odooaibridge.com/audit and sign in with your token.
• Restore a value. On deployments that record before-and-after values (desktop and self-host, where the log stays on your own machine), any changed field shows its previous value — restoring it is one approved change, itself audited.

Who sees what is decided by your role in Odoo itself, not by any app setting: administrators and managers can review the whole organisation's activity; everyone else sees only their own. Worth knowing: standard Odoo keeps no comparable who-changed-what history — this trail exists because every action passes through one governed gateway.

Trial limits, AI costs and what counts

Troubleshooting

Frequently asked

Still stuck?

Send us what you typed, what you expected and what you got — screenshots are ideal. If it's a connection problem, include your Odoo version and whether it's Odoo Online, Odoo.sh or on-premise. Never send us your API key or password; we never need them by email.

Contact support [email protected]