Chatpack MCP vs Oec.sh
A side-by-side look at the Chatpack MCP and Oec.sh MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
Chatpack MCPDeveloper Tools · Local subprocess (stdio)Read-only MCP server for Chatpack documentation, framework setup guides, and React UI block source. Runs locally over stdio with npx -y @chatpack/mcp. Node.js 20 or later; MIT license; no account or API key required.86ExcellentAuth: no auth requiredO
Oec.shDeveloper Tools · Local subprocess (stdio)Operate your oec.sh Odoo servers, projects and environments with your own API key.53GoodAuth: api key requiredVerdict: choose Chatpack MCP for developer tools work as a local process; choose Oec.sh for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
CChoose Chatpack MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
search_docs, get_document, get_integration_guide.
OChoose Oec.sh when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
OECSH_API_KEY, OECSH_ALLOW, OECSH_API_URL. - You want tools like
oecsh_get_organization, oecsh_get_server_metrics, oecsh_list_environments.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Chatpack MCP | O Oec.sh |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 86/100 · Excellent | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | BYOK (pay the provider) |
| Required env vars | None listed | OECSH_API_KEYOECSH_ALLOWOECSH_API_URL |
| Verified owner | Verified | Community listing |
| GitHub stars | 224 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | 14 |
| Full listing | View Chatpack MCP | View Oec.sh |
Tools & capabilities
Chatpack MCP tools 5
search_docsSearch bundled Chatpack documentation and the authoritative llms reference. Returns document ids, links and matching excerpts with package versions.get_documentRead a complete bundled Chatpack document by id. Use llms for the authoritative integration contract or concepts/errors for troubleshooting.get_integration_guideRetrieve the repository's framework setup guide with authentication guidance and the authoritative llms reference. Examples match the bundled package versions.list_ui_blocksList public runtime exports of @chatpack/ui, including components, providers and utilities. Returns names accepted by get_ui_block.get_ui_blockRetrieve a public @chatpack/ui export's source module and usage guide. Optionally include supporting UI modules and stylesheet. Files are reference source, not a standalone copy-and-paste component.
Oec.sh tools 14
oecsh_get_organizationPlan, limits and current usageoecsh_get_server_metricsLive CPU, memory, disk and network of one of your own servers (not shared servers)oecsh_list_environmentsA project's environments, optionally by statusoecsh_get_environmentOne environment with its health and last deployoecsh_get_runtime_logsThe newest lines (up to 1000) of an environment's Odoo or PostgreSQL log, read live from its serveroecsh_get_environment_metricsLive CPU and memory of an environment's containers, and its disk sizesoecsh_list_deploymentsAn environment's deploy historyoecsh_get_taskAny task's status and progressoecsh_wait_for_taskWaits until a task finishesoecsh_get_task_logA task's step log and erroroecsh_list_changelogoec.sh release notes, newest first; optionally only those after a version (`since_version`) or since a date (`since_date`)oecsh_deploy_environmentPulls the branch and redeploys; can update modules- +2 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Chatpack MCP
{
"mcpServers": {
"chatpack-mcp": {
"command": "npx",
"args": [
"-y",
"@chatpack/mcp"
]
}
}
}
Oec.sh
{
"mcpServers": {
"oec-sh": {
"command": "npx",
"args": [
"-y",
"@oecsh/mcp-server"
],
"env": {
"OECSH_API_KEY": "YOUR_OECSH_API_KEY_HERE",
"OECSH_ALLOW": "YOUR_OECSH_ALLOW_HERE",
"OECSH_API_URL": "YOUR_OECSH_API_URL_HERE"
}
}
}
}
Frequently asked questions
Chatpack MCP is categorized under Developer Tools and uses a local stdio subprocess. Oec.sh belongs to Developer Tools and uses a local stdio subprocess. Pick Chatpack MCP for developer tools work and Oec.sh for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Chatpack MCP is listed as free. Auth: no auth required. Oec.sh is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add chatpack-mcp and oec-sh as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Chatpack MCP has a quality signal of 86/100 (Excellent) with 2 views, 0 installs and 224 GitHub stars. Oec.sh has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.