In-depth architectural comparison of the Tela and Deja Vu MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Tela
Knowledge & Memory · Local stdio
Quality: 60/100 (Good) | Auth: API Key required
Deja Vu
Knowledge & Memory · Local stdio
Quality: 68/100 (Great) | Auth: No auth required
Verdict Summary: Choose Tela if you need specialized Knowledge & Memory tools running via a local process. Choose Deja Vu if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Tela when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: TELA_PUBLIC_BASE_URL, TELA_SHARE_SECRET, TELA_API_KEY_SECRET, TELA_PG_PASSWORD.
Primary tools included: MCP access to search, read, and write wiki pages, Ranked PostgreSQL full-text search, Optional pgvector semantic retrieval.
Tela is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Deja Vu belongs to Knowledge & Memory using local stdio subprocess. Select Tela when you need capabilities focused on knowledge & memory and Deja Vu when you require tools for knowledge & memory.
Self-hostable, markdown-native team wiki with a built-in MCP server: agents search, read, and write your wiki pages (ranked Postgres full-text + semantic search, backlink traversal). Plus Atlas, which auto-generates a cited, coverage-checked wiki from your git repos and Jira. Go + Postgres. npx tela-mcp
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.