In-depth architectural comparison of the Konbu and Adeu MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Konbu
Workplace & Productivity · Local stdio
Quality: 40/100 (Fair) | Auth: No auth required
Adeu
Workplace & Productivity · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Konbu if you need specialized Workplace & Productivity tools running via a local process. Choose Adeu if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Konbu when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Freemium).
You have access to required keys: DATABASE_URL, SESSION_SECRET.
Primary tools included: Cross-resource full-text search, Built-in MCP server and CLI client, Markdown memos with tags.
Self-hostable all-in-one planner (calendar, notes, todos, bookmarks) with built-in MCP server for AI assistant integration. Single Go binary, MIT.
docx ↔ LLM translator. Projects .docx office files to Markdown for editing. Projects edits back to OOXML as tracked changes (redlines). Python and Node.js implementations.
Konbu is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Adeu belongs to Workplace & Productivity using local stdio subprocess. Select Konbu when you need capabilities focused on workplace & productivity and Adeu when you require tools for workplace & productivity.