Honcho vs Obsidian Turbocharged
A side-by-side look at the Honcho and Obsidian Turbocharged MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Honcho for knowledge & memory work as a local process; 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?
Choose Honcho when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
HONCHO_API_KEY, HONCHO_URL.
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 | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 48/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | HONCHO_API_KEYHONCHO_URL | OBSIDIAN_TC_CONFIG |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7,746 | 10 |
| Directory activity | 1 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Honcho | View Obsidian Turbocharged |
Tools & capabilities
Honcho 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.
Honcho
{
"mcpServers": {
"honcho": {
"command": "uvx",
"args": [
"honcho-ai"
],
"env": {
"HONCHO_API_KEY": "YOUR_HONCHO_API_KEY_HERE",
"HONCHO_URL": "YOUR_HONCHO_URL_HERE"
}
}
}
}
Obsidian Turbocharged
{
"mcpServers": {
"obsidian-turbocharged": {
"command": "npx",
"args": [
"-y",
"obsidian-tc"
],
"env": {
"OBSIDIAN_TC_CONFIG": "YOUR_OBSIDIAN_TC_CONFIG_HERE"
}
}
}
}
Frequently asked questions
Honcho is categorized under Knowledge & Memory and uses a local stdio subprocess. Obsidian Turbocharged belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Honcho 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.
Honcho has no declared pricing — check the project's own site. 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 honcho and obsidian-turbocharged as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Honcho has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 7,746 GitHub stars. Obsidian Turbocharged has 49/100 (Fair) with 6 views, 0 installs and 10 GitHub stars.