Obsidian MCP (pgvector + Ollama, self-hosted)
Related Servers
Alternatives to Obsidian MCP (pgvector + Ollama, self-hosted)
- AlicenseAqualityAmaintenanceStandalone MCP server for Obsidian vaults - hybrid search (FTS5 + vector + cross-encoder reranking), images and PDFs in agent-readable form, Kanban-aware tasks (Tasks-plugin + Dataview formats), structured memory with topic recall, fine-grained read/write tools for optimal token efficiency, and link graph support. Run locally, self-host, or one-click deploy for remote access. OAuth 2.1.433116 npm34MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceSelf-hosted MCP server for private Obsidian vaults on GitHub, exposing tools to search, read, write, and analyze Markdown notes and their link graph.MIT
- AlicenseNot gradedqualityDmaintenanceSelf-hosted MCP server that provides embedding-powered semantic search with graph context over Obsidian vaults, supporting multiple vaults, local embeddings, and a web dashboard.23 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceMCP server exposing fast full-text and semantic search over an Obsidian vault, plus safe structured note read and write access for Claude.2Apache 2.0
- AlicenseNot gradedqualityAmaintenanceSelf-hosted server for your Obsidian vaults: a web UI for you, MCP for your AI agents, no Obsidian or plugins required. Agents search notes by keyword or meaning, then read, edit, move and link them across several vaults, and a write is refused if the note changed since the agent read it.72AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceLocal-first MCP server for retrieval over markdown wikilink vaults, offering hybrid vector+lexical search, note reading, neighbor expansion, and recent activity tracking with fully local embeddings and no network egress.MIT
- AlicenseBqualityCmaintenanceHeadless semantic MCP server for Obsidian, Logseq, Dendron, Foam, and any markdown folder. Features built-in hybrid semantic search, surgical AST editing, template scaffolding, zero-config local embeddings, and workflow tracking.557 npm12MIT
TDQS
Scored across 28 tools
The set has many neighboring tools (keyword/semantic/hybrid search, find_related vs get_neighborhood, note vs file operations), but descriptions explicitly distinguish their purposes and route uncertain cases. A few pairs still require careful reading, especially list_notes vs get_recent and the several search modes, so it is not perfectly unambiguous.
All tool names are consistently snake_case and almost all follow a clear verb_noun pattern: get_tags, read_note, create_note, edit_note, delete_note, move_note, write_file, list_files, import_from_url, and so on. The few non-standard forms like get_recent and find_orphans still fit the same readable convention.
At 28 tools this is a heavy surface for a single MCP server, exceeding the range where each tool easily stays top-of-mind for an agent. The domain is broad enough that most tools have distinct jobs, but the count still pushes into over-large territory.
The surface covers the core vault lifecycle well: note and file CRUD, search, links, backlinks, tags, tasks, change feeds, and transfer/import workflows. Minor gaps remain around folder management and moving non-markdown files, but agents can work around them with existing write and list tools.