Odoo Surface MCP

Name: Odoo Surface MCP
Author: solutionsunity

作者：solutionsunity版本 0.6.1i★ –i在你的电脑上运行

注册名称io.github.solutionsunity/odoo-surface-mcp

安装

概览

作者提供的说明（英文原文）

Full Odoo access for AI agents via MCP: CRUD, website, translations, attachments, workflows.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：ODOO_URL, ODOO_DB, ODOO_USERNAME, ODOO_PASSWORD

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： ODOO_URL, ODOO_DB, ODOO_USERNAME, ODOO_PASSWORD

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "odoo-surface": {
      "command": "npx",
      "args": [
        "-y",
        "@suco/odoo-surface-mcp"
      ],
      "env": {
        "ODOO_URL": "your-value",
        "ODOO_DB": "your-value",
        "ODOO_USERNAME": "your-value",
        "ODOO_PASSWORD": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add odoo-surface --env ODOO_URL=your-value --env ODOO_DB=your-value --env ODOO_USERNAME=your-value --env ODOO_PASSWORD=your-value -- npx -y @suco/odoo-surface-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "odoo-surface": {
      "command": "npx",
      "args": [
        "-y",
        "@suco/odoo-surface-mcp"
      ],
      "env": {
        "ODOO_URL": "your-value",
        "ODOO_DB": "your-value",
        "ODOO_USERNAME": "your-value",
        "ODOO_PASSWORD": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "odoo-surface": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@suco/odoo-surface-mcp"
      ],
      "env": {
        "ODOO_URL": "your-value",
        "ODOO_DB": "your-value",
        "ODOO_USERNAME": "your-value",
        "ODOO_PASSWORD": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

ODOO_URL 必填 env
Odoo instance URL (e.g. https://myodoo.com)
ODOO_DB 必填 env
Odoo database name
ODOO_USERNAME 必填 env
Odoo login username
ODOO_PASSWORD 机密必填 env
Odoo login password

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 solutionsunity 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32476 个服务器的 0%
发布到注册中心的时间比此分类中其他 32476 个服务器的 55% 更新
基础检查结果等于或优于此分类中其他 32476 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Odoo Surface MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：ODOO_URL, ODOO_DB, ODOO_USERNAME, ODOO_PASSWORD

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.6.1）于34天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, zanadir

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新

安装

zanadir

作者：MustacheCase

Find what a repository's CI is missing, and which security checks cannot fail the build.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

OdooSurface MCP

User-equivalent Odoo access for AI agents — what the authenticated user can do in their browser, nothing more.

Prerequisites

Node.js 18+ (ships with npx — no extra install needed)
A running Odoo instance (15.0+, CE or EE) — per-version behaviour of every call: docs/compatibility.md
An MCP-compatible client (VS Code, Claude Desktop, Claude Code, Cursor, …)

Configure your MCP client

Add this to your MCP client config (e.g. Claude Desktop claude_desktop_config.json):

"mcpServers": { "odoo-surface": { "command": "npx", "args": ["-y", "@suco/odoo-surface-mcp@latest"], "env": { "ODOO_URL": "http://localhost:8069", "ODOO_DB": "your_database", "ODOO_USER": "admin", "ODOO_PASSWORD": "admin" } } } }

Restart your MCP client after saving. npx downloads and runs the package automatically — no further install steps.

Authentication

Option A — `.env` file (keep credentials out of MCP config)

Instead of putting credentials in your MCP client JSON, create a .env file in the directory where you run the MCP:

ODOO_URL=http://localhost:8069

ODOO_DB=your_database ODOO_USER=admin ODOO_PASSWORD=your_password

Remove the env block from the MCP client config — the .env file is loaded automatically.

Option B — API Key (recommended, no password stored)

Since Odoo 14+, users can generate personal API keys that act as a password replacement. Each user generates their own key from their own account — there is no admin-side menu for this.

Log in as the user the MCP will authenticate as
Click the user avatar (top-right) → Preferences
Go to the Account Security tab
Under API Keys → click New API Key
Enter your password when prompted, give the key a name, copy the generated key
Use it as ODOO_PASSWORD — the actual account password is never stored

ODOO_URL=http://localhost:8069

ODOO_DB=your_database ODOO_USER=admin ODOO_PASSWORD=your_api_key_here

API keys can be revoked individually from the same screen without changing the account password.

Advanced Configuration

Multiple Odoo instances

Technical users commonly work with more than one Odoo instance (local dev, staging, production). Each instance gets its own named entry in the MCP config — they run as independent processes with fully isolated credentials. The AI client exposes them as separate tool namespaces.

"mcpServers": { "odoo-local": { "command": "npx", "args": ["-y", "@suco/odoo-surface-mcp@latest"], "env": { "ODOO_URL": "http://localhost:8069", "ODOO_DB": "dev", "ODOO_USER": "admin", "ODOO_PASSWORD": "dev_api_key" } }, "odoo-production": { "command": "npx", "args": ["-y", "@suco/odoo-surface-mcp@latest"], "env": { "ODOO_URL": "https://mycompany.odoo.com", "ODOO_DB": "prod", "ODOO_USER": "admin", "ODOO_PASSWORD": "prod_api_key" } } } }

Note: The .env file approach (Option A) does not work for multi-instance setups — both

processes share the same working directory and would load the same file. Use the env block

per entry instead.

Debug mode

Registers additional tools: ping, echo, inspect_view, inspect_action, inspect_fields, dump_cache, clear_cache, restart_mcp.

"args": ["-y", "@suco/odoo-surface-mcp@latest", "--debug"]

Tools

Layer	Tools
Guidance	`list_skills`, `get_skills`, `find_skill`, `list_workflows`, `get_workflows`
Discovery	`get_models`, `get_model_actions`, `get_model_interface`
Planning	`get_available_actions`
Supporting	`list_records`, `get_record`, `search_records`, `read_group`, `get_fields`, `get_defaults`, `get_filters`, `list_pages`, `get_page_arch`, `list_snippets`, `get_snippet`, `list_attachments`, `download_binary`, `fetch_and_upload`, `translation_get`, `translation_update`, `translation_audit`
Intent	`create`, `update`, `execute_action`, `archive`, `post_message`, `schedule_activity`, `create_page`, `set_page_arch`, `set_page_visibility`, `upload_binary`

Architecture

Core Contract

The agent may only do what the authenticated user can do in their browser. Scope is bounded by the user's menus, views, and ACL — nothing more. Tool verbs express functional intent (publish, confirm) rather than raw ORM operations. Discovery is lazy: the agent resolves only what the current prompt requires.

Layered Tool Surface

Layer	Role	When invoked
0 — Guidance	Canonical recipes (skills, workflows) the agent consults before any multi-step operation. Pure documentation, no side effects.	Before planning
1 — Discovery	Establishes the bounded universe of models and reachable relations for the current user.	At intent resolution
2 — Planning Bridge	Answers "what is live on this specific record right now" — record-state-aware actions.	Once a record is identified
3 — Supporting	Read-only data fetchers used silently to fill gaps in the agent's plan.	Throughout planning
4 — Intent	Mutating actions that fulfill the user's request — bounded by the user's UI permissions.	Final execution

Planning Loop

User prompt

├── Discovery — what models/relations does this user have? ├── (optional) — locate the specific record ├── Planning Bridge — what is live on that record right now? ├── Guidance — consult skills/workflows for multi-step recipes └── Intent — execute the mutation(s)

Skills and workflows are authored in skills/ and workflows/ as markdown with YAML frontmatter; they are exposed as Layer 0 tools at runtime.