Obsidian MCP Server can read, search, append, patch, and delete files in the configured vault., Patch and append operations can change existing notes, create new notes, and insert content relative to headings, block references, or frontmatter fields., Delete operations can remove files or directories from the vault., Keep vault backups and require human review before allowing broad edits, deletes, generated summaries, or note reorganizations.
Privacy notes
Obsidian vaults often contain private notes, meeting records, research, personal data, API keys, customer details, drafts, and internal decisions., Vault paths, note names, note contents, search terms, prompts, tool arguments, and generated notes may be visible to the MCP client and model provider., Treat the Obsidian API key as a secret and avoid exposing the Local REST API beyond the trusted host and port configuration.
Author
Markus Pfundstein
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-05
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
4 safety and 3 privacy notes across 4 risk areas. Review closely: credentials & tokens, third-party handling.
4 areas
SafetyLocal filesObsidian MCP Server can read, search, append, patch, and delete files in the configured vault.
SafetyGeneralPatch and append operations can change existing notes, create new notes, and insert content relative to headings, block references, or frontmatter fields.
SafetyLocal filesDelete operations can remove files or directories from the vault.
SafetyGeneralKeep vault backups and require human review before allowing broad edits, deletes, generated summaries, or note reorganizations.
PrivacyCredentials & tokensObsidian vaults often contain private notes, meeting records, research, personal data, API keys, customer details, drafts, and internal decisions.
PrivacyThird-party handlingVault paths, note names, note contents, search terms, prompts, tool arguments, and generated notes may be visible to the MCP client and model provider.
PrivacyCredentials & tokensTreat the Obsidian API key as a secret and avoid exposing the Local REST API beyond the trusted host and port configuration.
Safety notes
Obsidian MCP Server can read, search, append, patch, and delete files in the configured vault.
Patch and append operations can change existing notes, create new notes, and insert content relative to headings, block references, or frontmatter fields.
Delete operations can remove files or directories from the vault.
Keep vault backups and require human review before allowing broad edits, deletes, generated summaries, or note reorganizations.
Privacy notes
Obsidian vaults often contain private notes, meeting records, research, personal data, API keys, customer details, drafts, and internal decisions.
Vault paths, note names, note contents, search terms, prompts, tool arguments, and generated notes may be visible to the MCP client and model provider.
Treat the Obsidian API key as a secret and avoid exposing the Local REST API beyond the trusted host and port configuration.
Prerequisites
Python 3.11 or newer available to the MCP client runtime.
uvx available for package execution.
Obsidian installed with a vault you want Claude to access.
Obsidian Local REST API community plugin enabled with an API key.
Host and port values configured for the local Obsidian REST API service.
Obsidian MCP Server connects MCP clients to an Obsidian vault through the
Obsidian Local REST API community plugin. It exposes tools for listing files,
listing directories, reading note contents, searching across vault files,
patching existing notes, appending content, and deleting files or directories.
The upstream README documents published server configuration with uvx, and
the PyPI package exposes the mcp-obsidian command for MCP clients.
These sources were reviewed on 2026-06-05. Prefer the live repository and
PyPI metadata for current package version, command name, Python requirement,
dependencies, supported tools, and setup guidance.
Features
List files and directories in an Obsidian vault.
Read the contents of individual notes.
Search vault files for matching text.
Append content to new or existing notes.
Patch existing note content relative to headings, block references, or
frontmatter fields.
Delete files or directories from the vault.
Installation
Enable the Obsidian Local REST API community plugin, copy its API key, then add
the MCP server to a client that launches stdio servers:
Ask Claude to summarize recent meeting notes from an Obsidian vault.
Search a vault for mentions of a project, customer, decision, or incident.
Append a generated summary to a daily note or project note.
Patch an existing note under a specific heading or frontmatter field.
Build a lightweight knowledge-base workflow around Markdown notes.
Review vault structure before reorganizing notes manually.
Safety and Privacy
Obsidian vault automation can touch important personal and organizational notes.
Back up the vault, keep destructive operations gated by human review, and avoid
broad patch, append, or delete requests unless the target files are clear.
Vaults can contain sensitive personal notes, internal plans, meeting summaries,
credentials, customer information, drafts, and private research. Treat the
Obsidian API key as a secret, keep the Local REST API bound to trusted access,
and review generated notes before syncing or sharing them.
Duplicate Check
No MarkusPfundstein/mcp-obsidian entry, mcp-obsidian package entry, or
matching source URL was found in content/mcp.
Show that Obsidian MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/obsidian-mcp-server)
How it compares
Obsidian MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
Apache-licensed TypeScript MCP server for Obsidian vaults with stdio and Streamable HTTP transports, Local REST API access, note search, section-aware edits, tag/frontmatter management, path policies, and read-only controls.
Local-first Basic Memory MCP server for giving Claude a persistent Markdown knowledge base with note editing, semantic search, recent activity, knowledge graph context, projects, schema tools, and optional cloud sync.
Official Brave Search MCP server for giving Claude web, local, place, image, video, news, LLM context, and summarizer search tools backed by the Brave Search API.
✓Obsidian MCP Server can read, search, append, patch, and delete files in the configured vault.
Patch and append operations can change existing notes, create new notes, and insert content relative to headings, block references, or frontmatter fields.
Delete operations can remove files or directories from the vault.
Keep vault backups and require human review before allowing broad edits, deletes, generated summaries, or note reorganizations.
✓Cyanheads Obsidian MCP can read, list, search, create, append, patch, replace, delete, tag, and edit frontmatter in the configured vault through the Local REST API plugin.
The server defaults to full-vault access unless read paths, write paths, or read-only mode are configured.
Set `OBSIDIAN_READ_ONLY=true` for research-only workflows, then narrow writes with `OBSIDIAN_WRITE_PATHS` before allowing note edits.
Delete operations are permanent in the vault and should require human review even when the MCP host supports destructive-tool prompts.
Command-palette tools are disabled unless `OBSIDIAN_ENABLE_COMMANDS=true`; command execution can trigger opaque or destructive Obsidian plugin behavior.
Streamable HTTP deployments should use JWT or OAuth auth before being exposed beyond a trusted local machine.
✓Basic Memory MCP can create, edit, move, and delete notes in the configured project.
The server exposes content, search, knowledge graph, project, schema, cloud, and release-note tools.
Edit and delete tools should be reviewed carefully because the model can change the human-readable Markdown source of truth.
Imports can ingest Claude, ChatGPT, or memory JSON exports and may bring old sensitive conversations into the knowledge base.
Auto-update behavior can update uv tool and Homebrew installs, while uvx runs use the ephemeral runtime managed by uv.
The optional cloud service changes the trust boundary by syncing notes through hosted storage and account authentication.
✓Brave Search MCP uses BRAVE_API_KEY from the MCP client environment or command-line options.
The server defaults to stdio transport in version 2.x and can also run an HTTP transport when explicitly configured.
Tools can send web, news, image, video, local, place, and LLM-context queries to the Brave Search API.
Local and place tools may use location strings, coordinates, postal codes, or optional location headers.
Summarizer workflows depend on summary keys returned by web search and should be checked against cited source URLs.
API usage may be metered or plan-limited, especially for Pro-only local search capabilities and extra snippets.
Privacy notes
✓Obsidian vaults often contain private notes, meeting records, research, personal data, API keys, customer details, drafts, and internal decisions.
Vault paths, note names, note contents, search terms, prompts, tool arguments, and generated notes may be visible to the MCP client and model provider.
Treat the Obsidian API key as a secret and avoid exposing the Local REST API beyond the trusted host and port configuration.
✓Vault notes, headings, block references, frontmatter, tags, file metadata, outgoing links, search queries, command names, plugin status, and edit history may be exposed to the MCP client and model provider.
API keys, local plugin endpoints, HTTP auth settings, path allowlists, logs, OpenTelemetry traces, and Docker environment variables can reveal private vault structure or credentials.
Tag listing is vault-wide in upstream behavior and can reveal tag names outside narrowed read paths.
Notes may contain personal journals, client work, credentials, meeting notes, research plans, health data, or other sensitive knowledge-base content.
✓Local notes, frontmatter, wikilinks, observations, relations, embeddings, logs, and project metadata can contain personal data, credentials, customer details, unreleased plans, or private research.
Cloud routing and hosted team workspaces may sync Markdown, metadata, snapshots, and backups outside the local machine.
The README says telemetry records non-content usage events and does not collect file contents, note titles, knowledge base data, PII, IP addresses, or per-tool tracking.
Logs are written to Basic Memory's local log file by default for MCP usage; review log level and retention before using sensitive prompts or notes.
Keep API keys, cloud credentials, imported chat archives, and private project paths out of prompts, screenshots, issues, and committed files.
✓Search queries, location parameters, result filters, language settings, freshness windows, and optional headers may reveal user intent, location, research topics, or sensitive business context.
BRAVE_API_KEY should stay out of prompts, issues, logs, screenshots, and committed files.
Returned snippets, summaries, search results, local-business metadata, images, videos, and news items can include third-party copyrighted or sensitive content.
HTTP transport should be bound and exposed carefully so the API key and search tools are not reachable by untrusted clients.
Prerequisites
Python 3.11 or newer available to the MCP client runtime.
uvx available for package execution.
Obsidian installed with a vault you want Claude to access.
Obsidian Local REST API community plugin enabled with an API key.
Node.js 24 or newer, or Bun 1.3.11 or newer.
Obsidian vault with the Obsidian Local REST API community plugin enabled.
Local REST API key stored in the MCP client environment.
Stdio MCP client, or reviewed Streamable HTTP deployment with authentication.
Python 3.12 or newer available through uv for the local MCP server.
A selected Basic Memory project directory for Markdown notes and generated metadata.
Backups or version control for important notes before enabling model-assisted writes.
Team agreement on whether notes stay local, sync through the optional cloud service, or route per project.
Brave Search API account and API key.
Node.js and npm available in the MCP client runtime.
API plan review for web, local, extra snippets, summarizer, and LLM context usage.
Tool whitelist or blacklist if the client should expose only selected search tools.
Install
uvx mcp-obsidian
npx -y obsidian-mcp-server@latest
claude mcp add basic-memory -- uvx basic-memory mcp