oec.sh MCP server
online · 96% uptimesh.oec/mcp-server·v0.3.1Operate your oec.sh Odoo servers, projects and environments with your own API key.
not scanned yet
0 stars215 downloads/wk
Reviews
Write oneNobody has reviewed oec.sh yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
oec.sh tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How oec.sh compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 91/100
- higher than 85% of 48,255 servers
- Uptime
- 96%
- of our recent checks; the typical remote server answers 100%
- Response time
- 739 ms
- faster than 18% of 30,031 servers
- Downloads a week
- 215
- more than 76% of 12,191 servers with a package
Release history: 4 versions in the registry since 2026-10-08, latest 2026-10-28, typically one every 6 days.
Install oec.sh in Claude Code, Cursor or VS Code
claude mcp add --transport http mcp-server https://mcp.oec.sh/mcp
What the publisher says
From the oec.sh repository's README, as published. We do not edit it. Read it on GitHub
oec.sh MCP server
Let an AI assistant (Claude Code, Claude Desktop, Cursor and other MCP clients) work with your oec.sh organization: look at servers, projects and environments, read an environment's Odoo logs and live metrics, deploy, restart, update modules, take backups and follow a task to its end.
The server adds no powers of its own. Every tool is one or two calls to the oec.sh Public API made with your API key, so the key's type (read only or full access), its scope (organization or one project), your plan, your quotas and the audit log all apply exactly as they do for any other API client.
Requirements: an oec.sh organization on the Starter plan or higher, and an API key from Settings > API Keys in the dashboard. Local mode needs Node.js 22 or newer.
Choose a key
A project-scoped key limits the assistant to one project. Use one whenever the assistant only needs to work on one project.
The server reads the key's type from its prefix and only offers the tools that key can use.
Install: local mode (stdio)
The MCP client starts the server on your computer. Your key stays on your computer and is sent only to api.oec.sh.
Claude Code
claude mcp add oecsh -e OECSH_API_KEY=oec_live_ro_your_key -- npx -y @oecsh/mcp-serverClaude Desktop
Add to claudedesktopconfig.json (Settings > Developer > Edit Config), then restart Claude Desktop:
{
"mcpServers": {
"oecsh": {
"command": "npx",
"args": ["-y", "@oecsh/mcp-server"],
"env": { "OECSH_API_KEY": "oec_live_ro_your_key" }
}
}
}Cursor
Add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):
{
"mcpServers": {
"oecsh": {
"command": "npx",
"args": ["-y", "@oecsh/mcp-server"],
"env": { "OECSH_API_KEY": "oec_live_ro_your_key" }
}
}
}Do not commit a file that contains your key.
Settings (local mode)
Hosted mode (streamable HTTP)
https://mcp.oec.sh/mcp. Nothing to install: your client sends your API key with every request in the Authorization header, the server forwards it to the API for that request only, and keeps nothing.
Claude Code:
claude mcp add --transport http oecsh https://mcp.oec.sh/mcp \
--header "Authorization: Bearer oec_live_ro_your_key"Cursor (mcp.json):
{
"mcpServers": {
"oecsh": {
"url": "https://mcp.oec.sh/mcp",
"headers": { "Authorization": "Bearer oec_live_ro_your_key" }
}
}
}To turn on opt-in tools in hosted mode, add the header X-OECSH-Allow: destructive (or backup-download, or both, comma separated).
Clients that only connect through OAuth, such as claude.ai web connectors, cannot use the hosted server yet.
The hosted server at mcp.oec.sh passes your address to the API (it is configured with OECSHMCPPROXY_SECRET, see below), so the API's block on repeated refused keys counts your address, not the server's shared one. Rate limits are per API key either way.
Tools
Every tool name starts with oecsh. List tools take limit (1 to 100, default 20) and cursor (the nextcursor of the previous page) and answer with items, count, total, hasmore and nextcursor.
Read tools (any key)
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
oec.sh: common questions
- Is oec.sh MCP server safe?
- Yes, by our scan: it is graded A (91/100). Read the oec.sh safety report
- How do I install oec.sh?
- It runs remotely at mcp.oec.sh. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does oec.sh need an API key?
- Yes. The registry entry asks for
OECSH_API_KEY,Authorization. - Is oec.sh maintained?
- The last commit was 27 days ago (2026-10-08). The latest release is v0.3.1.
- Is oec.sh up?
- 96% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of oec.sh?
- Servers from other publishers that do the same job: Touchdesigner MCP server.
- How does oec.sh compare with other MCP servers?
- safety score 91/100 (higher than 85% of 48,255 servers); uptime 96% (of our recent checks; the typical remote server answers 100%); response time 739 ms (faster than 18% of 30,031 servers). Full comparison.
Alternatives to oec.sh
Same job from other publishers: the closest match first, then the best rated.
- TouchdesignerMCP server for TouchDesigner - Control and operate TouchDesigner projects through AI agentsnot reviewedEstablishedA