MitDesk — MCP Server
| Let Claude, an IDE or another AI client use Odoo through per-user keys with narrow scope. |
Technical name minddesk_mcp.
Edition: Business and above. See Editions and how the modules fit together.
MCP (Model Context Protocol) is a standard way for an outside AI client to call tools. This module makes MitDesk an MCP server. Each client gets a key that belongs to one Odoo user.
What it adds
- Keys per user. A key is stored as a hash and shown once. You can rotate it and revoke it.
- Narrow scope. Per key: allowed models, read / update / create / delete switches, record filters, blocked fields, allowed IP ranges and a tool list.
- Rate limits. Requests per minute, per second and per day. The counters are stored on the key, so restarts do not reset them.
- OAuth sign-in. Clients can connect with OAuth: authorization code with PKCE (S256) and refresh tokens.
- Extra tools. Analytics (pivot, time series, top N, funnel, cohort), a business pulse, dataset export, a health check, and a list of reviewed actions.
- Remote MCP servers. You can also register other MCP servers, so MitDesk agents can use their tools.
- Kill switch. Set the system parameter
minddesk.mcp_enabledto False. Every request then gets "endpoint disabled" (HTTP 503).
Limits that always apply
- Same gate as chat. A tool called from outside uses the same dispatch and consent rules as the in-app agent.
- A key can only narrow. A key limits the owner's rights. It never adds to them.
- Writes need confirmation. An outside change must be confirmed with a token. Local and financial changes always use a single-use token.
Where you find it
- Configuration ▸ MCP: Keys, Business vocabulary, Remote servers
What to know
- Only part of the MCP protocol is implemented.
- A relation path onto a model with record filters is refused, not returned half-filtered.
Requirements
Needs minddesk.
Related
- Connecting an external AI
- Keys and scopes
- The modules: every module and what it needs.
- Installing MitDesk: how to add it.