Llmwiki vs Obsidian Turbocharged
A side-by-side look at the Llmwiki and Obsidian Turbocharged MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
LlmwikiKnowledge & MemoryOpen Source Implementation of Karpathy's LLM Wiki. Upload documents, connect your Claude account via MCP, and have it write your wiki !49FairAuth: not declaredVerdict: choose Llmwiki 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?
LChoose Llmwiki when
- You need dedicated capabilities in the Knowledge & Memory domain.
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 | L Llmwiki | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 49/100 · Fair | 49/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | None listed | OBSIDIAN_TC_CONFIG |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,709 | 10 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Llmwiki | View Obsidian Turbocharged |
Tools & capabilities
Llmwiki 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.
Llmwiki
No confirmed install command for Llmwiki 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
Llmwiki 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 Llmwiki 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. Llmwiki has no confirmed install command yet — follow its own setup instructions.
Llmwiki is bring-your-own-key: usage is billed by the API provider you supply a key for. 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 llmwiki-2 and obsidian-turbocharged as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Llmwiki has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 1,709 GitHub stars. Obsidian Turbocharged has 49/100 (Fair) with 5 views, 0 installs and 10 GitHub stars.