obsidian-mcp-connector
Your Obsidian vault, exposed to Claude, Codex, Cursor and any MCP client. Runs inside Obsidian, on-device semantic search, no cloud round-trip, no binary to download
What XERJ indexed
Snapshot
The whole repository at commit 209b4f07ee (2026-10-07). main is 126 commits ahead.
Selected work
“add Codex menu, installer and project install”. 19 files, 4,658 lines in packages/obsidian-plugin.
Licence
The repository
LICENSE file checked at the pinned commit; the author agreed to inclusion.
The XERJ corpus
The author agreed by email on 2026-10-29. Same terms as the repository. Answers name the repo, the commit and the file:line.
selected for the XERJ Corpus Hublicence clearedsuggested use: adapt with attribution
claudemcpmodel-context-protocolobsidian-pluginai-toolslocal-firstsemantic-searchtypescript
Example questions
- How does obsidian-mcp-connector implement claude?
- Where does obsidian-mcp-connector handle “add Codex menu, installer and project install”?
- What does packages/obsidian-plugin do in obsidian-mcp-connector?
Inside the indexed corpus
- Languages by size: TypeScript 93.5%, Svelte 4.2%, JavaScript 1.1%, Python 0.8%, Shell 0.4%.
- On GitHub since 2026-04-11, last push 2026-10-29, 1,429 commits on main.
- The pin is 126 commits behind main; the corpus answers from the pinned code, not the newest.
Licence on GitHub and in the corpus
GitHub reported MIT for istefox/obsidian-mcp-connector on 2026-10-29, and the LICENSE file at commit 209b4f07ee was reviewed as MIT. They match, so answers from this corpus carry the same terms as the live repository.
Contributors
istefox (@istefox) has 1 selected repository on the hub.
Using XERJ with obsidian-mcp-connector
- Code search MCP for Claude Code: cite file:line, not grep obsidian-mcp-connector is tagged mcp on GitHub.
- What is an MCP memory server?
- A local search tool for Codex and Cursor obsidian-mcp-connector is tagged claude-code on GitHub.
- Local code search MCP that uses fewer tokens than grep
The prompt
Paste it into your AI agent. It clones istefox/obsidian-mcp-connector at the pinned commit and indexes it on your machine.
Search the GitHub repository istefox/obsidian-mcp-connector with XERJ (https://hub.xerj.org/corpus/istefox--obsidian-mcp-connector). Run these in a shell, in order, and check each result before the next: 1. xerj --help (success: it prints usage). If xerj is missing: curl -fsSL https://xerj.org/get | sh 2. git clone https://github.com/istefox/obsidian-mcp-connector obsidian-mcp-connector && git -C obsidian-mcp-connector checkout 209b4f07ee6d572bc110278af0480bb4647848d1 3. Start a local node and leave it running: xerj --insecure --data-dir ./xerj-data 4. xerj autoindex ./obsidian-mcp-connector --url http://127.0.0.1:9200 --prefix obsidian-mcp-connector --progress plain 5. xerj autoindex map --url http://127.0.0.1:9200 Then answer my question from the indexed files and cite the ax_path of every hit. Query syntax: https://xerj.org/llms.txt Licence: MIT. Keep the copyright notice and credit the authors.
Related
istefoxAI, prompts and agents corporaxerj-blogpostsfaahdunorth595--ai-agent-chatrodaddy/mcp2clikanghyunsoon/duoham7a311/Vitrine
Stats: GitHub API, fetched 2026-10-29. Selected work and consent: the XERJ registry.