Dannet vs Vocci

A side-by-side look at the Dannet and Vocci 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 declared
V
VocciKnowledge & Memory · Remote HTTP/SSE
Read-only MCP access to authorized Vocci sessions, notes, files, and memory search.42FairAuth: not declared

Verdict: choose Dannet for knowledge & memory work as a local process; choose Vocci for knowledge & memory over a hosted endpoint. 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

V
Choose Vocci when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a remote HTTP/SSE transport.
Explore Vocci

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDannet logoDannet
V
Vocci
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal47/100 · Fair42/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars29—
Directory activity 1 views 0 installs 0 upvotes 2 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.

Vocci 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"
      ]
    }
  }
}

Vocci

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vocci": {
      "url": "https://docs.vocci.ai/developers/mcp"
    }
  }
}

Frequently asked questions

Dannet is categorized under Knowledge & Memory and uses a local stdio subprocess. Vocci belongs to Knowledge & Memory and uses a remote HTTP/SSE transport. Pick Dannet for knowledge & memory work and Vocci 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. Vocci 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 vocci 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. Vocci has 42/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.