MCP Server. AI Chats and LLM Odoo Integration v.20

Connect in minutes

Link your database to Claude, ChatGPT (developer mode), or any other MCP client with a guided app authorization or a ready config - no middleware project, no API keys to hand around.

A complete MCP server

Tools, resources, prompts, sessions, streaming (SSE), and change notifications on three protocol versions - the full surface a serious AI client expects, not just a list of actions.

Read and write with 31 tools

Search and read records, create and update them, run actions, work with attachments, chatter, activities, PDF reports, global search, dashboard KPIs, and company context.

Write with a safety net

Write tools return a preview first; the change runs only after an explicit confirm, can be cancelled, and expires on its own. Risk levels tell the assistant when to warn.

Your rules, not the model's

Native Odoo rights stay in force. On top: deny rules per user or group, model and field allow-lists, domain guards, rate limits, and a payload-level audit journal with retention.

Your own tools without a module

Point a tool at an existing model method (for example sale.order / action_confirm) and the assistant can call it. A one-line decorator covers tools with their own arguments.

Natural-language BI

Skip another pivot table when you need a clear answer now:

• Find margin anomalies and ask why they happened
• Compare categories or regions across periods
• List inactive top customers and draft follow-ups

Inventory & supply chain

Go beyond static min/max rules with AI that reads moves and lead times:

• Flag products at stockout risk before the next replenishment window
• Spot dead stock and suggest sensible bundle ideas
• Review picking patterns for warehouse layout ideas

Finance that understands context

Match documents and project cash - not only OCR digits:

• Compare a PDF bill to a purchase order and highlight mismatches
• Project near-term balances from open invoices, bills, and payment habits
• Scan partners for missing or invalid VAT numbers

CRM & personalization

Combine sales, support, and projects into one customer story:

• Summarize account health from volume, tickets, and payment speed
• Draft localized offers from real purchase history
• Prioritize new leads against your most profitable account patterns

Routines & automation

When your AI client supports schedules (for example Claude), keep Odoo in the loop without opening the app every morning:

• Daily brief - summarize new tickets by priority before work starts
• Stock early warning - weekly risk scan from moves and open sales
• Smarter reconciliation helpers - reason over messy bank text and leave only hard cases for humans

AI never bypasses Odoo security. Every call runs as the Odoo user who authorised the client - with that user's groups, record rules, and company access. The server then adds controls of its own, so you decide what assistants may do, for whom, and with which confirmation.

Preview, then confirm

• Create, update, delete, and action tools answer with a preview of the exact change - nothing is written yet
• The assistant asks you, then calls confirm or cancel; a pending operation expires after its TTL
• Per tool: Direct, Preview + Confirm, or Disabled - built-in and custom tools alike

Risk levels

• Every tool carries a level: low, medium, high, or critical
• High-impact tools instruct the assistant to warn the user before executing
• The level is visible in the tool registry and recorded with each audit entry

Mandatory MCP roles

• MCP Server: User - required before any AI agent can act on that user's behalf
• MCP Server: Administrator - clients, signing keys, registries, deny rules, and audit control

Security deny rules

• Block selected tools for chosen users or groups (for example posting chatter or deleting records)
• A refused call fails with a clear error - the request never silently succeeds

Per-tool guards

• Allowed models and a field allow-list keep sensitive data out of the assistant's reach
• Domain guards limit which records a tool may touch
• Rate limit per minute and timeout per tool

Audit journal in your database

• Request and response payloads, status, latency, user, client, session, and company context for every call
• Remote address and user agent, plus a change diff for writes
• Retention period of your choice; old entries are cleaned up by a cron

Full protocol surface

• Tools - 31 built-in actions with JSON schema validation
• Resources - 14 read-only views such as odoo://record/{model}/{id}, chatter, attachments, schema, dashboards
• Prompts - 6 reusable templates with arguments: record summary, daily briefing, changelog, workflow guide, data analysis
• Sessions with SSE streaming and resumption, list-changed notifications, and three negotiated protocol versions
• A failing tool call is answered in-band, so the session stays up and the client does not re-authenticate

Your own OAuth 2.0 server

• Authorisation code with refresh tokens and rotation, plus client credentials for server-to-server use
• Public or confidential clients, registered by hand, from a metadata document, or through dynamic client registration
• Consent screen in Odoo; access, refresh, and code lifetimes set in Settings
• JWT access tokens signed with RSA keys that you manage in Odoo and publish through a JWKS endpoint

Files in both directions

• Small files travel inline; large ones use staged uploads with their own size and slot limits
• The assistant can hand the user an upload page that works from a phone camera
• Signed download links with a TTL, a MIME allow-list, allowed models for binaries, and an optional scan hook

Multi-company sessions

• The assistant can list companies and set the active ones for the session, the same way the company switcher works
• Writes always name one current company; the company context is stored with every audit entry

Custom tools without a module

• Create a tool record that points at an existing public model method - the assistant calls it on the records it names
• Mark a method with the @mcp_tool decorator when it needs its own arguments or must be read-only
• Custom tools follow the same scopes, confirmation modes, and audit as the built-in ones

Governance in one menu

• Tools, Resources, Prompts, Clients, Sessions, Pending Operations, Audit Logs, Security Deny Rules, Signing Keys
• About twenty settings: token lifetimes, session TTL, SSE heartbeat, notification queue, upload limits, audit retention
• Cleanup crons for tokens, sessions, pending operations, and logs