Dannet vs Graphify
A side-by-side look at the Dannet and Graphify 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 Graphify 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 Dannet when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
Choose Graphify when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
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 | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 29 | 3 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Dannet | View Graphify |
Tools & capabilities
Dannet tools
No tool names declared yet. Check the project README from the listing page.
Graphify 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"
]
}
}
}
Graphify
{
"mcpServers": {
"graphify": {
"command": "npx",
"args": [
"-y",
"not"
]
}
}
}
Frequently asked questions
Dannet is categorized under Knowledge & Memory and uses a local stdio subprocess. Graphify belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Dannet for knowledge & memory work and Graphify 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.
Dannet has no declared pricing — check the project's own site. Graphify has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 dannet and graphify as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dannet has a quality signal of 47/100 (Fair) with 1 views, 0 installs and 29 GitHub stars. Graphify has 48/100 (Fair) with 1 views, 0 installs and 3 GitHub stars.