Skip to Content

Odoo Claude Code — AI Terminal, MCP Agent & Claude AI Integration

by
Odoo

$ 600.00

v 18.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 4790
Technical Name claude_code_integration
LicenseOPL-1
Websitehttps://apps.odoo.com/apps/modules/browse?search=globalops
Versions 18.0 19.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 4790
Technical Name claude_code_integration
LicenseOPL-1
Websitehttps://apps.odoo.com/apps/modules/browse?search=globalops
Versions 18.0 19.0
Odoo Claude Code

Odoo Claude Code

A fully functional Claude Code terminal embedded directly inside the Odoo backend. Write code, query your database, and build Odoo modules — powered by Anthropic AI — without leaving your ERP.

Odoo 18 Claude AI On-Premise & Odoo.sh Live Database Access

Why Odoo Claude Code?

Every Odoo developer knows the drill: open a separate terminal, switch to the project folder, start Claude Code, then alt-tab back and forth between your ERP and your AI assistant. It breaks flow, wastes time, and makes context-sharing awkward.

Odoo Claude Code eliminates that friction by embedding a real claude terminal directly inside the Odoo backend. Claude connects to your live database automatically — so it can answer questions using your actual schema, installed modules, and real records without any manual setup.

Each user gets their own isolated session and credential store. Authentication is handled through Claude's standard login flow — no API keys stored in the database. Works on-premise and on Odoo.sh.

Module Demonstration

Watch the Full Module Walkthrough

See how to install the module, launch a Claude Code terminal session from inside Odoo, use the postgres-mcp MCP server to query your live database, manage workspaces, and review the per-user audit log — all without leaving your browser.

How It Works
1

Open the Terminal from the Odoo Backend

A dedicated Claude Code menu appears in the Odoo app switcher. Click Terminal to launch a full Claude Code session right inside your browser — no separate window needed.

2

Each User Gets Their Own Isolated Session

Every Odoo user runs their own independent Claude session on the server. Sessions are completely separated — credentials, history, and files are never shared between users.

3

Claude Connects to Your Live Database

A read-only database connection is automatically configured at session start. Claude can query your schema, list models, and read records — no manual setup required.

4

Odoo Development Skill Pre-Installed

A built-in Odoo skill gives Claude immediate knowledge of Odoo conventions, ORM patterns, and module structure from the very first command.

5

Every Action is Audited

Session start/stop, workspace switches, and configuration changes are logged per user and viewable from the Odoo backend — full visibility without digging through server logs.

Real Claude Code — Inside Odoo

✦ Full Claude CLI — No Emulation

This is not a chatbot widget. It is the real claude command-line tool running in a PTY — with slash commands, agentic file editing, MCP tool calls, and full multi-turn context. Below is a representative session: Claude queries the Odoo database through postgres-mcp and generates a new Odoo model.

Claude Code — Odoo Backend Terminal
odoo@sh $ claude
╔══════════════════════════╗
║ Claude Code v1.x.x ║
╚══════════════════════════╝
Tip: Use /login to authenticate with Anthropic

> List all installed modules that depend on sale

● Using postgres-mcp → query(sql=...)
┌──────────────────────────────────┬──────────┐
│ name │ state │
├──────────────────────────────────┼──────────┤
│ sale_management │ installed│
│ sale_stock │ installed│
│ digital_catalog_orders │ installed│
│ claude_code_integration │ installed│
└──────────────────────────────────┴──────────┘

> Create a new odoo 18 model called fleet.maintenance.log

● Writing models/fleet_maintenance_log.py …
● Writing views/fleet_maintenance_log_views.xml …
● Writing security/ir.model.access.csv …
✔ Done — 3 files created. Run `odoo-bin -u my_module` to apply.
Feature Highlights

1 User Groups & Access Control

Three dedicated security groups control access at a granular level: Claude User (can open a terminal), Claude Manager (can view all sessions and audit logs), and Claude Administrator (full configuration rights — MCP servers, workspaces, system settings). Administrators are granted access automatically on install.

User groups and access control
Claude / User
• Open terminal
• Own session management
• Own audit log
Claude / Manager
• All sessions read
• All audit logs
• Workspace assign
Claude / Administrator
• MCP server config
• System settings
• All permissions above

2 Dedicated Claude Code Menu in Odoo Backend

A top-level Claude Code menu appears in the Odoo app switcher after installation. From here, users access the terminal, managers review sessions and audit logs, and administrators configure MCP servers, workspaces, and system parameters — all without leaving Odoo.

Dedicated Claude Code menu in Odoo backend
── Odoo App Switcher ──────────────────────────────
⬡ Claude Code
Sales
Inventory
Accounting
── Claude Code Sub-Menu ───────────────────────────
Terminal          → Open Claude CLI
Sessions         → Active & past PTY sessions
Workspaces       → Git repos / project roots
MCP Servers      → postgres-mcp + custom servers
Audit Log        → Per-user event trail
Configuration    → System settings (admin only)

