Server data from the Official MCP Registry
Full Odoo access for AI agents via MCP: CRUD, website, translations, attachments, workflows.
Full Odoo access for AI agents via MCP: CRUD, website, translations, attachments, workflows.
OdooSurface MCP is a well-structured Odoo integration server with proper authentication requirements and user-scoped access controls. Credentials are correctly handled via environment variables, and the codebase demonstrates thoughtful permission scoping aligned with Odoo's user-level ACLs. Minor code quality observations exist but do not represent meaningful security risks. Supply chain analysis found 8 known vulnerabilities in dependencies (1 critical, 4 high severity). Package verification found 1 issue.
5 files analyzed · 13 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: ODOO_URL
Environment variable: ODOO_DB
Environment variable: ODOO_USERNAME
Environment variable: ODOO_PASSWORD
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-solutionsunity-odoo-surface-mcp": {
"env": {
"ODOO_DB": "your-odoo-db-here",
"ODOO_URL": "your-odoo-url-here",
"ODOO_PASSWORD": "your-odoo-password-here",
"ODOO_USERNAME": "your-odoo-username-here"
},
"args": [
"-y",
"@suco/odoo-surface-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
User-equivalent Odoo access for AI agents — what the authenticated user can do in their browser, nothing more.
npx — no extra install needed)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.
.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.
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.
ODOO_PASSWORD — the actual account password is never storedODOO_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.
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
.envfile approach (Option A) does not work for multi-instance setups — both processes share the same working directory and would load the same file. Use theenvblock per entry instead.
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"]
| 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, get_fields, get_defaults, get_filters, list_snippets, get_snippet, list_attachments, fetch_and_upload, translation_get, translation_update |
| Intent | create, update, execute_action, archive, post_message, schedule_activity, set_page_arch, set_page_visibility |
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.
| 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 |
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.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
by Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
by mcp-marketplace · Developer Tools
Scaffold, build, and publish TypeScript MCP servers to npm — conversationally
by mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.