Butlerbrain MCP vs Deja Vu

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

B
Butlerbrain MCPKnowledge & Memory
Persistent memory for AI assistants. Save once; recall from Claude, ChatGPT, or any MCP client.37FairAuth: not declared
Deja Vu logoDeja VuKnowledge & Memory · Local subprocess (stdio)Local memory layer over the session histories coding agents already write (Claude Code, Codex CLI, opencode): lexical search, recall tools, session-start auto-recall, secret redaction at index time, cross-machine sync over SSH.65GreatAuth: no auth required

Verdict: choose Butlerbrain MCP for knowledge & memory work; choose Deja Vu 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?

B
Choose Butlerbrain MCP when

  • You need dedicated capabilities in the Knowledge & Memory domain.
Explore Butlerbrain MCP

Deja Vu logoChoose Deja Vu when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You have the keys it needs: DEJA_TUI.
  • You want tools like deja.
Explore Deja Vu

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
B
Butlerbrain MCP
Deja Vu logoDeja Vu
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal37/100 · Fair65/100 · Great
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedDEJA_TUI
Verified ownerCommunity listingCommunity listing
GitHub stars—1,303
Directory activity 1 views 0 installs 0 upvotes 8 views 0 installs 0 upvotes
ToolsNot listed1

Tools & capabilities

Butlerbrain MCP tools

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

Deja Vu tools 1

  • dejaDepends on the mode, below.

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.

Butlerbrain MCP

No confirmed install command for Butlerbrain MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.

Deja Vu

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vshulcz-deja-vu": {
      "command": "npx",
      "args": [
        "-y",
        "@vshulcz/deja-vu"
      ],
      "env": {
        "DEJA_TUI": "YOUR_DEJA_TUI_HERE"
      }
    }
  }
}

Frequently asked questions

Butlerbrain MCP is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. Deja Vu belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Butlerbrain MCP for knowledge & memory work and Deja Vu 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. Butlerbrain MCP has no confirmed install command yet — follow its own setup instructions.

Butlerbrain MCP has no declared pricing — check the project's own site. Deja Vu is listed as free. Auth: no auth required. 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 mcp-4 and vshulcz-deja-vu as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Butlerbrain MCP has a quality signal of 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Deja Vu has 65/100 (Great) with 8 views, 0 installs and 1,303 GitHub stars.