3 Workspace Management

Workspaces map to filesystem directories — typically an Odoo addons folder or a git repository. Each workspace has a name, path, and optional git remote. Users can switch workspaces from the terminal view dropdown, and managers can trigger a git pull on any workspace directly from the backend form without SSH access.

Workspace management
# Workspace: odoo_addons_go
path: /home/usertest/odoo/odoo19/odoo_apps_go
git: git@github.com:your-org/odoo-apps.git
branch: 19.0

# Switch workspace in Claude terminal view
▼ Workspace: [ odoo_addons_go ▾ ]
└─ odoo_src
└─ my_custom_modules

4 postgres-mcp — Live Database Access for Claude

At session start, a read-only database connection is automatically configured for Claude. It can run SELECT queries, introspect the schema, and pull context from live data — making answers database-aware without any copy-paste, and without any manual setup on your part.

postgres-mcp live database access for Claude
> What custom fields are on res.partner in this database?

● postgres-mcp → query(sql=
"SELECT name, ttype, field_description
FROM ir_model_fields
WHERE model = 'res.partner'
AND state = 'manual'"
)

┌────────────────────────┬───────────┬────────────────────────┐
│ name │ ttype │ description │
├────────────────────────┼───────────┼────────────────────────┤
│ x_test_field_code │ char │ test field Code │
│ x_users_ids │ many2many │ Assigned userss │
└────────────────────────┴───────────┴────────────────────────┘

5 Per-User Credential Isolation

Each Odoo user's Claude session runs in a private directory on the server. Authentication tokens, conversation history, and preferences are completely separated — one user cannot see another's sessions or credentials.

Per-user credential isolation via CLAUDE_CONFIG_DIR
# User: usertest (uid=2)
CLAUDE_CONFIG_DIR=/var/lib/odoo/.claude/users/2/

# User: usertest2 (uid=7)
CLAUDE_CONFIG_DIR=/var/lib/odoo/.claude/users/7/

# Directories are created on first session start.
# No cross-user file access is possible.

6 Session Management & Monitoring

Managers can see all active and past Claude sessions from the Sessions list view. Each record shows the user, workspace, start time, end time, and session state. Orphaned sessions (e.g. after a server restart) are automatically detected and marked as terminated.

Session management list view Session management detail view
── Claude Code / Sessions ─────────────────────────────────────────────
User Workspace Started Duration State
usertest odoo_apps_go 2026-06-17 09:12 1h 24m ● active
usertest2 odoo_src 2026-06-17 08:00 42m ● closed
sara odoo_apps_go 2026-06-16 16:55 3h 10m ● closed

7 MCP Server Configuration

Beyond the default postgres-mcp, administrators can register additional MCP servers from the Odoo backend — for example, a file-system MCP, a GitHub MCP, or any custom tool server. Each MCP server record stores the command, arguments, and environment variables. On session start, all active MCP servers are injected into the Claude CLI config automatically.

MCP server configuration in Odoo admin
# ~/.claude/claude_code_mcp_config.json (auto-generated per user)
{
"mcpServers": {
"postgres-mcp": {
"command": "uvx",
"args": ["postgres-mcp", "--access-mode=readonly"],
"env": { "DATABASE_URI": "postgresql://odoo:***@localhost/mydb" }
},
"filesystem": {
"command": "npx",
"args": ["@modelcontextprotocol/server-filesystem", "/home/usertest/odoo"]
}
}
}

8 Audit Log — Full Visibility

Every significant event is recorded with timestamp, user, and event type. This includes session open/close, workspace switches, and configuration changes. Managers can filter by user or date range and export to Excel.

Audit log full visibility per user
── Claude Code / Audit Log ────────────────────────────────────────────
Timestamp User Event Detail
2026-06-17 09:12:03 usertest session_opened workspace=odoo_apps_go
2026-06-17 09:45:17 usertest workspace_switch → odoo_src
2026-06-17 10:36:44 usertest session_closed duration=1h24m

9 Authentication — No Tokens in Odoo

Authentication is handled entirely inside the terminal. On first use, the user runs /login in the Claude CLI. Anthropic's standard OAuth flow opens in a new browser tab, and the resulting credential is stored in the user's private CLAUDE_CONFIG_DIR — never in the Odoo database, never in a config parameter, never visible to other users or admins.

Authentication step 1 Authentication step 2
Authentication step 3 Authentication step 4
> /login

Opening browser for Anthropic authentication …
Waiting for OAuth callback …

✔ Authenticated as usertest@company.com (Pro plan)
✔ Credentials stored in CLAUDE_CONFIG_DIR (not in Odoo)
─────────────────────────────────────────────────────
Ready. Type your first prompt below.

