Leteo vs Honcho
A side-by-side look at the Leteo and Honcho MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Leteo for knowledge & memory work as a local process; choose Honcho for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Leteo when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Honcho when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HONCHO_API_KEY, HONCHO_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 47/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | HONCHO_API_KEYHONCHO_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 7,734 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Leteo | View Honcho |
Tools & capabilities
Leteo tools
No tool names declared yet. Check the project README from the listing page.
Honcho 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.
Leteo
{
"mcpServers": {
"leteo": {
"command": "bunx",
"args": [
"@asanabrial/leteo"
]
}
}
}
Honcho
{
"mcpServers": {
"honcho": {
"command": "uvx",
"args": [
"honcho-ai"
],
"env": {
"HONCHO_API_KEY": "YOUR_HONCHO_API_KEY_HERE",
"HONCHO_URL": "YOUR_HONCHO_URL_HERE"
}
}
}
}
Frequently asked questions
Leteo is categorized under Knowledge & Memory and uses a local stdio subprocess. Honcho belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Leteo for knowledge & memory work and Honcho for knowledge & memory.
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.
Leteo is listed as free. Auth: no auth required. Honcho 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 leteo and honcho as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Leteo has a quality signal of 47/100 (Fair) with 3 views, 0 installs and 3 GitHub stars. Honcho has 48/100 (Fair) with 1 views, 0 installs and 7,734 GitHub stars.