odouche-mcp
Related Servers
Alternatives to odouche-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables ChatGPT to interact with Odoo by providing tools for repository management, git operations, Odoo.sh management, Odoo RPC, browser screenshots, and approval workflows.-

oec.sh MCP serverofficial
AlicenseNot gradedqualityBmaintenanceLets MCP clients such as Claude Code, Claude Desktop and Cursor work with an oec.sh organization by listing servers, projects, environments and backups, reading live Odoo logs, metrics and task progress, and running deploys, restarts, module updates and manual backups under the user's own API key. Every tool is a thin call to the oec.sh Public API, so the key's type, scope, plan, quotas and audit log all still apply.471 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables AI clients and workflow tools to search, read, create, and update Odoo projects and tasks, and to manage website page content including publishing and unpublishing, through named tools with explicit field allowlists. Access is role-controlled via bearer tokens and per-user Odoo instance scoping, with Odoo's own permissions and record rules enforced as a second layer.LGPL 3.0
- AlicenseAqualityCmaintenanceEnables AI assistants to manage Odoo development environments by providing tools for server control, module management, database operations, and project navigation.47 npm2MIT
- FlicenseAqualityBmaintenanceEnables agents to interact with self-hosted Odoo project tasks, chatter, and timesheets through nine typed tools for viewing, updating, and logging work.9-
- FlicenseAqualityBmaintenanceEnables AI agents to safely interact with GitHub, query Postgres read-only, check deployment status, and search/read files within an allowlisted sandbox—all with dry-run writes and SQL/path safety gates.8-
TDQS
Scored across 8 tools
Each tool targets a distinct resource and action: session state, projects, branches, builds, a single build, waiting on a build, logs, and firewall. The only near-pair is get_build vs wait_for_build, but the descriptions clearly separate 'read now' from 'poll until finished'.
All names follow a consistent snake_case verb_noun pattern (list_projects, list_branches, list_builds, get_build, wait_for_build, read_log, get_firewall, get_session). The get_/read_ verb split is semantically coherent rather than a convention clash.
Eight tools is well-scoped for a read-only Odoo.sh inspection surface, with each tool earning its place (list, get, wait, read, session, firewall). No redundant or filler tools.
The read surface is solid: session, projects, branches, builds, logs, and firewall are all covered with sensible get/list/wait depth. It is entirely read-only, so any mutation workflows (create/edit firewall, manage branches) are absent, though that may be intentional for this diagnostic server.