odouche-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ODOUCHE_SESSION | No | The Odoo.sh session (`session_id` cookie of `www.odoo.sh`). Used instead of the keyring, kept in memory only. For CI, containers, and machines without a keyring. Where there is no keyring, start the server with ODOUCHE_SESSION in its environment (never write the value in a config file). |
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, |
| get_firewallA | Read the firewall of a project: the public IPv4 addresses and ranges that may reach its production and staging builds by SSH, and by PostgreSQL on a dedicated server. Returns: the firewall: the project's name and its |
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 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.