Other · Local MCP server
Odoo MCP
Workflow-native MCP server for safe Odoo Enterprise back-office operations.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ebmurha/odoo-mcp- Version
- 0.3.0
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-09-27
- Updated
- 2026-09-27
- Publisher
- ebmurha (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/ebmurha) · how
- Listed under
- Odoo MCP servers
- Website
- github.com/ebmurha/odoo-mcp
- Repository
- github.com/ebmurha/odoo-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | odoo-erp-mcp | 0.3.0 | stdio |
How to connect Odoo MCP
Odoo MCP runs locally from a Python package published to PyPI: odoo-erp-mcp version 0.3.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx odoo-erp-mcp. It reads these environment variables: ODOO_MCP_ODOO_URL (required), ODOO_MCP_ODOO_DATABASE (required), ODOO_MCP_ODOO_USERNAME (required), ODOO_MCP_ODOO_API_KEY (required, secret), ODOO_MCP_ALLOWED_COMPANY_IDS (required) and ODOO_MCP_DEFAULT_COMPANY_ID (required); set them in the client's configuration for this server. Required arguments: --config.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"odoo-mcp": {
"command": "uvx",
"args": [
"odoo-erp-mcp"
],
"env": {
"ODOO_MCP_ODOO_URL": "<value>",
"ODOO_MCP_ODOO_DATABASE": "<value>",
"ODOO_MCP_ODOO_USERNAME": "<value>",
"ODOO_MCP_ODOO_API_KEY": "<secret>",
"ODOO_MCP_ALLOWED_COMPANY_IDS": "<value>",
"ODOO_MCP_DEFAULT_COMPANY_ID": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Odds Api MCP ServerLive sports betting odds from 365+ bookmakers across 34 sports, with value bets and arbitrage. | Local · stdio |
| Oddsradarwire - Live & Prematch Betradar Odds with No-Vig ProbabilitiesLive and prematch Betradar odds with no-vig fair prices. Free demo access, no key. | Remote · HTTPLive check: ✗ no handshake |
| Odgs MCP ServerODGS governance enforcement - validation, regulation compilation, drift detection, signed S-Certs. | Local · stdio |
| OdooOdoo ERP for AI agents: hosted OAuth endpoint, gated writes, one endpoint for every instance. | Remote · HTTPLive check: ✗ no handshake |
| Odoo MCP by bancadaConnect any AI assistant to Odoo 16-19 via OAuth 2.0 + PKCE. 400 free calls, no local install. | Remote · HTTPLive check: sign-in required |
| Odoo MCP ConnectorQuery, report on, and optionally modify any Odoo ERP from Claude. Read-only by default. | Local · stdio |
| Odoo PulseAn AI business analyst for Odoo ERP (18+) - one-call reports with verdicts, over MCP. | Local · stdio |
| Odoo Surface MCPFull Odoo access for AI agents via MCP: CRUD, website, translations, attachments, workflows. | Local · stdio |