odoo-sh-readonly-mcp
Provides read-only access to Odoo.sh projects, including builds, branches, environments, logs, and system status via web API and SSH.
Allows listing PostgreSQL databases and their sizes on the Odoo.sh environment.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@odoo-sh-readonly-mcp Show me the latest build statuses for my Odoo.sh project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
odoo-sh-readonly-mcp 🔒
MCP solo lectura para Odoo.sh: builds, entornos, logs y estado del sistema — consultable por una AI sin entrar a la web.
Sin tools de escritura: no hay git push, ni shell arbitrario, ni escritura de archivos. SSH via execFile (sin shell → sin command injection) con comandos whitelisted. El smoke test de CI falla el build si alguna vez aparece una tool con nombre de escritura o sin readOnlyHint.
📑 Tabla de contenidos
Related MCP server: readonly-mcp-akamai
🧰 Tools
Tool | Fuente | Qué da |
| Web API | Repos + branches con stage (production/staging/dev) y último build |
| Web API | Builds recientes con status real (success/failed/testing) |
| Web API | Introspección de campos de modelos |
| Web API | Query genérica read-only (whitelist |
| SSH |
|
| SSH | Hostname, uptime, disco, memoria, versiones |
| SSH | DBs PostgreSQL y tamaños |
| — | Diagnóstico de configuración (sin exponer secretos) |
🐳 Instalación via imagen GHCR (recomendado)
Cada push a main publica una imagen multi-arch (amd64/arm64) en GitHub Container Registry:
ghcr.io/ai-zar/odoo-sh-readonly-mcp:latest1. Autenticarse contra GHCR
El repo es privado, así que la imagen también. Necesitás un PAT con scope read:packages:
echo $GITHUB_PAT | docker login ghcr.io -u TU_USUARIO --password-stdin
docker pull ghcr.io/ai-zar/odoo-sh-readonly-mcp:latest2. Configurar el cliente MCP
Solo builds/entornos (sin SSH):
{
"mcpServers": {
"odoo-sh": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-e", "ODOO_SH_SESSION_ID",
"-e", "ODOO_SH_PROJECT",
"ghcr.io/ai-zar/odoo-sh-readonly-mcp:latest"
],
"env": {
"ODOO_SH_SESSION_ID": "tu_session_id",
"ODOO_SH_PROJECT": "mi-proyecto"
}
}
}
}Con SSH (logs / system / DBs) — montá la clave privada read-only:
{
"mcpServers": {
"odoo-sh": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-v", "/home/usuario/.ssh/odoo_sh:/keys/id:ro",
"-e", "ODOO_SH_SESSION_ID",
"-e", "ODOO_SH_SSH_HOST",
"-e", "ODOO_SH_SSH_USER",
"-e", "ODOO_SH_SSH_KEY_PATH",
"ghcr.io/ai-zar/odoo-sh-readonly-mcp:latest"
],
"env": {
"ODOO_SH_SESSION_ID": "tu_session_id",
"ODOO_SH_SSH_HOST": "mi-proyecto.dev.odoo.com",
"ODOO_SH_SSH_USER": "BUILD_ID",
"ODOO_SH_SSH_KEY_PATH": "/keys/id"
}
}
}
}⚠️ En Windows usá rutas estilo
C:\\Users\\usuario\\.ssh\\odoo_sh:/keys/id:roen el-v.ODOO_SH_SSH_KEY_PATHsiempre apunta a la ruta dentro del contenedor (/keys/id).
3. Probar la imagen a mano
docker run -i --rm -e ODOO_SH_SESSION_ID=xxx \
ghcr.io/ai-zar/odoo-sh-readonly-mcp:latestPegá esto en stdin para ver las tools:
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"cli","version":"1"}}}
{"jsonrpc":"2.0","id":2,"method":"tools/list"}💻 Instalación local (Node)
git clone https://github.com/ai-zar/odoo-sh-readonly-mcp.git
cd odoo-sh-readonly-mcp
npm install
npm run smoke # verifica que arranca y expone las 8 tools{
"mcpServers": {
"odoo-sh": {
"command": "node",
"args": ["C:\\ruta\\absoluta\\odoo-sh-readonly-mcp\\index.js"],
"env": { "ODOO_SH_SESSION_ID": "tu_session_id" }
}
}
}⚙️ Configuración
Variable | Requerida | Descripción |
| ✅ (web) | Cookie |
| ❌ | Repo por defecto para filtrar |
| ❌ | Default |
| ✅ (ssh) |
|
| ✅ (ssh) |
|
| ✅ (ssh) | Ruta a la clave privada |
| ❌ | Default |
| ❌ | Default |
🍪 Obtener la cookie de sesión
Odoo.sh no expone API pública; su panel web es un Odoo estándar. Se usa tu propia sesión:
Logueate en https://www.odoo.sh
F12 → Application → Cookies →
www.odoo.sh→ copiásession_id
La cookie expira: cuando las llamadas fallen con error de sesión, repetí el paso. Los permisos son exactamente los de tu usuario — ni más ni menos.
💬 Ejemplos de uso con AI
"¿Cómo están los builds de staging?"
"¿Falló algún build esta semana en main?"
"Mostrame los últimos errores del log de producción"
"¿Cuánto pesa la DB de producción?"
"Listame todos los entornos y en qué commit está cada uno"
🔬 Nota técnica: modelos paas.*
Los modelos internos de Odoo.sh (paas.build, paas.branch, ...) no están documentados y sus campos pueden cambiar. Por eso:
resilientSearchRead: si un campo no existe, reintenta pidiendo todos los campos legiblesodoo_sh_model_fields: la AI puede autodescubrir el schema y después consultar con precisión viaodoo_sh_search_read
Primera vez, pedile a la AI:
"Usá
odoo_sh_model_fieldssobrepaas.buildy después listá los builds con los campos correctos"
🛡️ Seguridad
Riesgo | Mitigación |
Command injection | SSH via |
Escritura accidental | No existen tools de escritura. Whitelist de modelos + de métodos ( |
Prompt injection → acción destructiva | Superficie de ataque = solo lectura. Lo peor que puede pasar es leer datos a los que ya tenés acceso |
MITM en SSH |
|
Secretos en la imagen | Nada hardcodeado; todo por env vars. Clave SSH se monta read-only en runtime |
Supply chain | Imagen con attestation de provenance ( |
MIT — ver LICENSE.
Available Tools
8 toolsodoo_sh_databasesList databases (SSH)ARead-only
List PostgreSQL databases and sizes on the configured Odoo.sh build container. Read-only.
Inputs: no named parameters.
odoo_sh_list_buildsList Odoo.sh buildsARead-only
List recent builds with their REAL status/result (e.g. success, failed, testing) from the Odoo.sh platform API. Filter by branch name. Requires ODOO_SH_SESSION_ID.
Inputs: limit, branch.
odoo_sh_logsRead Odoo logs (SSH)CRead-only
Tail Odoo logs (odoo.log, install.log or pip.log) from the configured Odoo.sh build container via SSH. Read-only.
Inputs: grep, lines, log_type.
odoo_sh_model_fieldsDiscover Odoo.sh model fieldsARead-only
Introspect available fields on an Odoo.sh platform model (paas.repository, paas.branch, paas.build, ...). Use this if odoo_sh_list_builds/odoo_sh_overview return unexpected data, then query precisely with odoo_sh_search_read.
Inputs: model (required).
odoo_sh_overviewOdoo.sh project overviewARead-only
Get repositories, branches and their environment stage (production/staging/dev) with last build info from the Odoo.sh platform API. Use this first to understand the project layout. Requires ODOO_SH_SESSION_ID.
Inputs: project.
odoo_sh_search_readGeneric read-only query on Odoo.sh modelsARead-only
Run a search_read on a whitelisted Odoo.sh platform model with a custom domain and field list. Read-only escape hatch when the curated tools don't cover a need. Example domain: [["branch_id.name","=","main"]]
Inputs: model (required), limit, order, domain, +1 more.
odoo_sh_statusMCP configuration statusARead-only
Show which data sources are configured (web API session, SSH) without exposing secrets. Use to diagnose setup issues.
Inputs: no named parameters.
odoo_sh_system_infoSystem info (SSH)ARead-only
Hostname, uptime, disk, memory, Python and Odoo version of the configured Odoo.sh build container. Read-only.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Tools are mostly distinct with clear purposes, though overview and list_builds overlap slightly in build-related information. Overall, each tool targets a specific function and confusion is unlikely.
All tools use the consistent 'odoo_sh_' prefix followed by snake_case verbs/nouns, creating a uniform and predictable naming pattern.
8 tools is a reasonable number for a read-only Odoo.sh management surface, covering key areas without being excessive or sparse.
The set covers critical read-only operations like builds, logs, system info, databases, and model search. It lacks some advanced operations (e.g., deployment history) but for a read-only utility it is well-rounded.
Maintenance
Related MCP Connectors
Read-only MCP server for AIStatusDashboard status, incidents, metrics, and fallback recommendations.
Read-only MCP server for interior design studios: projects, overviews, weekly activity. No writes.
Read-only MCP server for public WeJob jobs, formations, and companies.
Read-only MCP for AI usage profiles, leaderboards, stats, and docs; no writes or private data.
Related MCP Servers
AlicenseAqualityDmaintenanceRead-only MCP server that allows AI assistants to query and monitor KVM Fleet devices, audit logs, and console sessions through the official REST API.58 npm1MIT- AlicenseAqualityCmaintenanceRead-only MCP server for Akamai CDN that enables searching properties, browsing EdgeWorker code, querying DNS zones, inspecting network lists, and translating error codes via natural language.1643 PyPI1MIT
- FlicenseNot gradedqualityDmaintenanceRead-only MCP server for Hevo Data API, enabling monitoring of pipelines, objects, destinations, models, and workflows with secure self-hosted credentials.-
- FlicenseNot gradedqualityDmaintenanceA read-only MCP server for observing registered local and SSH hosts, providing system, service, container, Git, and GPU status/log inspection through a closed-world registry without arbitrary shell access.-