Butterbase Oss vs MCP Obsidian Via Rest

In-depth architectural comparison of the Butterbase Oss and MCP Obsidian Via Rest MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Butterbase Oss when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Butterbase Oss Details

Choose MCP Obsidian Via Rest when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore MCP Obsidian Via Rest Details

Feature & Specification Comparison

Specification	Butterbase Oss butterbase-ai Knowledge & Memory	MCP Obsidian Via Rest Knowledge & Memory
Summary	Butterbase MCP server — manage your backend: schemas, auth, functions, storage, RAG, deploys.	MCP Server for Obsidian Vault Access via Local REST API
Category & Scope	Knowledge & Memory	Knowledge & Memory

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "mcp-285": {
      "command": "npx",
      "args": [
        "-y",
        "@butterbase/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "mcp-obsidian-via-rest": {
      "command": "bunx",
      "args": [
        "-y",
        "@oleksandrkucherenko/mcp-obsidian"
      ]
    }
  }
}

Related MCP Server Comparisons