AiAkiv Memory vs Weasley DeepMind

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

AiAkiv Memory logoAiAkiv MemoryKnowledge & Memory · Remote HTTP/SSEShared long-term memory for AI agents: save and recall context as a searchable knowledge graph.56GoodAuth: oauth 2.0Weasley DeepMind logoWeasley DeepMindKnowledge & Memory · Local subprocess (stdio)Secure, fragment-based long-term memory for MCP-compatible AI agents.43FairAuth: not declared

Verdict: choose AiAkiv Memory for knowledge & memory work over a hosted endpoint; choose Weasley DeepMind 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?

AiAkiv Memory logoChoose AiAkiv Memory when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore AiAkiv Memory

Weasley DeepMind logoChoose Weasley DeepMind when

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAiAkiv Memory logoAiAkiv MemoryWeasley DeepMind logoWeasley DeepMind
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal56/100 · Good43/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthOAuth 2.0Not declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars04
Directory activity 1 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

AiAkiv Memory tools

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

Weasley DeepMind 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.

AiAkiv Memory

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "aiakiv-memory": {
      "url": "https://mcp.aiakiv.com/mcp"
    }
  }
}

Weasley DeepMind

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "weasley-deepmind": {
      "command": "npx",
      "args": [
        "-y",
        "weasley-deepmind"
      ]
    }
  }
}

Frequently asked questions

AiAkiv Memory is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. Weasley DeepMind belongs to Knowledge & Memory and uses a local stdio subprocess. Pick AiAkiv Memory for knowledge & memory work and Weasley DeepMind 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.

AiAkiv Memory has no declared pricing — check the project's own site. Auth: oauth 2.0. Weasley DeepMind 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 aiakiv-memory and weasley-deepmind as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, AiAkiv Memory has a quality signal of 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Weasley DeepMind has 43/100 (Fair) with 2 views, 0 installs and 4 GitHub stars.