obsidian-mcp-guard
Provides read/write file tools with lint validation to prevent agents from writing malformed Obsidian markdown, and constrains writes to a single configurable vault for security.
README
obsidian-mcp-guard
An MCP server for agent-safe Obsidian vault access. Provides read/write file tools with lint validation to prevent agents from writing malformed Obsidian markdown.
Why this exists
Most Obsidian MCP servers give agents direct write access with no markdown validation. Those that route through the Obsidian REST API gain some input sanitisation, but none validate content against Obsidian's markdown rendering rules before writing. obsidian-mcp-guard fills this gap: all writes are validated against Obsidian's markdown rules before they touch the vault, and if the content would render incorrectly, the write is rejected with a structured error explaining exactly which rule was violated. Writes can also be constrained to a single configurable vault path, giving agents a designated space to create and manage content on behalf of the user while preventing accidental or runaway writes to other vaults on the same filesystem. Directory traversal attacks are blocked at the path resolution layer, so a misconfigured, misbehaving, or prompt-injected agent cannot escape the write vault by constructing paths like Claude/../OtherVault/note.md
Features
- Read/list/create/update/delete/move notes via
HOST_VAULT_PATHon the host filesystem - Lint validation on all writes using mdlint-obsidian — blocks writes that violate Obsidian markdown rules (unclosed wikilinks, raw HTML, standard-markdown links, etc.)
- Write-vault isolation — writes are constrained to a single configurable vault; directory-traversal attacks are blocked on both read and write paths
- Composable —
create_vault_server()returns aFastMCPinstance that can be mounted into a larger server viaimport_server() - Pre-validation tool —
lint_notelets agents check content before committing a write
Installation
pip install obsidian-mcp-guard
For Claude Desktop users who don't want a manual install, uvx runs it directly with no setup:
uvx obsidian-mcp-guard
For local development:
python -m venv .venv
source .venv/bin/activate
pip install -e .
Configuration
| Environment variable | Default | Description |
|---|---|---|
HOST_VAULT_PATH |
(required) | Absolute path to the directory containing your vaults as subdirectories |
WRITE_VAULT |
Claude |
Name of the only vault where write operations are permitted |
Example layout expected under HOST_VAULT_PATH:
/path/to/your/vaults/
Claude/ ← write operations land here
Work/ ← readable but not writable
Personal/ ← readable but not writable
Usage
As a standalone stdio server
# via the installed CLI entry point
HOST_VAULT_PATH=/path/to/your/vaults obsidian-mcp-guard
# or via python -m
HOST_VAULT_PATH=/path/to/your/vaults python -m obsidian_mcp_guard
Claude Desktop / Cursor config
{
"mcpServers": {
"obsidian": {
"command": "uvx",
"args": ["obsidian-mcp-guard"],
"env": {
"HOST_VAULT_PATH": "/path/to/your/vaults",
"WRITE_VAULT": "Claude"
}
}
}
}
Claude Code
claude mcp add obsidian -- uvx obsidian-mcp-guard
Pass environment variables with -e:
claude mcp add obsidian -e HOST_VAULT_PATH=/path/to/your/vaults -e WRITE_VAULT=Claude -- uvx obsidian-mcp-guard
Mounted into another FastMCP server
from contextlib import asynccontextmanager
from fastmcp import FastMCP
from obsidian_mcp_guard import create_vault_server
@asynccontextmanager
async def lifespan(app):
await app.import_server(create_vault_server(
vault_path="/path/to/your/vaults",
write_vault="Claude"
))
yield
mcp = FastMCP("my-agent", lifespan=lifespan)
@mcp.tool()
def search_notes(...):
...
Tools
| Tool | Description |
|---|---|
read_note(source) |
Return full content of a note in vault/path.md format |
list_notes(vault, folder?, recursive?) |
List note paths within a vault or subfolder |
create_note(source, content, overwrite?) |
Create a note; blocked by lint errors |
update_note(source, content, mode?) |
Overwrite or append to a note; blocked by lint errors |
delete_note(source) |
Move a note to .trash/ (recoverable) |
move_note(source_path, dest_path, create_dirs?) |
Move a note within the write vault; rewrites wikilinks in all vault files |
lint_note(content) |
Pre-validate content without writing; returns {valid, errors, warnings} |
Development
make install # install package + test dependencies
make test # run tests with coverage (90% minimum)
make build # build source and wheel distributions
make clean # remove build artefacts and cache files
See CONTRIBUTING.md for full guidelines.
Related projects
- mdlint-obsidian — the lint engine used to validate markdown against Obsidian's rendering rules
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。