odouche-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_sessionA | Report whether the server has an Odoo.sh session, where it came from and who it belongs to. Returns: whether a session is available, its source, its user and the seconds left before its max age. Touches: reads only Bounds: one request to Odoo.sh, none when there is no session. |
| list_projectsA | List the Odoo.sh projects the user can reach. Call it first: every other tool takes a project by its name. Returns: the projects, each with its name, repository and address, and |
| list_branchesA | List the branches of a project, given by its name, with the stage each sits in. Returns: the branches, each with its name and stage, and |
| list_buildsA | List the latest builds of a branch of a project, newest first, with their status, result and commit. Returns: the builds, and |
| get_buildA | Read one build of a branch of a project: the build of that number, or the latest one when none is given. Returns: the build, with its commit and the address of its database. Touches: reads only Bounds: three requests to Odoo.sh; a build older than the branch's latest ones is not found. |
| wait_for_buildA | Wait for a build of a branch of a project to finish, for Returns: the build as last seen, or none while the branch has no build of |
| read_logA | Read the last lines of a log of a build of a branch of a project: of the build of that number, or of the latest one. Without Returns: the build's number, the log's kind, |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
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.
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.
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.
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.