/ ディレクトリ / プレイグラウンド / mcp-server-odoo
● コミュニティ ivnvxd ⚡ 即起動

mcp-server-odoo

作者 ivnvxd · ivnvxd/mcp-server-odoo

Query and safely update any Odoo ERP model from chat — orders, contacts, products — with smart field selection and read-only guardrails.

mcp-server-odoo connects to any Odoo 16+ instance via XML-RPC. It exposes record search/read/create/update/delete with auto-selection of meaningful fields per model, plus a YOLO-read mode for any Odoo version. Use API key auth (recommended) or user/password.

なぜ使うのか

主な機能

ライブデモ

実際の動作

server-odoo.replay ▶ 準備完了
0/0

インストール

クライアントを選択

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "server-odoo": {
      "command": "uvx",
      "args": [
        "mcp-server-odoo"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config を開く。保存後、アプリを再起動。

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "server-odoo": {
      "command": "uvx",
      "args": [
        "mcp-server-odoo"
      ],
      "_inferred": true
    }
  }
}

Cursor は Claude Desktop と同じ mcpServers スキーマを使用。プロジェクト設定はグローバルより優先。

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "server-odoo": {
      "command": "uvx",
      "args": [
        "mcp-server-odoo"
      ],
      "_inferred": true
    }
  }
}

Cline サイドバーの MCP Servers アイコンをクリックし、"Edit Configuration" を選択。

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "server-odoo": {
      "command": "uvx",
      "args": [
        "mcp-server-odoo"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop と同じ形式。Windsurf を再起動して反映。

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "server-odoo",
      "command": "uvx",
      "args": [
        "mcp-server-odoo"
      ]
    }
  ]
}

Continue はマップではなくサーバーオブジェクトの配列を使用。

~/.config/zed/settings.json
{
  "context_servers": {
    "server-odoo": {
      "command": {
        "path": "uvx",
        "args": [
          "mcp-server-odoo"
        ]
      }
    }
  }
}

context_servers に追加。保存時に Zed がホットリロード。

claude mcp add server-odoo -- uvx mcp-server-odoo

ワンライナー。claude mcp list で確認、claude mcp remove で削除。

ユースケース

実用的な使い方: mcp-server-odoo

Answer ad-hoc sales questions against Odoo

👤 Ops managers, founders using Odoo as their source of truth ⏱ ~10 min beginner

使うタイミング: 'What were last week's top 5 customers by revenue?' — without writing XML-RPC.

前提条件
  • Odoo API key — Odoo: user profile > Preferences > API Keys > New
  • ODOO_URL, ODOO_DB, ODOO_API_KEY env vars — Set in your MCP client config
フロー
  1. List available models
    list_models — which Odoo models can we query in this instance?✓ コピーしました
    → Model catalog with descriptions
  2. Run the query
    In sale.order, find orders with date_order between last Monday and today, group by partner_id, sum amount_total, top 5.✓ コピーしました
    → Ranked customer list with totals
  3. Drill in
    For the top customer, show the last 3 orders with their line items.✓ コピーしました
    → Detailed breakdown

結果: A business answer from ERP data without leaving chat.

注意点
  • Multi-currency totals aren't converted — Specify currency_id in the filter, or convert in the LLM layer
  • ODOO_YOLO=true is dangerous in prod — Use ODOO_YOLO=read or leave unset; enable full access only in a staging DB
組み合わせ: notion

Clean up stale CRM leads in Odoo

👤 Sales ops ⏱ ~30 min intermediate

使うタイミング: Leads pile up with no activity; you want to reassign or archive.

フロー
  1. Find stale leads
    In crm.lead, find leads where stage_id is not 'Won' and last activity > 60 days ago.✓ コピーしました
    → Stale lead list
  2. Propose actions
    Classify each: archive, reassign to team lead, or ping current owner.✓ コピーしました
    → Classification per lead
  3. Apply in batches (read-only first!)
    Dry run only: show what would change if I archived the 'archive' bucket.✓ コピーしました
    → Dry-run summary; then confirm before update_record

結果: A cleaner pipeline with auditable changes.

注意点
  • Archiving leads other teams depend on — Always dry-run first; tag archived leads rather than delete

Draft follow-ups for unpaid invoices

👤 AR and finance ⏱ ~25 min intermediate

使うタイミング: Monthly dunning run.

フロー
  1. Pull overdue invoices
    In account.move, find invoices where state='posted', payment_state='not_paid', invoice_date_due < today - 15.✓ コピーしました
    → Overdue list with partner + amount
  2. Draft a polite follow-up per customer
    For each, draft an email in the customer's preferred language using ODOO_LOCALE settings.✓ コピーしました
    → Per-invoice draft text

結果: Dunning emails ready to send (human still reviews).

組み合わせ

他のMCPと組み合わせて10倍の力を

server-odoo + notion

Pull a sales snapshot from Odoo, post to Notion for stakeholders

Run last-month sales by product category from Odoo, post as a Notion table under Finance / Monthly.✓ コピーしました
server-odoo + postgres

Cross-reference Odoo data with a warehouse replica for heavy analytics

For top-10 Odoo customers, pull their web-session counts from the Postgres analytics DB.✓ コピーしました

ツール

このMCPが提供する機能

ツール入力呼び出すタイミングコスト
list_models (none) First-run discovery 1 XML-RPC call
search_records model: str, domain?: filter, fields?: str[], limit?: int Any read query 1 XML-RPC call
get_record model, id Known id, need full detail 1 call
create_record model, values: object Only with ODOO_YOLO=true or API key granting write 1 call (write)
update_record model, id, values Writes — confirm first 1 call (write)
delete_record model, id Rarely — archive is usually better 1 call (write, destructive)
list_resource_templates (none) Explore available resource URIs free

コストと制限

運用コスト

APIクォータ
Bounded by Odoo server; no per-call cost
呼び出しあたりのトークン
Smart-field responses keep responses under 1k tokens per record
金額
Free; you need an Odoo instance (community or enterprise)
ヒント
Always pass explicit fields= on big models like product.template to avoid pulling 200 fields.

セキュリティ

権限、シークレット、影響範囲

最小スコープ: API key or user with read rights on the models you query
認証情報の保管: ODOO_API_KEY in env var; never commit to repo
データ送信先: Calls to your Odoo instance only
絶対に付与しない: ODOO_YOLO=true in production

トラブルシューティング

よくあるエラーと対処法

Access Denied on model

API key user doesn't have access rights for that model. Grant or switch user.

確認: Odoo: Settings > Users > Access Rights
Database not found

Set ODOO_DB explicitly; auto-detection fails when db listing is disabled.

確認: curl -d '{"jsonrpc":"2.0","method":"call","params":{"service":"db","method":"list"}}' $ODOO_URL/jsonrpc
MCP Odoo module not installed

In standard mode, install the mcp_odoo community module, or switch to ODOO_YOLO=read mode.

確認: Odoo: Apps > search mcp_odoo

代替案

mcp-server-odoo 他との比較

代替案代わりに使う場面トレードオフ
Direct XML-RPC via fetch MCPYou only need one specific queryNo smart field selection; boilerplate-heavy
postgres MCP on Odoo's DBYou want raw SQL and can connect to the underlying PostgresBypasses Odoo ACLs — dangerous without care

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

🔍 400以上のMCPサーバーとSkillsを見る