Best Odoo MCP Connectors for 2026

A free server that takes security more seriously than most paid modules in other categories. It runs a built-in OAuth 2.1 server with per-request consent, lets a user pin a session to read-only with one checkbox, and starts from default-deny: no model is reachable until you enable it. Instead of generic write access you can expose curated verbs such as confirm_sale_order, backed by server actions.

• Log in with Odoo over OAuth 2.1: DCR, PKCE, consent and one-click revocation
• Read-only consent enforced server-side on every call
• Hashed, short-lived tokens with rotating refresh and reuse detection
• MCP-only API keys that cannot be used for general RPC
• Default-deny model whitelist with per-operation create, read, update and delete
• Business method calls, off by default and whitelisted per model
• Custom tools from server actions, each with its own schema and access groups
• 12 built-in tools including chatter posts and attachment fetch
• Audit log of every call, denial and login attempt
• Sanitised errors, clients never see tracebacks or SQL
• Local bridge for stdio-only MCP clients
• Works with Claude, ChatGPT, Microsoft Copilot, Cursor and VS Code

The free server with the most careful answer to the scariest part of MCP, the AI writing to your data. Every write runs in a savepoint, produces a field-level diff and can be undone in one click from an AI Changes screen, and content that arrives from untrusted sources is forced to human approval, so an injected instruction cannot quietly commit. OAuth 2.1, PII redaction and daily egress budgets are all included.

• Streamable HTTP and JSON-RPC at /mcp, plus legacy SSE for older clients
• OAuth 2.1 with DCR, PKCE S256 and refresh rotation, free
• Hashed bearer keys with a rotation grace window
• Model, field and domain scoping
• PII fields redacted by default
• Daily row and byte egress budgets
• Every write previewable, diffed and undoable from an AI Changes screen
• Untrusted content forced to human approval
• Audit log and database-backed rate limiting, no Redis
• In-Odoo Playground with a client config generator
• Publish any server action as an MCP tool with no Python
• Prompt templates as slash commands and pinned odoo:// resources
• Zero external Python dependencies, runs on Odoo.sh
• 90 days of free support included
• One tool registry shared by MCP clients, the in-Odoo Copilot and scheduled agents

From a publisher with a long reputation in the Odoo community, and the most developer-friendly server here. It ships 18 tools across the whole ORM, a playground inside Odoo, and a tool registry you can extend from your own addons with a decorator or from the backend without a deployment. Access is scoped by key, Read Only or Read and Write, rather than per model, and authentication is by bearer key rather than OAuth.

• 18 built-in tools, from model discovery and schema to reports and CSV or XLSX export
• Three MCP protocol revisions negotiated per request
• MCP keys scoped Read Only or Read and Write, or standard Odoo API keys
• Every call runs as the key owner, so record rules and ACLs apply
• Rate limiting per key, 60 requests a minute by default
• Audit log with method, tool, model, duration and status
• Built-in playground that calls the real /mcp endpoint
• Add tools with the @mcp_tool decorator or from the backend UI
• Reusable prompts surfaced as slash commands
• MCP badge on chatter messages written by an AI client
• Setup documented for Claude Code, Claude Desktop, Cursor, OpenCode, Windsurf and Codex CLI

More of an AI gateway than a plain MCP server. Alongside the MCP endpoint it connects five AI providers with automatic fallback, and puts Odoo behind chat bots on Telegram, WhatsApp, Discord and a web widget. Destructive actions are off by default, sensitive tools can require an approver, and every call is logged. Note that it needs a few external Python packages installed first.

• Streamable HTTP JSON-RPC endpoint at /mcp_gateway with API key access
• OpenAI, Anthropic, Gemini, Ollama and any OpenAI-compatible provider
• Priority ordering with automatic provider fallback
• Telegram, WhatsApp, Discord and web chat bots with memory
• @ai_tool decorator plus generic ORM, ask_ai and analyze_records tools
• Admin allow-list of models and operations, destructive actions off by default
• User consent gate for sensitive tools
• Tools honour each user access rights and record rules
• Full tool logging of user, source, model, duration and result
• AI Hub dashboard with live counts and server status
• Key generation wizard with client-ready config per platform
• Community and Enterprise

