Agentmemorymcp MCP vs Dannet
A side-by-side look at the Agentmemorymcp MCP and Dannet MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agentmemorymcp MCP for knowledge & memory work over a hosted endpoint; choose Dannet 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 Agentmemorymcp MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
memory_smart_search, memory_save_observation, memory_session_summary.
Choose Dannet when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 48/100 · Fair | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | 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 | 0 | 29 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Agentmemorymcp MCP | View Dannet |
Tools & capabilities
Agentmemorymcp MCP tools 4
memory_smart_searchmemory_save_observationmemory_session_summarymemory_graph_query
Dannet 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.
Agentmemorymcp MCP
{
"mcpServers": {
"agentmemorymcp-mcp": {
"url": "https://agentmemorymcp.clauxel.com/mcp"
}
}
}
Dannet
{
"mcpServers": {
"dannet": {
"command": "npx",
"args": [
"-y",
"shadow-cljs"
]
}
}
}
Frequently asked questions
Agentmemorymcp MCP is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. Dannet belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Agentmemorymcp MCP for knowledge & memory work and Dannet 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.
Agentmemorymcp MCP has no declared pricing — check the project's own site. Dannet 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 agentmemorymcp-mcp and dannet as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agentmemorymcp MCP has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Dannet has 47/100 (Fair) with 1 views, 0 installs and 29 GitHub stars.