Dannet vs LensHub
A side-by-side look at the Dannet and LensHub MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Dannet for knowledge & memory work as a local process; choose LensHub for knowledge & memory. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Dannet when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
LChoose LensHub when
- You need dedicated capabilities in the Knowledge & Memory domain.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L LensHub | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 47/100 · Fair | 38/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 29 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Dannet | View LensHub |
Tools & capabilities
Dannet tools
No tool names declared yet. Check the project README from the listing page.
LensHub 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.
Dannet
{
"mcpServers": {
"dannet": {
"command": "npx",
"args": [
"-y",
"shadow-cljs"
]
}
}
}
LensHub
No confirmed install command for LensHub yet — follow the setup steps linked from its listing page rather than a guessed package name.