MCP-Odoo

Created By
yourtechtribea year ago
Model Context Protocol (MCP) server for Odoo integration, allowing AI agents to access and manipulate Odoo data through a standardized interface.
Overview

what is MCP-Odoo?

MCP-Odoo is a Model Context Protocol server designed for integrating Odoo ERP systems with AI agents, allowing them to access and manipulate Odoo data through a standardized interface.

how to use MCP-Odoo?

To use MCP-Odoo, clone the repository, install the dependencies, configure the environment variables, and start the MCP server using the provided commands.

key features of MCP-Odoo?

  • Easy integration with Odoo instances
  • Standard MCP interface for AI agent compatibility
  • Access to rich accounting data
  • Secure authentication with Odoo

use cases of MCP-Odoo?

  1. Accessing and analyzing partner information.
  2. Viewing and reconciling accounting data including invoices and payments.
  3. Querying vendor bills and customer invoices.

FAQ from MCP-Odoo?

  • What is the Model Context Protocol (MCP)?

MCP is a standardized interface that allows AI agents to interact with various data sources, including Odoo.

  • Is MCP-Odoo secure?

Yes! MCP-Odoo uses secure authentication methods to ensure data protection.

  • Can I contribute to MCP-Odoo?

Absolutely! Contributions are welcome, and you can submit a Pull Request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yourtechtribe
Star
2
Language
Python
License
MIT 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