Dannet vs Listen Notes

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

Dannet logoDannetKnowledge & Memory · Local subprocess (stdio)DanNet - Danish WordNet with rich lexical relationships and SPARQL access.47FairAuth: not declaredListen Notes logoListen NotesKnowledge & Memory · Local subprocess (stdio)Podcast directory search + best podcasts + recommendations via Listen Notes. Free key required.43FairAuth: not declared

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

Dannet logoChoose Dannet when

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

Listen Notes logoChoose Listen Notes when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: PLATFORM_LISTENNOTES_KEY.
Explore Listen Notes

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDannet logoDannetListen Notes logoListen Notes
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal47/100 · Fair43/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedPLATFORM_LISTENNOTES_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars290
Directory activity 1 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Dannet tools

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

Listen Notes 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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "dannet": {
      "command": "npx",
      "args": [
        "-y",
        "shadow-cljs"
      ]
    }
  }
}

Listen Notes

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "listen-notes": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-listen-notes"
      ],
      "env": {
        "PLATFORM_LISTENNOTES_KEY": "YOUR_PLATFORM_LISTENNOTES_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Dannet is categorized under Knowledge & Memory and uses a local stdio subprocess. Listen Notes belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Dannet for knowledge & memory work and Listen Notes 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. Listen Notes 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 dannet and listen-notes 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. Listen Notes has 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.