A free add-on that sits on top of the ERP Heritage native MCP server, so install both. It adds the finest-grained controls in this list: fields hidden so completely the AI cannot learn they exist, a record domain it can never see past, dry-run previews of every write, caps on how many records one write or delete may touch, and confirmation on risky operations. It verifies OAuth 2.1 tokens but is not an authorisation server, so you bring your own identity provider.

• Requires the free MCP Server (Native) base module
• Per-model field masking on read and rejection on write
• Record domains that scope the AI to one company or team
• Dry-run writes that report the exact effect without committing
• Per-model caps on write and delete size
• Confirmation for high-risk operations
• All-or-nothing batch writes in a single transaction
• OAuth 2.1 resource server with strict audience validation
• Allow-listed method caller, private methods blocked
• Report, file, long-running task and resource subscription tools

A deliberately small, governance-first server. Nothing is exposed until you list a model and tick the operations you allow, every call runs as the real Odoo user, and each one is written to a log that refuses edits and deletions, even from automation. It offers only eight tools, depends on base alone, and sends nothing to any outside service.

• Nothing exposed by default, models listed one by one
• Read, create, update and delete granted separately per model
• Every call runs as the Odoo user, with record rules and multi-company scoping
• Immutable call log: caller, tool, model, arguments, records, duration and outcome
• Filter the log to calls that changed data
• OAuth 2.1 for hosted assistants, Odoo API keys for scripts
• A deliberately small set of eight tools
• Depends on base alone, installs on any database
• No external service, no telemetry
• Fully translated to Arabic and checked in RTL
• Free support included, in English or Arabic

The only other paid connector here, at under twenty dollars. Rather than exposing whole models, you define each tool yourself, one model, one operation, the fields it may return and a record filter it can never escape, so the agent sees nothing you have not listed. Approval before writes and a full audit trail are not included, they come in a separate AI Agent Governance module built on top.

• Tools defined one by one: model, operation, fields and record filter
• Runs as a real Odoo user you choose
• Dedicated MCP keys stored as hashes, with optional expiry
• Revoke a key instantly, its audit history is kept
• Domain filtering and paging with a hard ceiling on results
• Stdio bridge script for clients that do not connect over HTTP
• n8n via a companion bridge module
• Approval queue and audit trail sold separately
• Community and Enterprise

Despite the name, it works with Claude Web, Claude Desktop, Cursor and other MCP clients, and it generates both a connector URL for Claude Web and a JSON config for header-based clients. Access is set per user and per model, with separate read, create, update, delete and method-call permissions, and a global switch, read-size limits and per-user rate limits sit on top. It is the smallest server here, at about a thousand lines of code.

• MCP endpoint at /troo/mcp with Odoo API key authentication
• Ready-made Claude Web connector URL and Cursor JSON config
• Troo MCP User and Troo MCP Administrator groups
• Per-user model rules with read, create, update, delete and call method
• Calls run as the authenticated user, so ACLs and record rules apply
• Global on and off switch
• Read size limit and control over delete availability
• Per-user rate limits and request activity tracking

Part of the open-source Apexive LLM toolkit rather than a standalone connector, and that is its strength: the same server can pick up extra tool packs such as 18 accounting tools for CPAs or 44 MIS Builder tools. Each user brings their own MCP key and sees only what their Odoo rights allow. The limitation is the version, it is published for Odoo 16 and 18, and not yet for 19.

• MCP server inside Odoo, part of the Apexive LLM module family
• Each user creates their own MCP key from their profile
• Ready-to-paste config for Claude Desktop, Claude Code and Codex CLI
• Works with Claude Cowork for team use
• Extendable with LLM Tool Account, 18 accounting tools
• Extendable with LLM Tool MIS Builder, 44 reporting tools
• Requires LLM Integration Base, LLM Tool and Web JSON Editor
• Open source
• Users only see what their Odoo rights allow