MCP Odoo vs WalkerOS Flow
A side-by-side look at the MCP Odoo and WalkerOS Flow MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Odoo for developer tools work as a local process; choose WalkerOS Flow 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?
Choose MCP Odoo when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ODOO_MCP_ENABLE_WRITES, ODOO_MCP_MAX_ATTACHMENT_BYTES, ODOO_MCP_ALLOW_UNKNOWN_METHODS, MCP_CHATTER_DIRECT, ODOO_MCP_KNOWLEDGE_MAX_DOCS, ODOO_MCP_ELICIT_WRITES, ODOO_MCP_AUDIT_LOG, ODOO_LOCALE. - You want tools like
data_quality_report, diagnose_odoo_call, generate_json2_payload.
Choose WalkerOS Flow when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 63/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | ODOO_MCP_ENABLE_WRITESODOO_MCP_MAX_ATTACHMENT_BYTESODOO_MCP_ALLOW_UNKNOWN_METHODSMCP_CHATTER_DIRECTODOO_MCP_KNOWLEDGE_MAX_DOCSODOO_MCP_ELICIT_WRITESODOO_MCP_AUDIT_LOGODOO_LOCALE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 425 | 347 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 41 | Not listed |
| Full listing | View MCP Odoo | View WalkerOS Flow |
Tools & capabilities
MCP Odoo tools 41
data_quality_reportRun read-only data-quality checks on one Odoo model: duplicates, missing required values, orphaned references, format anomaliesdiagnose_odoo_callDiagnose an Odoo model call without executing itgenerate_json2_payloadBuild a JSON-2 request preview without network accessinspect_model_relationshipsInspect model relationships and required field metadatadiagnose_accessDiagnose ACL and record-rule visibility for an Odoo modelupgrade_risk_reportReport Odoo upgrade and JSON-2 migration risksanalyze_upgrade_logClassify Odoo install/update log errors into a migration worklist (no_action / needs_review / needs_script) with fix suggestionslookup_model_historyLook up Odoo model rename/removal history by old or new model name (e.g. account.invoice -> account.move)fit_gap_reportClassify Odoo requirements into fit/gap implementation bucketsscan_addons_sourceScan local Odoo addon source without importing addon codebuild_domainBuild a validated Odoo domain from structured conditionsbusiness_pack_reportReport expected modules, models, and safe discovery calls for a business pack- +29 more on the listing page
WalkerOS Flow tools
No tool names declared yet. Check the project README from 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.
MCP Odoo
{
"mcpServers": {
"mcp-odoo": {
"command": "uvx",
"args": [
"odoo-mcp"
],
"env": {
"ODOO_MCP_ENABLE_WRITES": "YOUR_ODOO_MCP_ENABLE_WRITES_HERE",
"ODOO_MCP_MAX_ATTACHMENT_BYTES": "YOUR_ODOO_MCP_MAX_ATTACHMENT_BYTES_HERE",
"ODOO_MCP_ALLOW_UNKNOWN_METHODS": "YOUR_ODOO_MCP_ALLOW_UNKNOWN_METHODS_HERE",
"MCP_CHATTER_DIRECT": "YOUR_MCP_CHATTER_DIRECT_HERE",
"ODOO_MCP_KNOWLEDGE_MAX_DOCS": "YOUR_ODOO_MCP_KNOWLEDGE_MAX_DOCS_HERE",
"ODOO_MCP_ELICIT_WRITES": "YOUR_ODOO_MCP_ELICIT_WRITES_HERE",
"ODOO_MCP_AUDIT_LOG": "YOUR_ODOO_MCP_AUDIT_LOG_HERE",
"ODOO_LOCALE": "YOUR_ODOO_LOCALE_HERE"
}
}
}
}
WalkerOS Flow
{
"mcpServers": {
"walkeros-flow": {
"command": "npx",
"args": [
"-y",
"walkeros"
]
}
}
}
Frequently asked questions
MCP Odoo is categorized under Developer Tools and uses a local stdio subprocess. WalkerOS Flow belongs to Developer Tools and uses a local stdio subprocess. Pick MCP Odoo for developer tools work and WalkerOS Flow 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.
MCP Odoo has no declared pricing — check the project's own site. WalkerOS Flow has no declared pricing — check the project's own site. 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 mcp-odoo and walkeros-flow as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Odoo has a quality signal of 63/100 (Good) with 0 views, 0 installs and 425 GitHub stars. WalkerOS Flow has 49/100 (Fair) with 1 views, 0 installs and 347 GitHub stars.