Butterbase Oss vs Obsidian Notes

A side-by-side look at the Butterbase Oss and Obsidian Notes 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 Notes logoObsidian NotesKnowledge & MemorySearch an Obsidian vault by tag, term and wikilink graph. Read-only, deterministic, no embeddings.33EmergingAuth: not declared

Verdict: choose Butterbase Oss for knowledge & memory work as a local process; choose Obsidian Notes for knowledge & memory. 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 Notes logoChoose Obsidian Notes when

  • You need dedicated capabilities in the Knowledge & Memory domain.
Explore Obsidian Notes

Feature & specification comparison

Rows where the two servers differ are marked.

SpecButterbase Oss logoButterbase OssObsidian Notes logoObsidian Notes
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal51/100 · Good33/100 · Emerging
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars3,0310
Directory activity 2 views 0 installs 0 upvotes 0 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 Notes 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 Notes

No confirmed install command for Obsidian Notes yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Butterbase Oss is categorized under Knowledge & Memory and uses a local stdio subprocess. Obsidian Notes belongs to Knowledge & Memory and uses an install path we have not confirmed yet. Pick Butterbase Oss for knowledge & memory work and Obsidian Notes 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. Obsidian Notes has no confirmed install command yet — follow its own setup instructions.

Butterbase Oss has no declared pricing — check the project's own site. Obsidian Notes 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-notes 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,031 GitHub stars. Obsidian Notes has 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.