Xerj vs Obsidian Turbocharged
A side-by-side look at the Xerj and Obsidian Turbocharged 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 Xerj for knowledge & memory work; choose Obsidian Turbocharged 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?
XChoose Xerj when
- You need dedicated capabilities in the Knowledge & Memory domain.
- Its auth model fits you: No auth required.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | X Xerj | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 53/100 · Good | 48/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | OBSIDIAN_TC_CONFIG |
| Verified owner | Community listing | Community listing |
| GitHub stars | 10,645 | 10 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Xerj | View Obsidian Turbocharged |
Tools & capabilities
Xerj tools
No tool names declared yet. Check the project README from the listing page.
Obsidian Turbocharged 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.
Xerj
No confirmed install command for Xerj yet — follow the setup steps linked from its listing page rather than a guessed package name.
Obsidian Turbocharged
{
"mcpServers": {
"obsidian-turbocharged": {
"command": "npx",
"args": [
"-y",
"obsidian-tc"
],
"env": {
"OBSIDIAN_TC_CONFIG": "YOUR_OBSIDIAN_TC_CONFIG_HERE"
}
}
}
}
Frequently asked questions
Xerj is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. Obsidian Turbocharged belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Xerj for knowledge & memory work and Obsidian Turbocharged 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.
Xerj is listed as free. Auth: no auth required. Obsidian Turbocharged 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 xerj and obsidian-turbocharged as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Xerj has a quality signal of 53/100 (Good) with 0 views, 0 installs and 10,645 GitHub stars. Obsidian Turbocharged has 48/100 (Fair) with 2 views, 0 installs and 10 GitHub stars.