MCP工具 是 AI Skill Hub 本期精选MCP工具之一。综合评分 7.5 分,整体质量较高。我们推荐使用将其纳入你的 AI 工具库,帮助提升工作效率。
MCP工具 是一款遵循 MCP(Model Context Protocol)标准协议的 AI 工具扩展。通过 MCP 协议,它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务,实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用,都可以通过自然语言在 AI 对话中直接触发,极大提升生产效率。
MCP工具 是一款遵循 MCP(Model Context Protocol)标准协议的 AI 工具扩展。通过 MCP 协议,它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务,实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用,都可以通过自然语言在 AI 对话中直接触发,极大提升生产效率。
# 方式一:通过 Claude Code CLI 一键安装
claude skill install https://github.com/pvliesdonk/markdown-vault-mcp
# 方式二:手动配置 claude_desktop_config.json
{
"mcpServers": {
"mcp--": {
"command": "npx",
"args": ["-y", "markdown-vault-mcp"]
}
}
}
# 配置文件位置
# macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
# Windows: %APPDATA%/Claude/claude_desktop_config.json
# 安装后在 Claude 对话中直接使用 # 示例: 用户: 请帮我用 MCP工具 执行以下任务... Claude: [自动调用 MCP工具 MCP 工具处理请求] # 查看可用工具列表 # 在 Claude 中输入:"列出所有可用的 MCP 工具"
// claude_desktop_config.json 配置示例
{
"mcpServers": {
"mcp__": {
"command": "npx",
"args": ["-y", "markdown-vault-mcp"],
"env": {
// "API_KEY": "your-api-key-here"
}
}
}
}
// 保存后重启 Claude Desktop 生效
A generic markdown collection MCP server with FTS5 full-text search, semantic vector search, frontmatter-aware indexing, incremental reindexing, and non-markdown attachment support.
Documentation | PyPI | Docker
Point it at a directory of Markdown files (an Obsidian vault, a docs folder, a Zettelkasten, a PARA vault) and it exposes search, read, write, and edit tools over the Model Context Protocol.
read(path, section=heading)Upgrading. As of this release,searchreturns query-relevant snippets in thecontentfield by default (approximately 200 words). Passsnippet_words=0to recover the prior full-chunk behaviour, or useread(path, section=heading)to fetch a specific chunk after seeing a snippet. Documents are also re-chunked on nextreindexto honour the adaptiveMARKDOWN_VAULT_MCP_MAX_CHUNK_WORDSthreshold (default 400). - Frontmatter-aware — indexes YAML frontmatter fields, supports required field enforcement - Incremental reindexing — hash-based change detection, only re-processes modified files - Write operations — create, edit, delete, rename documents with automatic index updates - Attachment support — read, write, delete, and list non-markdown files (PDFs, images, etc.) - Git integration — optional auto-commit and push on every write viaGIT_ASKPASS- OIDC authentication — optional token-based auth for HTTP deployments (Authelia, Keycloak, etc.) - MCP tools — 30 LLM-visible tools including search, read, write, edit, delete, rename, git history, manual git sync, file-exchange uploads, and admin operations; plus 6 app-only tools for MCP Apps clients - MCP resources — 9 resources exposing vault configuration, statistics, tags, folders, document outlines, similar notes, recent notes, and an interactive SPA - MCP prompts — 6 prompt templates including template-driven note creation
docker pull ghcr.io/pvliesdonk/markdown-vault-mcp:latest
The Docker image uses [all] (MCP + FastEmbed + API embeddings). By default, semantic search works locally with FastEmbed and can switch to Ollama/OpenAI when configured. A compose.yml ships at the repo root as a starting point — copy .env.example to .env, edit, and docker compose up -d.
To attach a remote Python debugger (development only — the protocol is unauthenticated), see Remote debugging.
cp examples/obsidian-readonly.env .env
.env to set MARKDOWN_VAULT_MCP_SOURCE_DIR to the absolute path of your vault on the host. docker compose up -d
docker compose logs -f markdown-vault-mcp
| File | Description |
|---|---|
examples/obsidian-readonly.env | Obsidian vault, read-only, Ollama embeddings |
examples/obsidian-readwrite.env | Obsidian vault, read-write with git auto-commit |
examples/obsidian-oidc.env | Obsidian vault, read-only, OIDC authentication (Authelia) |
examples/ifcraftcorpus.env | Strict frontmatter enforcement, read-only corpus |
For reverse proxy (Traefik) and deployment setup, see docs/deployment.md.
All configuration is via environment variables with the MARKDOWN_VAULT_MCP_ prefix (except embedding provider settings, which use their own conventions).
markdown-vault-mcp <command> [options]
Download .deb or .rpm packages from the GitHub Releases page. Both install a hardened systemd unit; env configuration is sourced from /etc/markdown-vault-mcp/env (copy from the shipped /etc/markdown-vault-mcp/env.example). See the systemd deployment guide for details.
/plugin marketplace add pvliesdonk/claude-plugins
/plugin install markdown-vault-mcp@pvliesdonk
Installs the MCP server and the vault-workflow skill. See the Claude Code plugin guide for details.
Git integration has three modes:
- Managed mode (MARKDOWN_VAULT_MCP_GIT_REPO_URL set): server owns repo setup. On startup it clones into SOURCE_DIR when empty, or validates existing origin. Pull loop + auto-commit + deferred push are enabled. - Unmanaged / commit-only mode (no GIT_REPO_URL): writes are committed to a local git repo if SOURCE_DIR is already a git checkout. No pull, no push. - No-git mode: if SOURCE_DIR is not a git repo, git callbacks are no-ops.
When token auth is used (MARKDOWN_VAULT_MCP_GIT_TOKEN), remotes must be HTTPS. SSH remotes (for example git@github.com:owner/repo.git) are rejected with a startup error. Fix with: git -C /path/to/vault remote set-url origin https://github.com/owner/repo.git
Backward compatibility: MARKDOWN_VAULT_MCP_GIT_TOKEN without GIT_REPO_URL still works (legacy mode) but logs a deprecation warning.
| Variable | Default | Description |
|---|---|---|
MARKDOWN_VAULT_MCP_GIT_REPO_URL | — | HTTPS remote URL for managed mode; enables clone/remote validation on startup |
MARKDOWN_VAULT_MCP_GIT_USERNAME | x-access-token | Username for HTTPS auth prompts (x-access-token for GitHub, oauth2 for GitLab, account name for Bitbucket) |
MARKDOWN_VAULT_MCP_GIT_TOKEN | — | Token/password for HTTPS auth (GIT_ASKPASS) |
MARKDOWN_VAULT_MCP_GIT_PULL_INTERVAL_S | 600 | Seconds between git fetch + ff-only update attempts; 0 disables periodic pull |
MARKDOWN_VAULT_MCP_GIT_PUSH_DELAY_S | 30 | Seconds of write-idle time before pushing; 0 = push only on shutdown |
MARKDOWN_VAULT_MCP_GIT_COMMIT_NAME | markdown-vault-mcp | Git committer name for auto-commits; **set this in Docker** where git config user.name is empty |
MARKDOWN_VAULT_MCP_GIT_COMMIT_EMAIL | noreply@markdown-vault-mcp | Git committer email for auto-commits |
MARKDOWN_VAULT_MCP_GIT_LFS | true | Enable Git LFS — runs git lfs pull on startup to fetch LFS-tracked attachments (PDFs, images). Set to false for repos without LFS. |
pdf, docx, xlsx, pptx, odt, ods, odp, png, jpg, jpeg, gif, webp, svg, bmp, tiff, zip, tar, gz, mp3, mp4, wav, ogg, txt, csv, tsv, json, yaml, toml, xml, html, css, js, ts
Override with MARKDOWN_VAULT_MCP_ATTACHMENT_EXTENSIONS. Use * to allow all non-.md files.
Hidden directories: Attachments inside hidden directories (.git/,.obsidian/,.markdown_vault_mcp/, etc.) are never listed, regardless of extension settings.MARKDOWN_VAULT_MCP_EXCLUDEpatterns are also applied to attachments.
markdown-vault-mcp 是一个专为 Markdown 知识库设计的 MCP (Model Context Protocol) 服务端实现。它能够将您的本地 Markdown 笔记库(如 Obsidian 库)转化为 AI 可检索的知识源,通过标准化的接口为 Claude 等 AI 助手提供强大的上下文感知能力,实现知识库与大模型的深度集成。
本项目提供强大的混合搜索能力:支持基于 SQLite FTS5 的全文检索(Full-text search),并结合 BM25 评分与 Porter Stemming 算法;同时支持基于向量嵌入(Embedding)的语义搜索(Semantic search),兼容 FastEmbed、Ollama 及 OpenAI。通过 Reciprocal Rank Fusion (RRF) 技术实现混合搜索,并具备多样性感知排序(Diversity-aware ranking)功能,确保搜索结果的质量与分布合理。
推荐使用 Docker 进行部署。您可以直接从 GitHub Container Registry 拉取最新的 Docker 镜像。项目根目录提供了 `compose.yml` 作为启动模板,您只需将 `.env.example` 复制为 `.env` 并根据需求编辑配置,随后运行 `docker compose up -d` 即可快速启动服务。此外,对于 Linux 用户,我们也提供了 `.deb` 和 `.rpm` 安装包。
项目提供了多种预设的 `.env` 配置文件以适配不同场景。例如,使用 `examples/obsidian-readonly.env` 可实现对 Obsidian 库的只读访问并配合 Ollama 进行本地嵌入;若需读写权限并支持 Git 自动提交,请使用 `examples/obsidian-readwrite.env`。通过配置不同的环境变量,您可以灵活定义知识库路径、权限模式及身份验证方式(如 OIDC)。
所有的系统配置均通过环境变量进行管理,并统一使用 `MARKDOWN_VAULT_MCP_` 作为前缀。需要注意的��,关于 Embedding Provider(嵌入提供商)的具体设置,请遵循其各自的命名规范。通过修改 `.env` 文件,您可以精确控制知识库的源目录、读写权限以及搜索行为。
本项目通过 CLI(命令行界面)提供交互能力。用户可以通过执行 `markdown-vault-mcp <command> [options]` 命令来调用相关功能。对于开发者而言,其核心逻辑封装在 MCP 协议标准接口中,确保了与支持 MCP 协议的 AI 客户端(如 Claude)的无缝对接。
除了标准的 MCP 服务,本项目还深度集成了 Claude Code 插件。您可以通过 `plugin marketplace add pvliesdonk/claude-plugins` 命令安装,并直接通过 `plugin install markdown-vault-mcp@pvliesdonk` 来部署 MCP 服务端及配套的 `vault-workflow` 技能,实现自动化、智能化的知识库工作流。
如果在部署或使用过程中遇到问题,可以参考官方提供的故障排除指南。常见问题通常涉及 Docker 挂载路径设置、环境变量配置错误或 Embedding 模型连接失败等。建议在启动后通过 `docker compose logs -f` 实时查看日志以定位问题。
高质量的MCP工具,支持全文搜索和语义搜索
AI Skill Hub 为第三方内容聚合平台,本页面信息基于公开数据整理,不对工具功能和质量作任何法律背书。
建议在沙箱或测试环境中充分验证后,再部署至生产环境,并做好必要的安全评估。
✅ MIT 协议 — 最宽松的开源协议之一,可自由商用、修改、分发,仅需保留版权声明。
经综合评估,MCP工具 在MCP工具赛道中表现稳健,质量良好。如果你已有明确的使用需求,可以直接上手体验;如果还在评估阶段,建议对比同类工具后再做决策。
| 原始名称 | markdown-vault-mcp |
| 原始描述 | 开源MCP工具:Generic markdown collection MCP server with FTS5 + semantic search, frontmatter-。⭐10 · Python |
| Topics | mcpfts5semantic search |
| GitHub | https://github.com/pvliesdonk/markdown-vault-mcp |
| License | MIT |
| 语言 | Python |
收录时间:2026-05-28 · 更新时间:2026-05-30 · License:MIT · AI Skill Hub 不对第三方内容的准确性作法律背书。
选择 Agent 类型,复制安装指令后粘贴到对应客户端