Talk to your Odoo
Connect Claude, ChatGPT, Cursor or any other AI assistant to live Odoo data. On your desktop, in the browser, on your phone. Scoped to the models you choose, bound to each user's own access rights. Sign in with your Odoo account, or paste one config.
BOOK A DEMO
Read-first by design. No blanket write access.
Works with your AI
Claude, ChatGPT, Cursor, VS Code. If it speaks MCP, it speaks Odoo.
Scoped, per user
Only the models you activate. Every answer respects the user's own Odoo access rights.
Read-first
No generic create, write or delete. Nothing changes unless you explicitly allow it.
Live in three steps
The MCP endpoint lives in your own Odoo, on the URL you already use. Nothing new to host, no ports to open, and no detour along another server.
1
SWITCH IT ON IN ODOO
MCP is part of your 360 AI subscription. Enable it in your Odoo and the endpoint is there, in the database you already run.
2
SCOPE WHAT AI CAN REACH
Activate the models the assistant may see, and optionally pin the exact methods per model. Everything else stays invisible.
3
CONNECT YOUR ASSISTANT
Sign in with your Odoo login, or paste a personal config generated in one click. First answer in minutes.
Your AI client
Claude, ChatGPT or Cursor. Asks in plain language, calls typed tools.
Your Odoo
The governed endpoint sits here. Two checks on every call, then Odoo's own access rights and record rules decide what comes back.
Your assistant talks to your Odoo directly. This is a separate route from the connection your 360 AI agents use.
MCP with guardrails
The Model Context Protocol is the open standard AI assistants use to talk to software. The USB-C of AI integrations.
360 puts a governed MCP endpoint in front of your Odoo, so assistants stop guessing about your business and start reading it.
8
typed read tools
0
servers in between
0
blanket write tools
1
sign-in to connect
Eight tools
The whole surface an assistant needs. Not one tool more.
odoo_search_read
Find and read records with full Odoo search filters, field selection, ordering and pagination.
odoo_read
Fetch specific records by ID. Just the fields you ask for, nothing more.
odoo_search_count
Count anything instantly, without pulling a single record into the conversation.
odoo_fields_get
Field definitions and metadata, so the assistant understands your data model before it queries.
odoo_list_models
Discover which models are open to the assistant. The allowlist, nothing more.
odoo_read_group
Grouped aggregates straight from Odoo: revenue by month, tickets by team, pipeline by stage.
odoo_get_callable_methods
Show which methods a model exposes, so the assistant reasons about your real business logic.
odoo_describe_function
Read a method's signature and docstring, so advice about your Odoo is grounded in your Odoo.
OPT-IN
odoo_call_method
Call model methods, but only the ones you allowlisted, model by model, for the users you put in the write group. Off by default.
Give AI answers, not the keys to your ERP
Access is layered: protocol, environment, user, model, method. Every layer must agree before a single record leaves your Odoo.
Runs as a real user
Every call is bound to the signed-in user. Odoo's own access rights and record rules decide what comes back. No shared super-user, ever.
Sign in, don't paste keys
OAuth 2.0 with the user's own Odoo login, straight from claude.ai, ChatGPT or the mobile apps. Revoke a connected client from Odoo at any time.
Keys scoped to MCP only
Desktop clients use a personal Odoo key issued for MCP and nothing else, so it can never be reused as a general API credential. Set an expiry, revoke it per user.
Model allowlist
Only the models you activate are reachable. Anything else simply doesn't exist for the assistant.
Method allowlist
Method calls are opt-in per model, method by method. Private methods are blocked outright.
Read-first by design
No generic create, write or delete tools. If the AI changes anything, it's through a method you deliberately allowed.
A bare AI connector.
Would you hand it your ERP?
Plenty of MCP connectors and DIY scripts give AI full admin access through one master key. 360 Odoo MCP is the same convenience, with the guardrails your ERP deserves.
MCP, the 360 way
Runs as each user
Odoo access rights and record rules apply to every single call.
Scoped by design
Model and method allowlists. Read-first: no blanket writes.
Sign in with Odoo
OAuth 2.0 from web and mobile clients, or one personal config per user.
Keys that expire
Per-user keys with end dates, scoped to MCP. Revoke anyone, anytime.
A bare connector
One master key
Every question runs with full admin access.
Everything exposed
HR, payroll, margins: readable by anyone who connects.
Writes included
One confused prompt away from changed data.
Keys never expire
Shared around, pasted in tools, and forgotten.
One sign-in. Or three lines of JSON.
- Web & mobile: add the connector in claude.ai or ChatGPT and sign in with your Odoo login.
- Desktop tools: Claude Desktop, Claude Code, Cursor or VS Code paste a personal config, generated in Odoo in one click.
- Per-user keys with expiry dates. Revoke one user without touching the rest.
{
"mcpServers": {
"odoo-360": {
"type": "streamable-http",
"url": "https:///ai360mcp",
"headers": {
"Authorization": "Bearer "
}
}
}
} Your own Odoo URL, your own key. No third address in the file.
Included in 360 AI
No separate product, no per-call fees. MCP access ships with the 360 AI platform: € 15 per user per month, everything included.
The questions your IT team will ask
Which AI assistants can connect?
Practically all of them. Browser and mobile clients (claude.ai, the Claude apps, ChatGPT) sign in with OAuth. Desktop and scripted clients (Claude Desktop, Claude Code, Cursor, VS Code) connect with a pasted config. If it speaks MCP, it can speak Odoo.
Can the assistant change my data?
Not by default. No generic write tools exist. Changes are only possible through methods you've explicitly allowlisted, per model, for users you put in the write group. Private methods are blocked outright.
What data can the assistant see?
Only models on the allowlist, and within those, only the records the signed-in user could already see in Odoo. Access rights are enforced by your Odoo itself, not re-implemented in a proxy.
Where does the connection actually go?
Straight to your own Odoo. The endpoint is part of your Odoo, on the HTTPS URL you already use, so there are no extra ports and no second service to host. It does not travel over the connection your 360 AI agents use, and no request or record passes through our infrastructure.
Which Odoo versions are supported?
Odoo Community and Enterprise, on the versions we support for 360 AI. Your Odoo version doesn't hold your AI back.
What's under the hood?
An Odoo module on your own database. The endpoint speaks JSON-RPC 2.0 over streamable HTTP, supports the current MCP protocol versions and OAuth 2.0 with PKCE.
Your ERP already knows the answer. Let it speak.
360 Odoo MCP is part of the 360 AI platform. Getting connected is as simple as our software: book your demo directly below.
That's AI, the 360 way.