Loredex MCP Server
Enables AI coding agents to search, read, and write notes in an Obsidian vault via MCP tools, and monitor product handoffs and state.
README
Loredex for Obsidian
Browse your loredex knowledge vault where it lives — and let your AI coding agents read and file into it while you do.
Loredex is an open-source CLI + Claude Code plugin that auto-files AI-agent-generated markdown (research, decisions, handoffs) into an Obsidian-compatible vault. This plugin is the Obsidian side of that loop:
- Live product dashboard — a workspace view showing every project's state: note counts, active topics, stale briefs, open cross-team handoffs, cross-project references. Computed fresh from the vault, never written to a file.
- Handoff badge — the status bar shows how many handoffs are open across the product. Click it to open the dashboard.
- Vault sync — one command pulls the shared vault repo (rebase + autostash), rebuilds the
_index/maps of content, commits, and pushes. Same conflict-free merge driver the CLI uses for generated files. - MCP server inside Obsidian — serves your vault to coding agents (Claude Code, Cursor, Codex CLI) over Streamable HTTP on localhost. All six loredex MCP tools (
vault_search,vault_note,handoffs_open,handoff_consume,product_state,vault_store) plus one only Obsidian can provide:active_note, the note you're looking at right now.
Network use disclosure
When the MCP server is enabled (default: on), the plugin listens on 127.0.0.1 only — it never binds a public interface and never makes outbound network requests. Every request must carry a bearer token generated on first load (Settings → Loredex). Turn the server off in settings and the plugin opens no sockets at all. Git sync runs git against whatever remote you configured for your vault repo; the plugin adds no remotes.
Install
Not yet in the community plugin directory. Two options:
BRAT (recommended): install BRAT, then Add beta plugin → ahmedtawfeeq1/loredex-obsidian.
Manual: grab main.js + manifest.json from the latest release, drop them in <vault>/.obsidian/plugins/loredex/, reload Obsidian, enable the plugin.
Desktop only (isDesktopOnly) — the plugin shells out to git and reads the vault through Node fs.
Setup
- Open your loredex vault (
~/Loredexby default) as an Obsidian vault, if you haven't already. - Enable the plugin. A bearer token is generated automatically.
- Run the command “Loredex: Copy MCP server config for coding agents” and paste the snippet into your project's
.mcp.json(or your agent's MCP config):
{
"mcpServers": {
"loredex": {
"type": "http",
"url": "http://127.0.0.1:28428/mcp",
"headers": { "Authorization": "Bearer <your-token>" }
}
}
}
Agents connected this way search and file into the vault while Obsidian is open — no separate process. (Without Obsidian running, agents can use the CLI's stdio server instead: npx -y loredex mcp. Same tools, minus active_note.)
Commands
| Command | What it does |
|---|---|
| Open product dashboard | Live view of all projects, briefs, handoffs, cross-project edges |
| Sync vault | git pull → rebuild indexes → commit → push |
| Copy MCP server config for coding agents | Clipboard-ready .mcp.json snippet with your port + token |
| Restart MCP server | Rebind after changing port/token |
Settings
| Setting | Default | |
|---|---|---|
| MCP server | on | Streamable HTTP on localhost |
| Port | 28428 | |
| Bearer token | generated | regenerate any time |
| Git sync | on | pull/commit/push during sync command |
| Handoff check interval | 5 min | status-bar badge refresh |
Security model
The vault is treated as untrusted input end to end — same rules as the loredex CLI. Note content returned to agents is framed as data, never instructions, control characters are stripped, and lengths are bounded. Note paths are resolved with realpath and must land inside the vault (symlink escapes rejected). The server is stateless: every request gets a fresh MCP server instance reading current vault state.
Development
npm install # needs loredex ≥ 0.10 on npm; before that: npm pkg set dependencies.loredex=file:../loredex
npm run typecheck
npm run build # bundles src/main.ts → main.js (CJS, obsidian external)
npm run smoke # boots the HTTP server against a temp vault, drives a real MCP session
npm run dev # esbuild watch mode
npm run smoke is the fast loop — it proves auth, initialize, tools/list, and a real vault_search without launching Obsidian.
Related
- loredex — the CLI, Claude Code plugin, vault spec, and all core logic (this plugin embeds it as a library)
License
MIT © Ahmed Tawfeeq — PM & Head of AI, Founder @ genudo.ai
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.