Connect Odoo to Claude Code

Have Claude create sales orders, invoices, and records in Odoo. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Odoo to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Odoo, you add a Odoo MCP server: a small hosted service that exposes Odoo's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Odoo account. No API keys pasted into config files.

claude mcp add --transport http odoo https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Odoo once connected?

Full read-write Odoo access lets Claude create and update the records you work in: draft a sales order from an email, raise a customer invoice, update a contact, or adjust an inventory item, then route it for your approval. The data entry that used to mean clicking through forms happens where the records already live.

Create or update a sales order from an email or quote you paste in
Draft a customer invoice and route it for your approval
Create or update contacts, customers, and vendor records
Update an inventory product, its pricing, or stock details
Log an activity or note on a CRM opportunity
Search records matching a filter and propose batched edits

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Odoo access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Odoo API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Odoo changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Odoo connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Odoo connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Odoo account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Odoo's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Odoo?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Odoo account it signs in with. Revoking access is one click in Odoo.

More on the Odoo connector

Odoo connector for claude.ai NetSuite + Claude Code SAP + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us