Claude Connector for Odoo: Setup and User Guide (MCP Server)

Claude Connector (technical name ki_claude_integration) turns your Odoo database into a remote Model Context Protocol (MCP) server. Once it is connected, you can ask Claude questions about your Sales, CRM, Inventory and Accounting data in plain English. Claude answers from live Odoo records, and it only sees what the logged-in Odoo user is allowed to see.

This guide covers what the app is for, how to install and connect it, how to use each main feature, and where its limits are.

You can buy and install the app from the store page: Claude Connector | Odoo Remote MCP Server.

What the connector does

MCP is a standard JSON-RPC protocol that lets AI clients call tools on external systems. Claude Connector exposes Odoo through that protocol, so the following Claude apps can talk to your ERP directly:

• claude.ai in the browser
• Claude Desktop on macOS and Windows
• Claude Code, the terminal CLI

When you ask a question, Claude translates it into MCP tool operations against Odoo: search, read, count and aggregate group. Those operations run as the authenticated Odoo user, so Odoo access rights, security groups, record rules and multi-company boundaries all apply automatically.

Who it helps

• Business owners and managers who want quick answers such as "what were last month's sales by salesperson?" without building a report.
• Sales, purchasing and finance staff who need order statuses, customer history, vendor bills or unpaid invoices on demand.
• Warehouse and operations teams checking stock levels and stockouts.
• ERP admins who need AI access to Odoo but must keep control over what the AI can read and change, with an audit trail.
• Developers using Claude Code who want to inspect real Odoo data while building or debugging.

Requirements

Before you start, check that you have:

1. Odoo 19.0 or 20.0, Community or Enterprise, hosted on Odoo.sh or your own server.
2. An Anthropic Claude account. Claude Pro, Team or Enterprise is required for Claude Desktop and claude.ai.
3. A public HTTPS address for your Odoo server. Claude completes OAuth 2.1 authorization over HTTPS, so a local-only or plain HTTP address will not work for the remote login flow.

Odoo Online (SaaS) is not supported, because it does not allow custom modules.

There are no extra fees beyond your normal Claude subscription and your Odoo hosting. For the app's own price, see the store page.

Installation and setup

1. Install the module

1. Get the module from the store page.
2. Add it to your Odoo addons path (self-hosted) or your Odoo.sh repository. [CHECK: delivery format and recommended deployment steps for Odoo.sh vs self-hosted]
3. In Odoo, open the Apps menu, update the apps list if needed, search for ki_claude_integration and click Install.

2. Open the Claude Integration dashboard

1. Go to Claude AI > Dashboard.
2. Note your MCP server endpoint and the configuration instructions shown there. You will need them for every Claude client you connect.

3. Connect claude.ai

1. In claude.ai, add a custom MCP server. [CHECK: current claude.ai menu path for adding a custom MCP server / connector]
2. Paste the MCP server endpoint from the Odoo dashboard.
3. Click Connect and continue to the authorization step below.

4. Connect Claude Desktop

1. Copy the MCP configuration snippet from Claude AI > Dashboard.
2. Paste it into your Claude Desktop config. [CHECK: location of the Claude Desktop config file on macOS and Windows]
3. Restart Claude Desktop so it picks up the new server.

The snippet is generated by the dashboard for your server. Use it as shown rather than writing your own:

[CHECK: paste an example of the configuration snippet as shown in Claude AI > Dashboard, with the endpoint replaced by a placeholder]

5. Connect Claude Code

1. Follow the Claude Code instructions on the dashboard to register the MCP server endpoint. [CHECK: exact Claude Code command or config shown on the dashboard]
2. Start a Claude Code session and confirm the Odoo tools are available.

6. Authorize and start chatting

1. When Claude prompts you, click Connect.
2. You are sent to your Odoo login. Sign in with your own Odoo user and approve the request.
3. Claude receives a token through OAuth 2.1 with PKCE, and you can start asking questions.

The connector supports Dynamic Client Registration, so Claude clients can register themselves during this flow, and Refresh Token Rotation, so long-lived sessions get fresh tokens instead of reusing old ones. API Key Bearer Tokens are also supported. [CHECK: where admins create API keys and when to use them instead of OAuth]

Using the main features

Ask questions about your ERP data

Once connected, just ask. Claude decides which tools to call and which Odoo models to query. Some example prompts:

How many sales orders did we confirm last week, and what was the total?
Which products are out of stock right now?
Show me unpaid customer invoices older than 30 days, grouped by customer.
What is the order history for customer "Acme Ltd" this year?
List vendor bills received this month that are still in draft.
What is our revenue by salesperson for the last quarter?

