Butterbase Oss vs Obsidian Turbocharged

A side-by-side look at the Butterbase Oss and Obsidian Turbocharged MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Butterbase Oss logoButterbase OssKnowledge & Memory · Local subprocess (stdio)Butterbase MCP server — manage your backend: schemas, auth, functions, storage, RAG, deploys.51GoodAuth: not declaredObsidian Turbocharged logoObsidian TurbochargedKnowledge & Memory · Local subprocess (stdio)Model-agnostic, agent-ready Obsidian MCP server with RBAC, SLSA provenance, and native search.49FairAuth: not declared

Verdict: choose Butterbase Oss 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?

Butterbase Oss logoChoose Butterbase Oss when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
Explore Butterbase Oss

Obsidian Turbocharged logoChoose 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.
Explore Obsidian Turbocharged

Feature & specification comparison

Rows where the two servers differ are marked.

SpecButterbase Oss logoButterbase OssObsidian Turbocharged logoObsidian Turbocharged
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal51/100 · Good49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedOBSIDIAN_TC_CONFIG
Verified ownerCommunity listingCommunity listing
GitHub stars3,03010
Directory activity 2 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Butterbase Oss 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.

Butterbase Oss

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-285": {
      "command": "npx",
      "args": [
        "-y",
        "@butterbase/mcp"
      ]
    }
  }
}

Obsidian Turbocharged

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "obsidian-turbocharged": {
      "command": "npx",
      "args": [
        "-y",
        "obsidian-tc"
      ],
      "env": {
        "OBSIDIAN_TC_CONFIG": "YOUR_OBSIDIAN_TC_CONFIG_HERE"
      }
    }
  }
}

Frequently asked questions

Butterbase Oss is categorized under Knowledge & Memory and uses a local stdio subprocess. Obsidian Turbocharged belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Butterbase Oss 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.

Butterbase Oss 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 mcp-285 and obsidian-turbocharged as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Butterbase Oss has a quality signal of 51/100 (Good) with 2 views, 0 installs and 3,030 GitHub stars. Obsidian Turbocharged has 49/100 (Fair) with 6 views, 0 installs and 10 GitHub stars.