Atlas / MCP servers / drewburchfield / Obsidian Graph

Obsidian GraphSAFE

Name: Obsidian Graph
Author: drewburchfield

mcp/drewburchfield/obsidian-graph-1

MCP server by drewburchfield · mcp · mcp server · obsidian · Audited 2026-10-10

Semantic knowledge graph navigation for Obsidian or markdown vaults using AI-powered vector embeddings and PostgreSQL+pgvector

Verdict

SAFE

Grade

Trust score

89 /100

Exposed tools

4 4r · 0w · 0d

Transport

stdio

License

MIT

Stars

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

[](https://github.com/drewburchfield/obsidian-graph)

[](https://github.com/drewburchfield/obsidian-graph/actions/workflows/ci.yml) [](https://www.python.org/downloads/) [](https://opensource.org/licenses/MIT) [](https://modelcontextprotocol.io/) [](https://deepwiki.com/drewburchfield/obsidian-graph)

Semantic knowledge graph engine for markdown vaults. Discovers hidden connections between notes using AI-powered vector embeddings and PostgreSQL+pgvector. Accessible to any AI app or harness compatible with MCP.

Overview

Obsidian Graph builds a semantic knowledge graph of your markdown vault, discovering relationships between notes that go beyond keywords and explicit links. It embeds your notes as vectors using Voyage Context-4, stores them in PostgreSQL+pgvector, and provides tools for semantic search, multi-hop graph traversal, hub detection, and orphan analysis.

Designed for Obsidian vaults but works with any folder of markdown files. Connects to any AI app or harness compatible with the Model Context Protocol (MCP).

Features

Semantic Search: Find notes by meaning, not just keywords
Connection Discovery: Multi-hop BFS graph traversal to map note relationships
Hub Analysis: Identify highly connected conceptual anchors (MOC candidates)
Orphan Detection: Find isolated insights that need integration
Auto-Indexing: Automatic file wa

Read from source at commit 26e154a3530eOBSERVED · 2026-10-10

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.

claude-code

claude mcp add obsidian-graph --env POSTGRES_PASSWORD=${POSTGRES_PASSWORD} --env VOYAGE_API_KEY=${VOYAGE_API_KEY} -- uvx obsidian-graph

claude-desktop

{
  "mcpServers": {
    "obsidian-graph": {
      "command": "uvx",
      "args": [
        "obsidian-graph"
      ],
      "env": {
        "POSTGRES_PASSWORD": "${POSTGRES_PASSWORD}",
        "VOYAGE_API_KEY": "${VOYAGE_API_KEY}"
      }
    }
  }
}

Exposed tools (4)

4 read · 0 write · 0 destructive.

Tool	Risk	Description
`get_hub_notes`	read	Identify highly connected notes (conceptual hubs/anchors)
`get_orphaned_notes`	read	Find isolated notes with few connections
`get_similar_notes`	read	Find notes semantically similar to a given note
`search_notes`	read	Semantic search across Obsidian vault using natural language queries

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

Layer	What it checks	Result
L0	Provenance & inventory	PASS
L1	Static analysis of the code	PASS
L2	Instruction surface (what it tells the agent)	PASS
L3	Class-specific surface	PASS
L4	Behavioural (sandbox)	SKIPPED

What the source does

Filesystem: declared (3 observation(s))
Network: declared (2 observation(s))
Shell: none-observed
Dependencies: pinned
Secrets in source: none-found

Findings (6)

LOWFilesystem / path · fs.credential_store · CWE-22, CWE-59

tests/test_security_path_traversal.py:42

"/home/user/.ssh/id_rsa",

Why it matters. touches a credential store