explaingit

junnnnnw00/obsidian-everywhere

Analysis updated 2026-05-18

2TypeScriptAudience · developerComplexity · 3/5LicenseSetup · easy

TLDR

A TypeScript MCP server that lets AI assistants like Codex, ChatGPT, and Claude read and safely edit an Obsidian notes vault as a linked graph rather than plain files.

Mindmap

mindmap
  root((repo))
    What it does
      Graph view of vault
      MCP tool server
      Safe note editing
    Tech stack
      TypeScript
      SQLite
      MCP
      graphology
    Use cases
      AI search notes
      Find backlinks
      Bulk edit with rollback
    Audience
      Obsidian users
      AI power users

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Let an AI assistant search and read Obsidian notes with full context of tags, links, and backlinks.

USE CASE 2

Find orphaned notes or broken links across a large vault automatically.

USE CASE 3

Have an AI create, move, rename, or edit notes safely, with rollback for bulk changes.

USE CASE 4

Connect Obsidian to Codex, ChatGPT Desktop, or Claude without opening the Obsidian app.

What is it built with?

TypeScriptSQLiteMCPgraphologyNode.js

How does it compare?

junnnnnw00/obsidian-everywhereadun-denton/chinvatagbara286/saint-cms
Stars222
LanguageTypeScriptTypeScriptTypeScript
Setup difficultyeasymoderateeasy
Complexity3/54/52/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Runs via npx with no install, connecting a real vault just needs its local folder path.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

In plain English

obsidian-everywhere is a TypeScript server that lets AI tools like Codex, ChatGPT, and Claude read and edit an Obsidian notes vault through the Model Context Protocol, or MCP. Instead of treating the vault as a plain folder of markdown files, the server represents notes and the links between them as a graph, so an AI client can ask for things like backlinks, neighboring notes within a certain number of hops, or a bundle of related context around a topic, rather than only reading raw file text. Under the hood it parses the markdown files, including wikilinks, embedded content, frontmatter, nested tags, headings, and block references, and keeps two things in sync as the vault changes: a SQLite index with full text search, and an in-memory graph structure that supports multi-hop traversal, shortest path lookups, and PageRank style ranking of important notes. The README states this index updates incrementally rather than being rebuilt from scratch each time. On top of this, the project exposes 31 separate tools an AI client can call, split between reading tools such as searching notes, listing backlinks, finding orphaned or unresolved notes, and writing tools such as creating, moving, renaming, or deleting notes, updating frontmatter, and running bulk find and replace operations with a rollback option. The server can connect to clients in three ways: through standard input and output for local tools like the Codex CLI, over HTTP with a fixed bearer token for private remote use, or over HTTP with OAuth 2.1 for public connectors. Write tools that can change the vault are turned on by default for local and bearer token connections, but turned off by default for the public OAuth connection unless specifically enabled. The README includes a demo command that builds a temporary sample vault to show off the graph features without touching a real one, plus setup commands that print ready to paste configuration for Codex, ChatGPT Desktop, and Claude, and a doctor command that checks the environment for problems. The project is released under the MIT license.

Copy-paste prompts

Prompt 1
Help me run the obsidian-everywhere demo to see the graph features before connecting my real vault.
Prompt 2
Walk me through the init and doctor commands to connect my Obsidian vault to Claude.
Prompt 3
Explain the difference between the stdio, bearer token, and OAuth connection modes.
Prompt 4
Help me understand which write tools are enabled by default for my setup.

Frequently asked questions

What is obsidian-everywhere?

A TypeScript MCP server that lets AI assistants like Codex, ChatGPT, and Claude read and safely edit an Obsidian notes vault as a linked graph rather than plain files.

What language is obsidian-everywhere written in?

Mainly TypeScript. The stack also includes TypeScript, SQLite, MCP.

What license does obsidian-everywhere use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is obsidian-everywhere to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is obsidian-everywhere for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.