A standalone Model Context Protocol (MCP) server for Odoo, providing Claude with safe, human-approved access to Odoo CRM, projects, and other business domains.
Overview
This MCP server exposes Odoo as a set of modular, domain-specific tools that Claude can safely call:
Open-source MCP server which connects your Clawd/Claude to Odoo in a clean and safe way
Domain-extensible — Easy to add support for other Odoo apps (Support, Finance, Knowledge, ERP Implementation, etc.)
All write operations are safety-checked to prevent accidental outbound communication (emails, SMS, calendar invites). Internal-only notes, activities, and field updates are safe by design.
Disclaimer
This project is an independent, community-maintained MCP server and is not affiliated with, endorsed by, or sponsored by Odoo S.A.
Odoo is a trademark of Odoo S.A. Any product names, logos, and brands are used for identification only.
You are responsible for validating security, compliance, and access controls before using this server in production environments.
Always test write-enabled workflows in a non-production environment first.
Key Features
✅ Safety-first: Outbound communication blocker prevents emails, SMS, and invites
The primary organisation path is Claude Cowork through a reachable, OpenCrane-managed remote MCP connector with per-user OAuth and per-user Odoo credential custody. The secondary path is local stdio, which remains local-first and needs no hosted relay. A plugin repository is not remote hosting.
See setup.md for the current setup, onboarding, transport, rotation, and fail-closed availability rules.
Hosted MCP Server Warning
Do not expose a shared MCP process that can select or read arbitrary users' Odoo tokens. A remote deployment is acceptable only when OpenCrane authenticates each user, binds profile selection and credential release to that identity, and fails closed when the adapter or qualification is unavailable.
Tools
Generic Odoo Tools
odoo_ping — Validate connectivity and show your profile
odoo_search_read — Find records with flexible filters
Use the secure local loopback/CLI onboarding flow, or the OpenCrane profile onboarding flow for Cowork.
For local stdio, ask Claude to create an Odoo connection. It returns a local browser
form for credential entry and can check completion before running odoo_ping.
Existing databases are retained; use odoo_list_databases and odoo_switch_database
to select among them. odoo-mcp-onboard remains a terminal fallback. Both flows
save validated credentials in the owner-only local file. For Cowork, credentials
must remain in the selected user's OpenCrane-backed custody. Do not paste an API
key into chat to repair either path.
"Odoo authentication failed"
Double-check:
Odoo URL (must include https://)
Database name (case-sensitive)
Email matches your Odoo login
API key is valid (generate new one in Odoo Settings > Users > API Keys)
"SafetyViolation: BLOCKED"
This is intentional! The tool attempted an operation that could send external communication. If you believe this is a false positive, please file an issue. Do NOT disable SafetyGuard.
Contributing
Contributions welcome! Please:
Add tests for new tools (especially safety tests)
Update docs and examples
Run pytest src/mcp/odoo/tests/test_safety.py before submitting PRs
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Perguntas
Como instalo Odoo?
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Odoo precisa de uma chave de API?
Este registro não lista nenhuma variável de ambiente obrigatória.
Qual transporte Odoo usa?
Odoo roda localmente via stdio.
Quando Odoo foi verificado pela última vez?
Última verificação: 2026-10-28. Open-source MCP server which connects your Clawd/Claude to Odoo in a clean and safe way