Vocci vs Deja Vu

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

V
VocciKnowledge & Memory · Remote HTTP/SSE
Read-only MCP access to authorized Vocci sessions, notes, files, and memory search.43FairAuth: oauth 2.0
Deja Vu logoDeja VuKnowledge & MemoryLocal 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.59GoodAuth: no auth required

Verdict: choose Vocci for knowledge & memory work over a hosted endpoint; choose Deja Vu for knowledge & memory. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

V
Choose Vocci 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 Vocci

Deja Vu logoChoose Deja Vu when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • Its auth model fits you: No auth required.
  • You want tools like deja.
Explore Deja Vu

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
V
Vocci
Deja Vu logoDeja Vu
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal43/100 · Fair59/100 · Good
Install commandConfirmedNot confirmed yet
TransportRemote HTTP/SSE—
AuthOAuth 2.0No auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—1,300
Directory activity 2 views 0 installs 0 upvotes 8 views 0 installs 0 upvotes
ToolsNot listed1

Tools & capabilities

Vocci 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.

Vocci

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

Deja Vu

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

Frequently asked questions

Vocci is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. Deja Vu belongs to Knowledge & Memory and uses an install path we have not confirmed yet. Pick Vocci 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. Deja Vu has no confirmed install command yet — follow its own setup instructions.

Vocci has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 vocci and vshulcz-deja-vu as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Vocci has a quality signal of 43/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Deja Vu has 59/100 (Good) with 8 views, 0 installs and 1,300 GitHub stars.