Desktop Commander vs Menlo Customer Insurance MCP
Both are utilities MCP servers, and we ran both through the same test (list products, write read back) in each app. Desktop Commander passed 2 of 4 apps we tested it in; Menlo Customer Insurance MCP passed 0 of 1.
Test results side by side
| Desktop Commander | Menlo Customer Insurance MCP | |
|---|---|---|
| Claude Code | Partial 2026-10-15 | Failed 2026-11-05 |
| Cursor | Partial 2026-10-15 | Not tested yet |
| Claude Desktop | Passed 2026-10-19 | Not tested yet |
| ChatGPT (Codex) | Passed 2026-10-20 | Not tested yet |
| Tools exposed (protocol check) | 25 tools | 12 tools |
| GitHub stars | 10,320 | 0 (shared repo) |
| License | MIT | — |
| Last push | 2026-11-12 | ? |
Results from our own harness runs, dated per cell. Stars and last push from GitHub at our last data refresh. We don’t pick a winner here: which one fits depends on your app and setup.
What each does
Desktop Commander: Terminal and file-system access for an agent: run commands, search files and make diff-based edits.
Menlo Customer Insurance MCP: Remote Streamable HTTP MCP for Menlo Insurance Services: list publishable insurance products and quote-form links for free, and — only after a customer authorizes a quote on Menlo's website — help fill application answers and attach documents in ChatGPT or Claude. Menlo supplies no AI model; nothing is purchased or bound through the MCP alone.