10 Odoo Configuration Settings

System parameters accessible via Settings → Claude Code let administrators configure the default workspace, session idle timeout, and whether the database MCP server is enabled globally.

Odoo Claude Code configuration settings panel
CLAUDE_CONFIG_DIR root:  /var/lib/odoo/.claude/users
Default Workspace:  odoo_apps_go
Session Idle Timeout:  60 minutes
postgres-mcp Enabled:  ✔ Yes (read-only)
Odoo Dev Skill Auto-Install:  ✔ Yes
Business Benefits

⚡ Everything in One Place

Stop switching between Odoo and a separate terminal. Your AI assistant lives right inside the backend — same browser, same context.

🗄️ AI That Knows Your Data

Claude has read-only access to your live database from the start. It answers questions using your actual modules, fields, and records — not guesses.

🔐 Secure & Audited

Each user has an isolated session. No credentials stored in Odoo. Every action is logged and visible to managers.

Key Features

🖥️ Real Terminal Inside Odoo

  • Full Claude Code CLI — not a chatbot widget
  • Auto-resize to fit the panel
  • Full clipboard support
  • Clickable URLs in terminal output
  • In-terminal search

🤖 AI & Database Integration

  • Read-only live database access for Claude
  • Auto-configured at session start — no setup
  • Additional MCP servers via admin UI
  • Odoo development skill pre-installed
  • Full Claude Code features (agents, hooks, skills)

🔐 Security & Isolation

  • Three-tier access control (User / Manager / Admin)
  • Per-user isolated session and credentials
  • No API keys stored in Odoo
  • Standard Anthropic OAuth login flow

📁 Workspace Management

  • Multiple named workspaces (filesystem paths)
  • Git pull from the Odoo UI — no SSH needed
  • Active workspace shown in terminal header
  • Default workspace configurable per system

📊 Sessions & Audit

  • Session list with duration and state
  • Automatic orphaned session cleanup
  • Full audit log (event, user, timestamp)
  • Manager-level cross-user visibility
  • Export to Excel / CSV

⚙️ Configuration & Portability

  • All settings in the Odoo Settings panel
  • Works on-premise and Odoo.sh unchanged
  • Configurable idle session timeout
  • Clean install and uninstall
Common Use Cases

🏗️ Odoo Module Development

Generate new models, views, security files, and controllers with AI assistance. Claude reads your existing modules and database schema to produce code that fits your conventions perfectly.

🐛 Bug Investigation

Ask Claude to explain why a workflow is broken, query the audit trail, inspect ir.rule records, or trace an error through the ORM — with full access to live data via postgres-mcp.

📊 Ad-hoc Reporting

Business analysts can ask Claude to write SQL queries against the live Odoo database, explain the data model, or produce CSV exports — without needing a separate BI tool or DBA access.

🔄 Migration & Upgrade Assistance

Upgrading from Odoo 16 to 19? Claude can read your custom modules, explain breaking API changes, and rewrite deprecated patterns — all while seeing the target database schema live.

📚 Onboarding New Developers

New team members can explore the codebase and database interactively. Claude answers questions about your specific customizations, explains domain logic, and guides development tasks.

🔧 DevOps & Server Administration

Run shell commands, inspect logs, manage git branches, and apply patches — all from inside the Odoo backend. No separate SSH session or VPN required for routine server tasks.

Requirements & Installation

📋 Prerequisites

  • odoo 18 (Enterprise recommended; Community untested)
  • Node.js + npm for the Claude Code CLI
  • uvx / pipx for postgres-mcp
  • An Anthropic Pro or Max subscription (per user)
  • Linux/macOS server (Windows Server not supported)

⚡ Quick Install

# 1. Install Claude Code CLI
npm install -g @anthropic-ai/claude-code

# 2. Install postgres-mcp
uvx postgres-mcp --help # or pipx install postgres-mcp

# 3. Drop addon in addons path & update
./odoo-bin -u claude_code_integration -d mydb

# 4. Open Odoo → Claude Code → Terminal
✔ Run /login inside the terminal on first use
Note on Odoo.sh: The module works on Odoo.sh with a few caveats: the claude binary must be available in the PATH of the Odoo worker process, and the CLAUDE_CONFIG_DIR root must point to a path writable by the Odoo user. See the README for Odoo.sh-specific configuration steps.

Ready to Bring Claude Code Into Your Odoo?

✉ Contact Us for Customization & Support

© 2026 Odoo Claude Code — Powered by Odoo & Anthropic Claude | Created by Odoo GlobalOps

More Apps from Odoo GlobalOps

Requires Claude Code CLI installed on the server. Compatible with on-premise and Odoo.sh. 

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.