A
licenseB
qualityD
maintenanceSSH-based Model Context Protocol server for Odoo.sh - Build custom apps with AI assistance using Git workflow tools.
19
6
MIT
odouche-mcp
by avanserv
Related Servers
Alternatives to odouche-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables seamless interaction with Odoo instances through the Model Context Protocol, supporting CRUD operations, custom method execution, and real-time updates. It offers versatile communication via stdio and HTTP protocols, including support for streaming and Server-Sent Events.8MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server integrating DevOps tools for GitHub, Docker, and filesystem operations.9MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables Claude to manage software development projects with complete context awareness and code execution through Docker environments.11 npm4-
- AlicenseAqualityDmaintenanceA Model Context Protocol server for secure local system operations, enabling shell command execution and file management via a standardized interface.141Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to interact with Odoo ERP systems, providing comprehensive tools for searching, creating, updating, and managing Odoo records through a standardized interface.23GPL 3.0
TDQS
A4.1/5.0
Scored across 7 tools
Disambiguation4/5
Each tool targets a distinct action: listing (list_projects/list_branches/list_builds), single-item read (get_build, get_session), log read (read_log), and polling (wait_for_build). The build-oriented tools (list_builds, get_build, wait_for_build, read_log) all touch builds but have clearly separated purposes, with minor potential overlap between get_build and the build data returned by wait_for_build.
Naming Consistency5/5
All names follow a consistent snake_case verb_noun pattern (list_projects, list_branches, list_builds, get_session, get_build, read_log, wait_for_build). The get_*/read_* split is a minor stylistic nuance but not a convention break.
Tool Count5/5
7 tools is well-scoped for a read-only Odoo.sh monitoring server, with each tool earning its place across the project → branch → build → log hierarchy plus session status and build polling.
Completeness4/5
The read-only surface covers the core lifecycle (discover projects, branches, builds, detailed build, logs, and build completion polling), which is coherent for a read-only server. Minor gaps exist: no dedicated single-project or single-branch detail tool, and no mutation operations, though the latter may be out of scope by design.
Maintenance
ActivityMaintained
ResponsivenessNo issues