Filesystem vs MCP Obsidian

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

Filesystem logoFilesystemFile SystemsSecure MCP server for sandboxed filesystem operations with document parsing support.41FairAuth: not declaredMCP Obsidian logoMCP ObsidianKnowledge & Memory · Local subprocess (stdio)Universal AI bridge for Obsidian vaults using MCP. Provides safe read/write access to notes with 11 comprehensive methods for vault operations including search, batch operations, tag management, and frontmatter handling. Works with Claude, ChatGPT, and any MCP-compatible AI assistant.73GreatAuth: no auth required

Verdict: choose Filesystem for file systems work; choose MCP Obsidian 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?

Filesystem logoChoose Filesystem when

  • You need dedicated capabilities in the File Systems domain.
  • You want tools like read_file, read_multiple_files, read_file_lines.
Explore Filesystem

MCP Obsidian logoChoose MCP Obsidian when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like read_note, write_note, patch_note.
Explore MCP Obsidian

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFilesystem logoFilesystemMCP Obsidian logoMCP Obsidian
CategoryFile SystemsKnowledge & Memory
Quality signal41/100 · Fair73/100 · Great
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars11,699
Directory activity 3 views 0 installs 0 upvotes 11 views 0 installs 0 upvotes
Tools1718

Tools & capabilities

Filesystem tools 17

  • read_fileRead file contents (text as UTF-8, binary as base64)
  • read_multiple_filesRead multiple files at once with per-file error handling
  • read_file_linesRead a specific range of lines
  • convert_to_markdownConvert one supported document file into a markdown file on disk
  • convert_directory_to_markdownBatch-convert supported document files in a directory to markdown files
  • write_fileCreate or overwrite a file with atomic write
  • append_fileAppend content to end of file with auto-newline
  • modify_fileFind and replace text (plain text or regex)
  • copy_fileCopy a file or directory recursively
  • move_fileMove or rename a file or directory
  • delete_fileDelete a file or directory
  • list_directoryList contents with type markers, sizes, and dates
  • +5 more on the listing page

MCP Obsidian tools 18

  • read_noteRead a note from the Obsidian vault
  • write_noteWrite a note to the Obsidian vault
  • patch_noteEfficiently update part of a note by replacing a specific string. This is more efficient than rewriting the entire note for small changes.
  • list_directoryList files and directories in the vault (includes non-note filenames, while read/write tools remain note-only)
  • delete_noteDelete a note from the Obsidian vault (requires confirmation). Supports permanent delete, vault trash, or system trash.
  • search_notesSearch for notes in the vault by content or frontmatter
  • move_noteMove or rename a note in the vault
  • move_fileMove or rename any file in the vault (binary-safe, file-only, requires confirmation)
  • read_multiple_notesRead multiple notes in a batch (max 10 files)
  • update_frontmatterUpdate frontmatter of a note without changing content
  • get_notes_infoGet metadata for notes without reading full content
  • get_frontmatterExtract frontmatter from a note without reading the content
  • +6 more on 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.

Filesystem

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

MCP Obsidian

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "bitbonsai-mcp-obsidian": {
      "command": "npx",
      "args": [
        "-y",
        "@bitbonsai/mcpvault@latest"
      ]
    }
  }
}

Frequently asked questions

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

Filesystem has no declared pricing — check the project's own site. MCP Obsidian is listed as free. Auth: no auth required. 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 filesystem-3 and bitbonsai-mcp-obsidian as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Filesystem has a quality signal of 41/100 (Fair) with 3 views, 0 installs and 1 GitHub stars. MCP Obsidian has 73/100 (Great) with 11 views, 0 installs and 1,699 GitHub stars.