Atlas Mind vs Dannet

A side-by-side look at the Atlas Mind and Dannet MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Atlas Mind logoAtlas MindKnowledge & Memory · Local subprocess (stdio)Self-hosted git-native knowledge base with an MCP endpoint your AI reads, writes and rewinds37FairAuth: not declaredDannet logoDannetKnowledge & Memory · Local subprocess (stdio)DanNet - Danish WordNet with rich lexical relationships and SPARQL access.47FairAuth: not declared

Verdict: choose Atlas Mind for knowledge & memory work as a local process; 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?

Atlas Mind logoChoose Atlas Mind when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
Explore Atlas Mind

Dannet logoChoose Dannet when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
Explore Dannet

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAtlas Mind logoAtlas MindDannet logoDannet
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal37/100 · Fair47/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars329
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Atlas Mind tools

No tool names declared yet. Check the project README from the listing page.

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.

Atlas Mind

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "atlas-mind": {
      "command": "uvx",
      "args": [
        "atlas-mind"
      ]
    }
  }
}

Dannet

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "dannet": {
      "command": "npx",
      "args": [
        "-y",
        "shadow-cljs"
      ]
    }
  }
}

Frequently asked questions

Atlas Mind is categorized under Knowledge & Memory and uses a local stdio subprocess. Dannet belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Atlas Mind 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.

Atlas Mind 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 atlas-mind and dannet as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Atlas Mind has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 3 GitHub stars. Dannet has 47/100 (Fair) with 1 views, 0 installs and 29 GitHub stars.