Tips for better answers:

1. Be specific about dates ("last quarter", "since 1 March") so Claude filters correctly.
2. Name the grouping you want ("by customer", "by product category"). This helps Claude use the aggregate group tool instead of reading many records.
3. Ask follow-ups in the same conversation to narrow results.
4. Check important figures in Odoo before acting on them, especially for accounting.

Rely on native Odoo permissions

The connector does not have its own data permissions layer that bypasses Odoo. Every tool call runs under the authenticated user's session. In practice:

• A salesperson who can only see their own leads in Odoo will only get their own leads from Claude.
• A user without Accounting access cannot ask Claude for vendor bills and get them.
• Multi-company record rules still apply, so users only see data from their allowed companies.

If someone gets an unexpected "no access" result, fix it in their Odoo user groups, not in Claude.

Read-only by default, write access by choice

After installation, only querying and reporting tools are active. Claude can search, read, count and aggregate, but it cannot create, edit or delete records, or trigger actions.

To allow changes, an administrator has to enable them explicitly, per model:

1. Open the model access settings. [CHECK: menu path for per-model access controls]
2. Select the model you want to open up, for example a CRM lead model.
3. Enable only the permissions you need: Read, Edit, Create or Delete.
4. Save, then test with a non-admin user.

Even when a permission is enabled here, the user's own Odoo access rights still apply. The connector setting can narrow what Claude may do; it does not grant rights the user does not already have.

Allowlist and blocklist models

You can control which Odoo models Claude may touch at all:

• Allowlist a short list of models if you want a tightly scoped setup, for example only sales orders, products and customers.
• Blocklist specific models you never want exposed, for example payroll or other sensitive data.

[CHECK: whether allowlist and blocklist can be combined, and which takes priority]

A sensible starting point is to begin narrow and add models as your team asks for them.

Review the audit trail

Every tool call is logged with the parameters used, the user ID and a timestamp, along with the AI prompts. Use it to:

• Answer "who asked what, and when" during a compliance review.
• Spot unusual queries, such as large data pulls from sensitive models.
• Debug why Claude returned an unexpected answer by checking the exact tool call it made.

[CHECK: menu path for the audit log, and available filters or export options]

Manage and revoke sessions

The dashboard lists all active Claude connections. From there you can:

1. See which clients are connected.
2. Revoke a token or disconnect a client with one click.

Use this when an employee leaves, a laptop is lost, or you simply want to reset access. After revoking, the client has to go through OAuth authorization again to reconnect.

Tips for a safe rollout

• Start with a pilot group of a few users before enabling it company-wide.
• Keep write access off until your team is comfortable with read-only answers.
• Blocklist sensitive models on day one rather than relying on group setup alone.
• Review the audit log weekly during the first month.
• Use dedicated Odoo users with limited rights if you connect Claude Code for development work.
• Test on a staging database first if you run Odoo.sh or have a staging server.

Limitations

• Odoo Online (SaaS) is not supported. You need Odoo.sh or a self-hosted server.
• HTTPS is required. OAuth 2.1 dynamic login needs HTTPS connectivity between Claude and your Odoo server.
• Write and delete are disabled by default and must be enabled per model by an admin.
• Supported versions are Odoo 19.0 and 20.0 only.
• Answers depend on your data and permissions. If records are incomplete or a user lacks access, Claude's answer will reflect that.

FAQ

Which Claude apps can connect to Odoo?

claude.ai in the browser, the Claude Desktop application on macOS and Windows, and the Claude Code terminal CLI.

Can Claude see confidential data from other departments?

No. Claude operates with the exact Odoo credentials and access rights of the person logged in. Record rules and groups are strictly enforced.

Can Claude accidentally delete or alter ERP records?

No. The connector runs in read-only mode by default. Modification tools must be explicitly unlocked and allowlisted by an admin.

Does this require any external subscription beyond Claude?

No extra fees. You need your standard Anthropic Claude subscription and your self-hosted or Odoo.sh instance.

Does it work with Odoo Community?

Yes. It supports both Community and Enterprise on versions 19.0 and 20.0.

What protocol does it use?

Model Context Protocol (MCP) over Stream / HTTP, secured with OAuth 2.1 with PKCE or API Key Bearer Tokens.

How KalvyAI can help

We build and connect Odoo, ERPNext and Shopify systems, and we add AI agents that work inside them with human approvals, budgets and an audit trail. If you want help deploying Claude Connector, setting up HTTPS and OAuth on your server, designing model access rules, or planning a safe move from read-only to write access, contact us.

To buy and install the app, visit the store page.