MCP Server for Odoo

Created By
ivnvxda year ago
A Model Context Protocol (MCP) server that enables AI assistants to securely interact with Odoo ERP systems through standardized resources and tools for data retrieval and manipulation.
Overview

What is MCP Server for Odoo?

MCP Server for Odoo is a Model Context Protocol (MCP) server implementation that allows AI models to interact with Odoo data and functionality through a standardized MCP interface.

How to use MCP Server for Odoo?

To use the MCP Server, install it via pip or uv, configure it with your Odoo instance details, and run it to expose Odoo data as MCP resources.

Key features of MCP Server for Odoo?

  • Exposes Odoo data as MCP resources
  • Supports search functionality with domain filters
  • Provides pagination and summarization for large datasets
  • Easy configuration through environment variables or CLI arguments
  • Auto-detection of the default database when not specified

Use cases of MCP Server for Odoo?

  1. Integrating AI models with Odoo for data analysis.
  2. Automating data retrieval and manipulation in Odoo.
  3. Enhancing Odoo functionalities with external AI services.

FAQ from MCP Server for Odoo?

  • How do I install MCP Server for Odoo?

You can install it using pip install mcp-server-odoo or uv install mcp-server-odoo.

  • What configurations are needed?

You need to set environment variables like ODOO_URL, ODOO_DB, and authentication details.

  • Can I use it with a single-database Odoo installation?

Yes! The server can auto-detect the default database if not specified.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ivnvxd
Star
2
Language
Python
License
MPL-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago