Connect your Odoo to your AI
Add the ERPeek connector once and your AI can work with all the Odoo code actually running your environment and all the data in it. Built for Claude on claude.ai and Claude Code, and open to any MCP client, Codex CLI included. Every call is logged, and no write ever executes without your approval on ERPeek.
- All your Odoo code, indexed
- Works with any MCP client
- Every call logged
- Writes gated by approval
- Revocable anytime
Why teams connect ERPeek to their AI
Not a chatbot bolted onto your ERP. A connector that gives Claude, Codex, or any MCP client the same grounded view of your Odoo that ERPeek has, with controls your account owner can audit.
The code actually running your Odoo
One connection gives your team access to every module in your environment: Odoo community, enterprise, and your own custom modules, all indexed by ERPeek. Your AI answers from the exact code your business runs on, not a generic Odoo it half-remembers.
Your data, through your environment
Once your environment is connected in ERPeek, your AI can also read the data in it: records, configuration, settings. Answers combine code and data, so "why is this invoice blocked" gets a real answer, not a guess.
Lower API costs on complex analysis
On complex Odoo analysis tasks, Claude Code with the ERPeek connector cut API costs by around 14% at equal answer quality (internal 3-seed benchmark, July 2026), and searches enterprise and custom code that a local checkout does not even contain. Semantic search finds the right file directly instead of grepping blindly through gigabytes of source.
Every call on the record
Full traceability: every single connector call is logged with who made it, which environment it touched, what was asked, and the credits charged. The account owner can audit the complete history at any time.
Writes never execute from the chat
Your AI can draft a change, but nothing runs from the conversation. Every proposal lands in an approval queue on erpeek.ai, gated by your project write policy, and only executes after a person approves it.
Built for partners and agencies
Clients share environments with you by email, with a read-only or read-write role, and can revoke access instantly. One connected workspace, every client project you have been granted.
Already paying for Claude?
Your Claude subscription already does the reasoning. On Odoo questions, what it lacks is your ground truth: the code your environment actually runs and the data in it. ERPeek supplies exactly that.
Claude on its own
- Answers from general Odoo knowledge, not the code your environment runs
- Cannot see Odoo enterprise source or your custom modules
- No access to your records, configuration, or model schemas
- No audit trail of what was asked about your ERP
Claude with the ERPeek connector
- Answers grounded in all the code your environment actually runs: community, enterprise, and your custom modules
- Reads your live data and full model schemas through your environment
- Every call logged: who asked, which environment, what was asked, credits charged
- Changes drafted in chat, executed only after approval on ERPeek
On complex Odoo analysis tasks, Claude Code with the connector measured about 14% lower API spend at equal answer quality (internal 3-seed benchmark, July 2026), and answered questions about enterprise and custom code that Claude alone cannot see at all.
Claude does the reasoning. ERPeek supplies the ground truth.
Using Codex or another MCP client instead? The same connector plugs into those too.
What the tools do
Five tools, each with a clear per-call price in ERPeek Credits. Your AI picks the right one for the question; you see every call in your log.
ask_erpeek
Full code-grounded research on your environment, the same engine as erpeek.ai. Pick a depth: Peek for fast lookups, Inspect for typical implementation questions, Deep Dive for cross-module analysis. Deeper costs more credits.
search_odoo_code
Semantic search over all the indexed source code of your environment. Your AI describes what it is looking for and gets the relevant functions, models, and views back, ranked by meaning, not keyword luck.
find_odoo_models
Instant lookup of Odoo models and their fields as they exist in your environment, custom fields included. The fastest way for your AI to get a data structure right on the first try.
read_odoo_file
Reads any file from your indexed environment, enterprise and custom modules included. When an answer cites a path, your AI can open the exact source and verify it line by line.
get_model_schema
The full schema of any model as it exists in your environment: every field, the complete inheritance chain, and the module that defines each part.
Results from our benchmark
We ran identical tasks in Claude Code with and without the ERPeek connector, against real Odoo environments. This is what changed.
Enterprise questions grounded
On 4 enterprise-only questions, Claude with ERPeek answered all 4 with real source citations. Without ERPeek, on community source only, it declined or answered from memory without verification on all 4.
Cited enterprise files verified
Every enterprise file cited in the answers was verified to exist in the actual enterprise source tree, checked file by file.
API cost on complex analysis
On complex analysis tasks, Claude Code with the connector cut API costs by around 14% at equal answer quality, measured across 3 seeds with blind pairwise judging.
Enterprise coverage: 4/4 grounded vs 0/4
Four questions that can only be answered from Odoo enterprise source:
- Helpdesk SLA rules
- Planning shift publication
- Documents workflow rules
- Extending helpdesk.ticket
Claude without ERPeek
0/4- Declined or answered from memory, without verification, on all 4 questions
- Community source only: the enterprise files are not there to cite
Claude with ERPeek
4/4- Answered all 4 questions with real source citations
- 100% of cited enterprise files verified to exist in the actual enterprise source tree
“Trace what happens to stock when a sale order is confirmed”
With the connector: the full mechanism traced, with file and line citations. Complex analysis tasks like this one are where the connector cut API costs by around 14% at equal answer quality.
Every call priced and logged
Not a benchmark number, just how the connector works: every tool call writes an audit log line and shows the credits it charged, so the account owner can audit the complete history.
Internal benchmark, July 2026: identical tasks run in Claude Code with and without the ERPeek connector, blind-judged for quality; enterprise citations verified file-by-file against the real source tree.
Accountable by design
Giving an AI access to your ERP is a decision. These are the controls that make it a safe one.
- You authenticate with a standard OAuth login on your ERPeek account, MFA supported. Your AI client never sees your Odoo credentials; they never leave ERPeek.
- Every connector call is logged: who, which environment, what was asked, credits charged. The account owner can audit everything.
- Writes are never executed from the chat. Proposals go to an approval queue on erpeek.ai, gated by your project write policy.
- Access is revocable from both sides at any time: remove the connector in your MCP client, or revoke the connection from your ERPeek account.
- Partners only see the projects a client has explicitly shared with them, and a client can revoke that sharing instantly.
One connection, every client project
If you are an Odoo partner or consultant, one Claude or Codex workspace serves all your clients: the connector works across every environment your clients share with you.
- Clients invite your email address from their project sharing settings, with a read-only or read-write role.
- Shared environments appear directly in your conversations, next to your own projects, whichever MCP client you use.
- A client can revoke your access instantly, and the change applies to the connector immediately.
- Your account pays the credits for the questions you ask, regardless of whose project you are asking about.
Set up in about a minute
In claude.ai
- 1In claude.ai, open Settings and go to Connectors
- 2Click "Add custom connector"
- 3Paste the connector URL: https://mcp.erpeek.ai/mcp
- 4Click Connect
- 5Log in with your ERPeek account when prompted
- 6Approve the access request, and the ERPeek tools appear in your Claude conversations
In Claude Code
Working in the terminal? Add ERPeek to Claude Code with one command, then log in with your ERPeek account when prompted.
claude mcp add --transport http erpeek https://mcp.erpeek.ai/mcpOther MCP clients
ERPeek is a standard remote MCP server: HTTP transport with OAuth login. Any MCP client that supports remote servers can connect, Codex CLI included.
- 1Add a remote MCP server in your client and point it at the endpoint below
- 2Use the HTTP transport if your client asks for one
- 3Complete the OAuth login with your ERPeek account when the browser opens
https://mcp.erpeek.ai/mcpFrequently Asked Questions
No ERPeek account yet?
Create one free and get 1,000 ERPeek Credits to try it, no credit card required.