Obsidian MCP Agent
A custom MCP server that cleans up raw notes into properly formatted, cross-linked notes in an Obsidian vault using Claude Desktop.
README
Obsidian MCP Agent
A custom Python MCP (Model Context Protocol) server that turns rough, train-of-thought notes into properly formatted, cross-linked notes in an Obsidian vault — using Claude Desktop as the interface, with no coding required at use-time.
The Problem
I take a lot of notes during coursework and independent learning, usually typed quickly and messily during or right after a lecture. Cleaning those up into a properly formatted, well-organized note — consistent tagging, inline links to related topics, clear structure — is repetitive and easy to put off. The raw notes pile up in an "unsorted" backlog instead of becoming useful, searchable knowledge.
What This Does
Point Claude Desktop at this MCP server, say something like "clean up my Obsidian backlog," and it will:
- Read each raw note sitting in the vault's inbox folder.
- Rewrite it into a consistent template — abstract, sections, references — while preserving all the original substance.
- Tag it using only tags that already exist in the vault (never inventing new ones).
- Add inline
[[wikilinks]]to genuinely related existing notes, verified by actually reading the candidate note first — not just matching titles. - Save it to the correct folder and archive the original raw note.
- If a note with the same name already exists, it stops and asks — it never silently overwrites.
Before/after example: see example/before-raw-inbox-note.md and example/after-formatted-note.md.
Architecture
Built with FastMCP, running as a local stdio server that Claude Desktop launches as a subprocess — no API key, no cloud hosting, uses an existing Claude Pro subscription.
Tools exposed:
| Tool | Purpose |
|---|---|
read_folder_guide |
Static notes on the vault's folder structure |
read_processing_instructions |
The full note-cleanup workflow, read by Claude before processing |
list_vault_notes / list_vault_notes_in_folder |
Recursive scan of existing notes and their summaries |
read_note |
Full content of one existing note, for verifying wikilink relevance |
list_templates / read_template |
Reads the vault's note templates |
list_tags |
Live scan of valid tags — never hardcoded |
list_inbox / read_inbox_note |
Reads raw notes waiting to be processed |
write_note |
Creates a new note; refuses to overwrite, returns a conflict instead |
update_note |
Overwrites an existing note — only ever called after explicit user approval of a proposed merge |
archive_inbox_note |
Moves a processed raw note out of the inbox |
All file paths are validated against the vault root to prevent path traversal outside the vault.
Setup
-
Clone this repo.
-
Create a virtual environment and install dependencies:
python -m venv .venv .venv\Scripts\activate # Windows pip install -r requirements.txt
-
Set the
OBSIDIAN_VAULT_PATHenvironment variable to your vault's absolute path. -
Add this server to your
claude_desktop_config.json:
{
"mcpServers": {
"obsidian-mcp-agent": {
"command": "/path/to/.venv/Scripts/python.exe",
"args": ["/path/to/server.py"],
"env": {
"OBSIDIAN_VAULT_PATH": "/path/to/your/vault"
}
}
}
}
- Fully restart Claude Desktop.
- Adjust
folder-guide.mdandprocessing-instructions.mdto match your own vault's conventions — these are personal to how I organize notes and will need editing for a different vault structure.
What's Next
- A template-selection step for coursework that uses a different note format (currently only one template is supported).
- Automated validation of tag/wikilink formatting in generated output, rather than manual review.
- Possibly extending beyond a chat-driven workflow to something workflow-embedded — this was intentionally out of scope for this build.
Notes on This Project
Built as a weekend project to learn MCP server design (tools vs. resources, path safety, conflict handling) rather than to build the most sophisticated possible agent. The example/ folder uses entirely made-up content — no real personal notes are included in this repo.
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.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
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.