Odoo MCP Server

Created By
tuanle96a year ago
MCP Server for Odoo
Overview

What is Odoo MCP Server?

Odoo MCP Server is an implementation that integrates with Odoo ERP systems, allowing AI assistants to interact with Odoo data and functionality through the Model Context Protocol.

How to use Odoo MCP Server?

To use the Odoo MCP Server, set up a configuration file or use environment variables to connect to your Odoo instance, and then utilize the provided tools to perform operations on Odoo records.

Key features of Odoo MCP Server?

  • Comprehensive integration with Odoo models and methods.
  • Secure XML-RPC communication with Odoo instances.
  • Flexible configuration options via config files or environment variables.
  • Resource pattern system for URI-based access to Odoo data.
  • Clear error handling for common API issues.
  • Stateless operations for reliable integration.

Use cases of Odoo MCP Server?

  1. Automating data entry and retrieval in Odoo.
  2. Integrating AI assistants to enhance user interaction with Odoo data.
  3. Building custom applications that leverage Odoo's ERP capabilities.

FAQ from Odoo MCP Server?

  • What programming language is Odoo MCP Server written in?

Odoo MCP Server is written in Python.

  • Is there a Docker version available?

Yes, Odoo MCP Server can be run using Docker for easier deployment.

  • How do I install Odoo MCP Server?

You can install it via pip with the command pip install odoo-mcp.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tuanle96
Star
75
Language
Python
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago