Koskamo

oec.sh MCP

The oec.sh MCP server enables AI assistants to manage Odoo hosting infrastructure on the oec.sh platform. It allows users to view servers, projects, and environments, monitor live metrics and logs, deploy code, restart services, create backups, and manage webhooks. It supports both local installation and a hosted endpoint, using the user's own API key for authentication and authorization.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

oec.sh MCP logo, by oec.shVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-10-26Operated by oec.sh
You need:Requires Starter plan or higherCreate a key under Settings → API Keys
MCP endpoint (Streamable HTTP)
https://mcp.oec.sh/mcp
Vendor documentation

What you can do with it

  • Monitor live CPU, memory, and disk metrics for Odoo environments
  • Deploy code updates and restart Odoo environments
  • View and manage project environments and server status
  • Create backups and check deployment history

Source and maintenance

Vendor evidenceRegistry 0.3.1MIT
mcp-registry: sh.oec/mcp-server@0.3.1Source repositoryProject website
Last repository push
Maintenance checked

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · repository · passed · metadata changed · unchanged
  • · repository · passed · metadata changed · updated
  • · registry · passed · metadata changed · Source metadata updated
  • · backfill · recorded · Pre-expansion baseline; unobserved rich metadata remains unknown

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http oec-sh-mcp https://mcp.oec.sh/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add oec-sh-mcp --url https://mcp.oec.sh/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable oec-sh-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "oec-sh-mcp": {
      "url": "https://mcp.oec.sh/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "oec-sh-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.oec.sh/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start oec-sh-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "oec-sh-mcp": {
      "type": "http",
      "url": "https://mcp.oec.sh/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http oec-sh-mcp https://mcp.oec.sh/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "oec-sh-mcp": {
      "url": "https://mcp.oec.sh/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "oec-sh-mcp": {
      "serverUrl": "https://mcp.oec.sh/mcp"
    }
  }
}

Let your agent find its tools

Find servers like oec.sh MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 298

Do you run oec.sh MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing