Obsidian Turbocharged vs Xerj
A side-by-side look at the Obsidian Turbocharged and Xerj MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
X
XerjKnowledge & MemoryLocal-first search engine and MCP server for AI agents. One Rust binary indexes code, docs, logs, JSONL/CSV and PDFs for BM25 full-text, vector and hybrid search, code search without grep, agent memory and RAG. Elasticsearch-compatible API; Corpus Hub serves hundreds of reference memory corpora.53GoodAuth: no auth requiredVerdict: choose Obsidian Turbocharged for knowledge & memory work as a local process; choose Xerj for knowledge & memory. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Obsidian Turbocharged when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OBSIDIAN_TC_CONFIG.
XChoose Xerj when
- You need dedicated capabilities in the Knowledge & Memory domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | X Xerj | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 48/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | OBSIDIAN_TC_CONFIG | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 10 | 10,645 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Obsidian Turbocharged | View Xerj |
Tools & capabilities
Obsidian Turbocharged tools
No tool names declared yet. Check the project README from the listing page.
Xerj 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.
Obsidian Turbocharged
{
"mcpServers": {
"obsidian-turbocharged": {
"command": "npx",
"args": [
"-y",
"obsidian-tc"
],
"env": {
"OBSIDIAN_TC_CONFIG": "YOUR_OBSIDIAN_TC_CONFIG_HERE"
}
}
}
}
Xerj
No confirmed install command for Xerj yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Obsidian Turbocharged is categorized under Knowledge & Memory and uses a local stdio subprocess. Xerj belongs to Knowledge & Memory and uses an install path we have not confirmed yet. Pick Obsidian Turbocharged for knowledge & memory work and Xerj 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. Xerj has no confirmed install command yet — follow its own setup instructions.
Obsidian Turbocharged has no declared pricing — check the project's own site. Xerj 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 obsidian-turbocharged and xerj as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Obsidian Turbocharged has a quality signal of 48/100 (Fair) with 2 views, 0 installs and 10 GitHub stars. Xerj has 53/100 (Good) with 0 views, 0 installs and 10,645 GitHub stars.