Claude Connector for Odoo

io.github.technovision-devv1.4.3Updated Oct 9, 2026

Permission-aware MCP server for Odoo 18/19. OAuth 2.1; each call runs as one named Odoo user.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Connects an AI assistant to an Odoo 18/19 database through a permission-aware remote MCP endpoint, acting as one named Odoo user.

What it does
Turns an Odoo 18 or 19 database into a remote MCP server at /mcp/v1 speaking JSON-RPC 2.0, supporting initialize, tools/list, tools/call and ping. Claude and other MCP clients connect over OAuth 2.1 with PKCE, and every request runs as one named Odoo user with that user's groups and record rules. Models are exposed only by administrator allow-list, and create, update and delete are proposals by default unless an administrator enables direct writes per model and field. Reads and writes are logged with user, token, client name and source.
When to use it
Use it when an assistant should answer from live Odoo data without sharing a shared admin API key, and when access must follow each person's existing Odoo permissions. It suits teams that want per-user identity, an approval step for writes, and an audit trail of AI access.
Requirements
An Odoo 18.0 or 19.0 instance (Community or Enterprise, Odoo.sh or self-hosted) reachable over HTTPS, with the connector module and its dependency technovision_ai_core installed from the Odoo Apps Store. An administrator must name the models to expose, and each user connects via OAuth 2.1 or a per-person token.
Before you install
The server can read Odoo records and, if an administrator enables it, create, update and delete them; writes are proposals by default and should stay that way unless direct writes are clearly intended. Per-person tokens are shown once and stored only as a SHA-256 digest, so store them securely and revoke them when no longer needed. Access is limited to the connecting user's Odoo rights, so review exposed models and user permissions before rollout.

Installation

In SourceWeft

  1. Open Claude Connector for Odoo in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "odoo-claude-connector": {
      "type": "http",
      "url": "https://{odoo_host}/mcp/v1"
    }
  }
}

README

Claude Connector for Odoo: a permission-aware MCP server

Connect Claude (web, desktop or mobile) and other MCP clients to your Odoo 18 or 19 database, without handing over an admin key.

[Claude Connector for Odoo]

This module turns your Odoo into a remote Model Context Protocol (MCP) server. Claude connects with OAuth 2.1 in two clicks. Every request runs as one named Odoo user, with that user's access rights, so the AI sees exactly what that person could see in Odoo. No more.

[Demo]

Why it's different

Typical "AI for Odoo" setupClaude Connector for Odoo
IdentityOne admin API key for everyoneEach token or OAuth grant acts as one person (with_user)
What the AI can seeEverythingOnly what that user's groups and record rules allow
WritesDirectOff by default. Enabled per model and per field, and by default each write is a proposal a person approves in Odoo
AuditNoneEvery call is logged with user, token, client name and source
Connecting Claude web and mobileConfig file on one desktopOAuth 2.1 (RFC 9728 / 8414 / 7591, PKCE S256)

Features

  • Remote MCP endpoint (/mcp/v1, JSON-RPC 2.0): initialize, tools/list, tools/call, ping
  • OAuth 2.1 for Claude: protected-resource and authorization-server metadata, dynamic client registration, authorization code + PKCE S256 only, rotating refresh tokens, an approval screen served by Odoo
  • Per-person tokens for desktop clients: shown once, stored only as a SHA-256 digest, with expiry and one-click revocation
  • Tools scoped per request: tools/list returns only what that person can reach
  • Models exposed by allow-list: nothing is exposed until an administrator names the models
  • Approval workflow for writes: create, update and delete are proposals unless an administrator decides otherwise for a named model
  • Full audit trail: MCP reads and writes appear next to reads made inside Odoo
  • Odoo 18.0 and 19.0, Community and Enterprise, Odoo.sh or self-hosted

Connect Claude in two clicks

  1. Install the module on your Odoo (HTTPS required).
  2. In Odoo, open AI Assistant → Connections and choose which models to expose.
  3. In Claude, go to Settings → Connectors → Add custom connector and paste your Odoo MCP URL (https://your-odoo.example.com/mcp/v1).
  4. Approve the connection on the Odoo screen that opens. Claude now answers from your Odoo data, as you.

Desktop clients that use a config file get a ready-made JSON block from the token wizard.

[Tokens] [Audit trail]

Get it

The module is published on the official Odoo Apps Store:

It requires AI Assistant for Odoo — Permission-Aware (technovision_ai_core), which the store installs with it.

Product page and documentation: https://technovision.dev/products/mcp-server

Need it set up?

We install and configure it on your database, including Odoo.sh, and can build a custom tool for one of your workflows. Contact [email protected].

This repository is the public information page for the connector. The module itself is licensed under OPL-1 and distributed through the Odoo Apps Store.

TechnoVision · technovision.dev

Source: README.md at commit acd82f9

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.4.3LatestOct 9, 2026