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
Your Odoo already talks to the 360 AI server. MCP rides that same connection: nothing new to host, no ports to open.
1
CONNECT YOUR ENVIRONMENT
Your Odoo is registered as an environment on the 360 AI server. One click validates the link and syncs models and users.
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.
360 AI server
One governed endpoint. Checks both keys, applies the model and method allowlists, then relays as the authenticated user.
Your Odoo
Answers with live data. Access rights and record rules apply, so the AI sees exactly what that user sees.
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.
7
typed tools
2
keys on every call
0
blanket write tools
1
sign-in to connect
Seven tools
The whole surface an assistant needs. Not one tool more.
x360_search_read
Find and read records with full Odoo search filters, field selection, ordering and pagination.
x360_read
Fetch specific records by ID. Just the fields you ask for, nothing more.
x360_search_count
Count anything instantly, without pulling a single record into the conversation.
x360_fields_get
Field definitions and metadata, so the assistant understands your data model before it queries.
x360_list_models
Discover which models are open to the assistant. The allowlist, nothing more.
x360_read_group
Grouped aggregates straight from Odoo: revenue by month, tickets by team, pipeline by stage.
OPT-IN
x360_call_method
Call model methods, but only the ones you allowlisted, model by model. Off by default.
Your language, your context
Every call carries the user's language, timezone and company. Answers arrive the way your team works.
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.
Two keys, both expiring
Config-based connections send an environment key plus a personal user key, validated together. Both carry expiry dates you control.
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. 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:///x360mcp",
"headers": {
"x360-api-key": "",
"x360-user-id": "",
"x360-user-api-key": ""
}
}
}
} 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. 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.
Does my Odoo have to be exposed to the internet?
No. AI clients connect to the 360 AI server. Your Odoo talks to that server over its existing 360 AI connection. No extra ports, no new public surface.
Which Odoo versions are supported?
Connected environments run Odoo v16 to v20, Community and Enterprise. Your Odoo version doesn't hold your AI back.
What's under the hood?
Open-source (LGPL-3.0) Odoo modules on the 360 AI platform. 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.