AI Skill Hub 强烈推荐:Obsidian MCP连接器 是一款优质的MCP工具。AI 综合评分 8.0 分,在同类工具中表现稳健。如果你正在寻找可靠的MCP工具解决方案,这是一个值得深入了解的选择。
Obsidian MCP连接器 是一款遵循 MCP(Model Context Protocol)标准协议的 AI 工具扩展。通过 MCP 协议,它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务,实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用,都可以通过自然语言在 AI 对话中直接触发,极大提升生产效率。
Obsidian MCP连接器 是一款遵循 MCP(Model Context Protocol)标准协议的 AI 工具扩展。通过 MCP 协议,它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务,实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用,都可以通过自然语言在 AI 对话中直接触发,极大提升生产效率。
# 方式一:通过 Claude Code CLI 一键安装
claude skill install https://github.com/istefox/obsidian-mcp-connector
# 方式二:手动配置 claude_desktop_config.json
{
"mcpServers": {
"obsidian-mcp---": {
"command": "npx",
"args": ["-y", "obsidian-mcp-connector"]
}
}
}
# 配置文件位置
# macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
# Windows: %APPDATA%/Claude/claude_desktop_config.json
# 安装后在 Claude 对话中直接使用 # 示例: 用户: 请帮我用 Obsidian MCP连接器 执行以下任务... Claude: [自动调用 Obsidian MCP连接器 MCP 工具处理请求] # 查看可用工具列表 # 在 Claude 中输入:"列出所有可用的 MCP 工具"
// claude_desktop_config.json 配置示例
{
"mcpServers": {
"obsidian_mcp___": {
"command": "npx",
"args": ["-y", "obsidian-mcp-connector"],
"env": {
// "API_KEY": "your-api-key-here"
}
}
}
}
// 保存后重启 Claude Desktop 生效
Your Obsidian vault, exposed to AI clients over the Model Context Protocol. The MCP server runs inside Obsidian, on loopback, with no binary to download and no cloud round-trip. Claude Desktop, Claude Code, Cursor, Cline, Continue, Windsurf and VS Code all connect to the same endpoint.
What's new · Quick start · Tools · Rendered search results · Adaptive tool loading · Per-client tokens · Prompts · Protocol · Clients · Troubleshooting · Security · For developers
---
Summarize my notes from the past <% tp.mcpTools.prompt("days", "How many days back") %> days about <% tp.mcpTools.prompt("topic", "The subject") %>.
Here is the brief they should be read against:
![[Projects/Q3 brief]]
Give me the three recurring themes and one action item. ```
tp.mcpTools.prompt(...) line declares a parameter and is stripped from the output. Inject the value with {{days}}, {{topic}}, as many times as you like.#mcp-tools-prompt hashtag works instead of frontmatter. Both spellings of the frontmatter tag are accepted.![[{{note}}]] lets the client pick the note. ![[note|alias]], ![[note#Heading]] and ![[note#^blockid]] all work. Depth 1, at most 32 KB across at most 20 embeds per render. An embed that cannot resolve keeps its token and gains a comment saying why, so nothing disappears quietly.Full contract: docs/features/prompt-system.md.
2.0 is the release where this connector stopped waiting for the next MCP revision and started serving it. The protocol work is the substance, and the visible half is that search results now arrive as a list you can read instead of a wall of JSON.
| Change | Why it matters |
|---|---|
**MCP revision 2026-07-28 is served, alongside the old one** (2.0.0) | Two protocol eras on one endpoint, one port, one token, classified per request. A client that speaks the new revision finds it by probing server/discover; a client that does not never sees it. Nothing you have configured needs to change. See [Protocol status](#protocol-status). |
| **Search results render as a ranked list** (2.0.0) | search_vault_smart and search_vault_simple publish an [MCP Apps](#rendered-search-results-mcp-apps) view: one row per hit with the path, the excerpt, and for the semantic search a similarity score and the heading. The text result is byte-identical to before, so clients without the extension see exactly what they saw. |
| **Prompt-list changes are announced for real** (2.0.0) | On the new revision, adding, deleting or renaming a note under Prompts/ tells listening clients to re-read the list. On the old revision the connector now says it cannot, which is the truthful answer. This retraction is what makes the number 2.0. |
| **Per-token request counters** (2.0.0) | The transport settings show how many requests each token served and on which revision, so a client that stopped working is a row whose count stopped moving. |
| **A tool promoted by one client is announced to the others** (2.0.0) | Promotion counters are vault-wide, so one client crossing the threshold widens every adaptive client's list. On the new revision the others are now told instead of serving a stale list. [#419](https://github.com/istefox/obsidian-mcp-connector/issues/419) |
| **Windows bridge: no more mangled accents** (2.0.1) | scripts/obsidian_mcp_bridge.py forces its stdio streams to UTF-8, so æ ø å ü and non-Latin scripts survive in both directions. Root-caused, with the fix, by [@smollern](https://github.com/istefox/obsidian-mcp-connector/discussions/406). |
| **Boolean arguments accept real booleans** (2.0.0) | Six fields across five tools rejected a genuine JSON true, including delete_vault_directory.recursive. [#444](https://github.com/istefox/obsidian-mcp-connector/issues/444) |
**search_vault_smart works under auto again** (2.0.0) | With Smart Connections installed it returned an empty result for every query, silently. [#430](https://github.com/istefox/obsidian-mcp-connector/issues/430) |
<details> <summary>What 1.0.x brought (still current)</summary>
| Change | Why it matters |
|---|---|
| **Per-client bearer tokens** (1.0.0) | The vault holds up to 10 tokens, one per client. Claude Code can keep all 52 tools while claude.ai sees only the 13-tool Core set, from one vault and one server. |
| **Per-token tool policy** (1.0.0) | Profile, promoted tools and an optional hard allowlist all live on the token, not on the vault. |
| **Rotation no longer restarts the transport** (1.0.0) | Adding, renaming, regenerating or revoking a token takes effect on the next request. The port cannot drift and in-flight requests finish. |
**.mcpb bundles are per token** (1.0.0) | Each bundle carries a token id and resolves that token's secret from the vault at connect time. Revoking the token fails the bundle closed instead of silently granting another client's access. |
| **Note embeds in prompts** (1.0.0) | ![[note]] in a prompt body is inlined before the prompt reaches the model, so no tool call per note. |
| **Built-in-Node fix** (1.0.1) | The Claude Desktop extension now works with **Use Built-in Node.js for MCP** left on. See [#412](https://github.com/istefox/obsidian-mcp-connector/issues/412). |
| **Whole-request deadline in the shim** (1.0.1) | A failing request answers inside 45 s with the reason instead of being cancelled at 60 s with nothing logged. |
| **MCP SDK v2, error codes out of the reserved range** (0.28.2, 1.0.1) | See [Protocol status](#protocol-status). |
</details>
Full history: CHANGELOG.md.
istefox/obsidian-mcp-connector.Ask the agent to call get_server_info to confirm the round trip. Requirements: Obsidian 1.7.2+, and Node.js only for the legacy mcp-remote path.
Copy config for streamable-http clients produces the generic payload these accept. Check each client's docs for the file location and wrapping keys.
| Symptom | Cause and fix |
|---|---|
401 on every call | The token matches no row, usually after a regenerate or revoke. Copy the current string from that row, or add a new token if the row is gone. |
ECONNREFUSED 127.0.0.1:<port> | Claude Desktop reads its config only at launch. Quit fully (Cmd+Q) and reopen. Check the port matches the one the plugin logs, and that only one vault has the plugin enabled. |
Claude Desktop: Failed to connect, command not found | Only affects the mcp-remote path. Settings → **Claude Desktop integration** reports whether node and npx are on the PATH Obsidian inherits, and installs Node for you on macOS. |
| 60 s hang on Windows, then "Could not attach" | mcp-remote bug. Switch to the [POST-only bridge](#claude-desktop). |
| 60 s hang on macOS with **Use Built-in Node.js for MCP** on | Fixed in **v1.0.1**. Update, re-export the .mcpb, reinstall once; the setting can stay on. On 1.0.0 and earlier, turn the setting off and restart fully. ([#412](https://github.com/istefox/obsidian-mcp-connector/issues/412)) |
.mcpb disconnected most of the time | Fixed in v0.26.0, which stopped baking the port and token into the manifest. Update and re-export once. |
First search_vault_smart is slow | Expected: ~25 MB model download, cached afterwards. A content-length warning in DevTools is harmless. |
On the built-in-Node path Claude Desktop does not write the connector's own stderr to mcp-server-Obsidian MCP Connector.log, so the startup banner and per-request lines are missing there even when everything works. To collect them, run the extension's server/index.js directly, or turn the setting off for the test. General logs: Settings → Open Logs, or Obsidian's console (Cmd+Opt+I / Ctrl+Shift+I).
obsidian-mcp-connector 是一个专为 Obsidian 设计的 MCP Connector 插件。它通过 MCP 协议将您的 Obsidian Vault 连接到兼容的 AI 客户端,让 AI 能够直接与您的本地笔记库进行交互,实现智能化的知识管理体验。
该插件通过连接到兼容 MCP 的客户端,赋予 AI 强大的 Vault 访问能力。它提供了 18 个经过类型定义的工具(如 get_vault_file、create_vault_file、patch_vault_file 等),支持对笔记进行读、写、修改及重命名操作,并原生支持图片和音频等二进制内容的处理。此外,它还能自动识别并加载您在 Prompts 文件夹中标记为 #mcp-tools-prompt 的提示词。
使用本插件需要满足以下前提条件:首先,必须在您的 Vault 根目录下创建一个名为 `Prompts`(首字母大写)的文件夹,用于存放提示词模板;插件内置了渲染器,无需额外插件即可运行。对于开发者环境,需要安装最新版本的 Bun 以及 TypeScript 5+。请注意,若需使用特定高级功能,可能需要配合 Templater 等插件。
您可以通过两种方式安装:首先是官方推荐方式,直接在 Obsidian 的 Community plugin store 中搜索 "MCP Connector" 并安装启用;其次是通过 BRAT 进行安装。安装完成后,插件设置界面会为不同的客户端家族提供 "Copy config" 按钮,您可以直接点击复制生成的 JSON 配置片段,并粘贴到您的客户端设置中。配置完成后,建议通过调用 `get_server_info` 工具来验证端到端的连接是否成功。
插件配置具有高度的可扩展性。虽然核心功能无需额外配置,但如果您希望使用 `execute_template` 工具,则需要安��� Templater 插件;若需使用 `search_vault` 工具进行 DQL 或 JsonLogic 查询,则需要安装 Local REST API 插件。此外,插件还支持与 Smart Connections 等工具的潜在集成,以增强 AI 对笔记内容的理解能力。
本章节涵盖了 90% 的常见使用场景。如果您需要了解完整的技术规范,包括文件夹命名规则、Frontmatter Schema 定义、参数解析逻辑、执行流程以及已知限制等详细信息,请查阅官方文档中的 `docs/features/prompt-system.md` 文件。
在运行时,所有对 Vault 的访问均通过 Obsidian 原生的 `app.vault` 和 `app.workspace` API 完成,并遵循 Obsidian 的权限模型。目前的架构已优化,大多数工具不再强制依赖 Local REST API。此外,为了安全性,命令执行功能采用了“按需开启”的机制,您可以为每个 Vault 设置专门的允许列表(Allowlist)。
如果在配置或使用过程中遇到问题,可以参考 FAQ 部分进行排查。常见的检查点包括:验证客户端是否正确加载了来自本服务器的 43 个 MCP tools,以及检查 Bearer Token 是否正确,确保客户端能够成功访问进程内的服务器。
高质量的Obsidian MCP连接器,扩展了Obsidian的功能
AI Skill Hub 为第三方内容聚合平台,本页面信息基于公开数据整理,不对工具功能和质量作任何法律背书。
建议在沙箱或测试环境中充分验证后,再部署至生产环境,并做好必要的安全评估。
✅ MIT 协议 — 最宽松的开源协议之一,可自由商用、修改、分发,仅需保留版权声明。
总体来看,Obsidian MCP连接器 是一款质量优秀的MCP工具,在同类工具中具备一定竞争力。AI Skill Hub 将持续追踪其更新动态,建议收藏备用,结合自身场景选择合适时机引入使用。
| 原始名称 | obsidian-mcp-connector |
| 原始描述 | 开源MCP工具:Add integrations like semantic search and custom Templater prompts to Claude or 。⭐8 · TypeScript |
| Topics | obsidianmcptypescript |
| GitHub | https://github.com/istefox/obsidian-mcp-connector |
| License | MIT |
| 语言 | TypeScript |
收录时间:2026-06-01 · 更新时间:2026-06-01 · License:MIT · AI Skill Hub 不对第三方内容的准确性作法律背书。
选择 Agent 类型,复制安装指令后粘贴到对应客户端