📄 工具详情 ⚙️ 安装教程 📚 使用教程
能力标签
🔌 MCP🤖 Agent🔄 工作流🐳 Docker💻 CLI🔗 REST API🧬 Embedding🧠 Claude
Obsidian MCP连接器
🔌
MCP工具

Obsidian MCP连接器

基于 TypeScript · 让 AI 助手直接操作你的系统与工具
英文名：obsidian-mcp-connector
⭐ 8 Stars 🍴 1 Forks 💻 TypeScript 📄 MIT 🏷 AI 8.0分
8.0AI 综合评分
obsidianmcptypescript
⬇ 下载源码 ZIP ⚙️ 配置说明 📺 TG 频道
✦ AI Skill Hub 推荐

AI Skill Hub 强烈推荐：Obsidian MCP连接器 是一款优质的MCP工具。AI 综合评分 8.0 分，在同类工具中表现稳健。如果你正在寻找可靠的MCP工具解决方案，这是一个值得深入了解的选择。

📚 深度解析

Obsidian MCP连接器 是一款基于 MCP（Model Context Protocol）标准协议的 AI 工具扩展。MCP 协议由 Anthropic 开发并开源，旨在建立 AI 模型与外部工具之间的标准化通信接口，目前已被 Claude Desktop、Claude Code、Cursor 等主流 AI 工具采纳。

通过安装 Obsidian MCP连接器，你的 AI 助手将获得额外的工具调用能力，可以用自然语言直接操控该工具的功能，无需学习复杂的命令行语法。MCP 工具的核心价值在于"一次配置，永久增强"——配置完成后，每次与 AI 对话时都可以无缝调用这些工具。

在技术实现上，MCP 工具通过标准的 JSON-RPC 协议与 AI 客户端通信，工具的功能以"工具列表"的形式暴露给 AI 模型，AI 可以按需调用。Obsidian MCP连接器 提供了结构化的工具调用接口，使 AI 模型能够精确地理解和使用每个功能点，显著降低 AI 在工具使用上的错误率。

与传统的 API 集成相比，MCP 工具的优势在于无需编写代码——用户只需在配置文件中添加几行 JSON，即可让 AI 获得全新能力。AI Skill Hub 将 Obsidian MCP连接器 评为 AI 评分 8.0 分，属于同类工具中的优质选择。

📋 工具概览

Obsidian MCP连接器 是一款遵循 MCP（Model Context Protocol）标准协议的 AI 工具扩展。通过 MCP 协议，它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务，实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用，都可以通过自然语言在 AI 对话中直接触发，极大提升生产效率。

GitHub Stars
⭐ 8
开发语言
TypeScript
支持平台
Windows / macOS / Linux
维护状态
轻量级项目，按需更新
开源协议
MIT
AI 综合评分
8.0 分
工具类型
MCP工具
Forks
1

📖 中文文档

以下内容由 AI Skill Hub 根据项目信息自动整理，如需查看完整原始文档请访问底部「原始来源」。

Obsidian MCP连接器 是一款遵循 MCP（Model Context Protocol）标准协议的 AI 工具扩展。通过 MCP 协议，它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务，实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用，都可以通过自然语言在 AI 对话中直接触发，极大提升生产效率。

📌 核心特色
  • 通过标准 MCP 协议与 Claude、Cursor 等主流 AI 客户端深度集成
  • 提供结构化工具调用接口，显著降低 AI 集成复杂度
  • 支持 Claude Desktop 和 Claude Code 无缝接入，开箱即用
  • 可与其他 MCP 工具组合叠加，构建完整 AI 工作站
  • 轻量无侵入设计，不影响现有系统架构
🎯 主要使用场景
  • 在 Claude Desktop 对话中直接调用本地工具，实现 AI 与系统的深度联动
  • 通过自然语言驱动复杂的多步骤自动化任务，代替繁琐手动操作
  • 将多个 MCP 工具组合使用，构建个人专属 AI 工作站
以下安装命令基于项目开发语言和类型自动生成，实际以官方 README 为准。
安装命令
# 方式一：通过 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
📋 安装步骤说明
  1. 确认已安装 Node.js（v18 或以上版本）
  2. 打开 Claude Desktop 或 Claude Code 的 MCP 配置文件
  3. 按「交给 Agent 安装 → Claude Desktop」标签中的 JSON 配置填入 mcpServers 字段
  4. 保存配置文件并重启 Claude 客户端
  5. 重启后，在对话中即可使用本工具
以下用法示例由 AI Skill Hub 整理，涵盖最常见的使用场景。
常用命令 / 代码示例
# 安装后在 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 生效
📑 README 深度解析 真实文档 完整度 37/100 查看 GitHub 原文 →
以下内容由系统直接从 GitHub README 解析整理，保留代码块、表格与列表结构。

MCP Connector for Obsidian

[!WARNING] Known issue: on Obsidian 1.14 (Electron 43) the window can go blank while this plugin loads. It affects macOS and Windows and is a crash of Obsidian's renderer, not an error thrown by this plugin. Update to 3.1.1 or later. The crash reports hold two signatures. The first, V8 stopping inside a read of Node's AsyncLocalStorage, is gone since 3.1.0, which no longer uses it inside Obsidian: on one Mac with Obsidian 1.14.5 (Electron 43.8.3), toggling the plugin off and on, 3.0.3 crashed on the first reload and 3.1.0-alpha.2 (the same fix as 3.1.0) crashed once in 200. The second is V8 running out of JavaScript heap: every reload of the plugin kept the previous instance in memory, about 40 MB each, through a global that the plugin's schema library registers and never removes. 3.1.1 removes it when the plugin unloads: on one Mac with Obsidian 1.15.0 (Electron 43.8.3), 420 reloads, with and without MCP clients connected, and no crash. The Electron 43.8.3 that ships with the Obsidian 1.14.5 installer changes neither on its own. I saw no crash on Electron 39.8.3 (Obsidian installer 1.12.7). If the window goes blank, restart Obsidian: the plugin usually loads on the next try. Reported to Obsidian on their forum, tracked here in #597 and #609.

GitHub release (latest by date) Build status License Downloads Stars Forks

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 in 3.0.0 · Quick start · Tools · Rendered search results · Adaptive tool loading · Per-client tokens · Prompts · Protocol · Clients · Troubleshooting · Security · For developers

---

description: Summarize my recent daily notes on a given topic

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. ```

  • The 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.
  • An inline #mcp-tools-prompt hashtag works instead of frontmatter. Both spellings of the frontmatter tag are accepted.
  • Embeds are inlined after parameters are filled, so ![[{{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.
  • Other Templater expressions pass through verbatim; the server does not evaluate them.

Full contract: docs/features/prompt-system.md.

What's new in 3.2.0

ChangeWhy it matters
**Fewer tools per session for older tokens**Access Control points out tokens still on All tools and moves them to Adaptive after a preview: about 12k tokens less of tool list in every session.
**No search-results view for Codex and Claude Code**Installing for Codex or copying the Claude Code config turns the view off for that token, about 1k tokens less per search.
**show_file_in_obsidian never writes**The read-only tool no longer creates a missing file.
**Clients in Docker or Podman**The broker URL works from a container with host.docker.internal. See [Clients in Docker or Podman](#clients-in-docker-or-podman).

The full list is in the CHANGELOG.

What's new in 3.1.0

ChangeWhy it matters
**Fewer blank windows on Obsidian 1.14**The plugin no longer uses AsyncLocalStorage inside Obsidian, and 3.1.1 stops a reload from keeping the previous instance in memory. On one Mac: a crash on the first reload with 3.0.3, one in 200 with 3.1.0, none in 420 with 3.1.1. See the known issue at the top.
**Headless mode**obsidian-mcp-headless serves the vault tools from a folder without Obsidian running. See [Headless mode](#headless-mode).
**Lighter plugin load**The semantic search engine loads the first time a search needs it, not at startup.
**Smaller tool results**Each result carries its data once instead of twice.

The full list is in the CHANGELOG.

What's new in 3.0.0

[!IMPORTANT] 3.0.0 is a major release, and it changes how every client connects. The shared broker now runs inside Obsidian on port 27200 and serves Claude Code, Claude Desktop, Codex, Cursor and the rest from one stable address. Existing Codex entries return 401 until you reinstall them from the new Codex menu. Read Upgrading from 2.x before you update.

Every release is announced on the Obsidian forum thread, where questions and ideas are welcome too.

ChangeWhy it matters
**One broker for every client**Copy buttons and the Claude Desktop sync now give http://127.0.0.1:27200/v1/<route-id>/mcp. The address survives vault port changes and the port swaps caused by opening vaults in a different order. If the hosting vault closes, another open vault takes over after a short outage. Each client's own bearer token reaches the vault, so per-client tokens and tool profiles apply as on a direct port.
**No separate process**The detached Node.js broker and its executable in application data are gone. The broker is plugin code in Obsidian's renderer, so there is nothing outside Obsidian to start, update or kill.
**A Codex menu on every token row**Copy the config.toml snippet, copy a codex mcp add command, install into your Codex config, or install into a project. An install shows a preview first, then writes with a backup, a lock, an atomic write and a read-back.
**Safe Codex installs**The installer refuses an entry that belongs to another vault, so two equally named vaults cannot overwrite each other. It migrates entries written by 2.11 and 2.12, and keeps your tool approvals and policy keys.
**Register one project**Set **Project path** in Access Control. Claude Code copies a local-scope claude mcp add command for that project, and Codex installs into the project's .codex/config.toml. A project install never writes your token: it reads OBSIDIAN_MCP_TOKEN.
**All tools offer for Codex**Codex does not refetch the tool list during a session, so an install on an **Adaptive** token offers to switch it to **All tools**. It is unticked by default and applied only after a successful install.
**Clear errors from the broker**When the broker cannot reach a vault, **Broker connection** shows **Refused** with the cause and what to change, and the copy buttons hand out the vault's direct URL meanwhile.
**Codex needs no Node.js**Node.js is still needed for the .mcpb export and the mcp-remote path.

What's new in 2.8 to 2.12

Five releases followed a code and protocol audit (docs/audit-2026-10-02.md). The tool count went from 52 to 64, writes got safer, and search got shorter and more precise.

ChangeWhy it matters
**12 new tools** (2.8.0, 2.9.0)get_workspace_state, list_tasks, set_task_status, get_note_properties, update_note_properties, rename_tag, update_canvas_node and delete_canvas_node in 2.8.0. get_file_info, list_attachments, ensure_block_id and search_files_by_name in 2.9.0.
**Safer writes** (2.8.0, 2.9.0)update_active_file, delete_vault_file and delete_active_file take expectedContent. delete_vault_directory has dry_run and trash, rename_heading has dry_run. delete_vault_file refuses a folder, and show_file_in_obsidian never creates a missing file.
**Search that fits a conversation** (2.9.0 to 2.12.0)search_vault_simple takes regex, caseSensitive and scope. search_vault_smart takes excerptLength and compact (2.10.0), and groupByFile (2.12.0), which keeps the best chunk of each note so limit counts notes. A full sentence ranks better than a list of keywords.
**Rendered search view has an off switch** (2.8.0)Turn it off for the whole vault, or per token, for hosts that show the view fully expanded.
**Client configs are named after the vault** (2.10.0, 2.11.0)Entries are obsidian_<vault>, with a hash for non-ASCII vault names. Claude Code gets a token-free .mcp.json entry and Codex can read the token from OBSIDIAN_MCP_TOKEN, so the secret stays out of committed files.
**Copying a vault no longer shares credentials** (2.10.0)**Make this copy independent** and **Replace all token secrets** each change only what their label says.
**Lighter and faster** (2.8.0 to 2.11.0)main.js went from 3.19 MB to 2.80 MB, settings are read once per request, and list_tasks pages with offset without reading every note.
**Fixes worth knowing**The rendered view works in hosts that block blob: scripts ([#538](https://github.com/istefox/obsidian-mcp-connector/issues/538), [@AS-prog](https://github.com/AS-prog)). execute_template renders against the note it creates ([#541](https://github.com/istefox/obsidian-mcp-connector/issues/541)).

What's new in 2.0.x

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.

ChangeWhy 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>

ChangeWhy it matters
**Per-client bearer tokens** (1.0.0)The vault holds up to 10 tokens, one per client. Claude Code can keep all 64 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.

Quick start

  1. Install the plugin. Community store: Settings → Community plugins → Browse → MCP Connector. Or via BRAT with istefox/obsidian-mcp-connector.
  2. Open Settings → MCP Connector → Access control. A fresh vault already has one token, labelled Default.
  3. Wire your client from that token's row. Either .mcpb (Claude Desktop, drag and drop) or Copy config (everything else). Details in Connecting a client.

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.

Cursor, Continue, Windsurf, VS Code

Cursor / Continue / VS Code copies the generic "type": "streamable-http" payload these accept. Check each client's docs for the file location and wrapping keys.

🇨🇳 中文文档镜像 AI 翻译 2026-06-01
英文原文章节由系统翻译为中文摘要，便于快速理解。完整原文见上方 "📑 README 深度解析"。
📌 简介

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 等插件。

🛠 安装步骤（Docker/pip/源码）

您可以通过两种方式安装：首先是官方推荐方式，直接在 Obsidian 的 Community plugin store 中搜索 "MCP Connector" 并安装启用；其次是通过 BRAT 进行安装。安装完成后，插件设置界面会为不同的客户端家族提供 "Copy config" 按钮，您可以直接点击复制生成的 JSON 配置片段，并粘贴到您的客户端设置中。配置完成后，建议通过调用 `get_server_info` 工具来验证端到端的连接是否成功。

⚙️ 配置说明（含 MCP / env）

插件配置具有高度的可扩展性。虽然核心功能无需额外配置，但如果您希望使用 `execute_template` 工具，则需要安��� Templater 插件；若需使用 `search_vault` 工具进行 DQL 或 JsonLogic 查询，则需要安装 Local REST API 插件。此外，插件还支持与 Smart Connections 等工具的潜在集成，以增强 AI 对笔记内容的理解能力。

🔌 API 说明

本章节涵盖了 90% 的常见使用场景。如果您需要了解完整的技术规范，包括文件夹命名规则、Frontmatter Schema 定义、参数解析逻辑、执行流程以及已知限制等详细信息，请查阅官方文档中的 `docs/features/prompt-system.md` 文件。

🔄 工作流/模块

在运行时，所有对 Vault 的访问均通过 Obsidian 原生的 `app.vault` 和 `app.workspace` API 完成，并遵循 Obsidian 的权限模型。目前的架构已优化，大多数工具不再强制依赖 Local REST API。此外，为了安全性，命令执行功能采用了“按需开启”的机制，您可以为每个 Vault 设置专门的允许列表（Allowlist）。

❓ FAQ 摘要

如果在配置或使用过程中遇到问题，可以参考 FAQ 部分进行排查。常见的检查点包括：验证客户端是否正确加载了来自本服务器的 43 个 MCP tools，以及检查 Bearer Token 是否正确，确保客户端能够成功访问进程内的服务器。

🎯 aiskill88 AI 点评 A 级 2026-06-01

高质量的Obsidian MCP连接器，扩展了Obsidian的功能

📚 实用指南（长尾问题）
适合谁
  • 需要让 Claude / Cursor 操作本地工具的 AI 工程师
  • 构建多智能体协作系统的 Agent 开发者
  • 构建企业知识库 / RAG 检索应用的团队
最佳实践
  • 配置 MCP 服务器时建议使用 stdio 传输 + JSON-RPC，避免暴露公网
  • 分块大小建议 256-512 tokens，向量库优选 pgvector 或 Qdrant
  • Agent 任务先做 dry-run 验证工具调用链，再开启自主执行
常见错误
  • API key 直接提交到 git 仓库（请用 .env 并加入 .gitignore）
  • MCP 配置路径拼错或权限不足，重启 Claude Desktop 才生效
  • embedding 模型与查询模型不一致导致检索失效
部署方案
  • CLI：直接 npm install -g / pip install，命令行调用
  • 云端托管：可放在 Vercel / Railway / Fly.io 等 PaaS 平台
相关搜索
obsidian-mcp-connector 中文教程obsidian-mcp-connector 安装报错怎么办obsidian-mcp-connector MCP 配置obsidian-mcp-connector Agent 工作流obsidian-mcp-connector 与同类工具对比obsidian-mcp-connector 最佳实践obsidian-mcp-connector 适合谁用

⚡ 核心功能

👥 适合谁
  • 需要让 Claude / Cursor 操作本地工具的 AI 工程师
  • 构建多智能体协作系统的 Agent 开发者
  • 构建企业知识库 / RAG 检索应用的团队
⭐ 最佳实践
  • 配置 MCP 服务器时建议使用 stdio 传输 + JSON-RPC，避免暴露公网
  • 分块大小建议 256-512 tokens，向量库优选 pgvector 或 Qdrant
  • Agent 任务先做 dry-run 验证工具调用链，再开启自主执行
⚠️ 常见错误
  • API key 直接提交到 git 仓库（请用 .env 并加入 .gitignore）
  • MCP 配置路径拼错或权限不足，重启 Claude Desktop 才生效
  • embedding 模型与查询模型不一致导致检索失效

👥 适合人群

Claude Desktop / Claude Code 用户AI 工具开发者需要扩展 AI 能力的专业人士自动化工程师

🎯 使用场景

  • 在 Claude Desktop 对话中直接调用本地工具，实现 AI 与系统的深度联动
  • 通过自然语言驱动复杂的多步骤自动化任务，代替繁琐手动操作
  • 将多个 MCP 工具组合使用，构建个人专属 AI 工作站

⚖️ 优点与不足

✅ 优点
  • +MIT 协议，可免费商用
  • +标准化 MCP 协议，生态互联性强
  • +与 Claude 官方生态无缝对接
  • +即插即用，配置简单快捷
⚠️ 不足
  • −依赖 Claude 客户端，非 Claude 用户无法使用
  • −MCP 协议仍在持续演进，接口可能变更
  • −需要一定的配置步骤
⚠️ 使用须知

AI Skill Hub 为第三方内容聚合平台，本页面信息基于公开数据整理，不对工具功能和质量作任何法律背书。

建议在沙箱或测试环境中充分验证后，再部署至生产环境，并做好必要的安全评估。

📄 License 说明

✅ MIT 协议 — 最宽松的开源协议之一，可自由商用、修改、分发，仅需保留版权声明。

🔗 相关工具推荐

FastGPT
基于LLM的知识平台，提供综合解决方案
mcp-use MCP工具
MCP工具
私有GPT
MCP工具
playwright-mcp MCP工具
基于Playwright的MCP协议服务器实现，提供浏览器自动化能力。支持网页交互、截图、数据采集等功能，适合开发者集成
📚 相关教程推荐
天涯社区重启：一个时代结束后，AI社区时代正在开始
帮助中心 · AI Skill Hub
MCP 配置教程
帮助中心 · AI Skill Hub
MCP 工具
帮助中心 · AI Skill Hub
Cursor AI 编程完全指南：Rules 配置、Composer 使用、MCP 集成
帮助中心 · AI Skill Hub
📰 相关 AI 新闻
AI Agent 自主化能力最新进展
AI 资讯 · 知识关联
AI 前沿资讯：Is your AI strategy burning ca…
AI 资讯 · 知识关联
AI Agent 自主化能力最新进展
AI 资讯 · 知识关联
AI Agent 自主化能力最新进展
AI 资讯 · 知识关联
🍿 AI 圈相关吃瓜
配了5个 MCP 工具，Claude 一个都没用
AI 圈观察
Filesystem MCP 帮 Claude 找文件，找了整个 node_modules
AI 圈观察
MCP 生态的现状：工具多，能用的少
AI 圈观察
🗺️ 相关解决方案
mcp
mcp-server-setup
agent
ai-agent-workflow
workflow
ai-workflow-templates
cli
cli-productivity
🧩 你可能还需要
基于当前 Skill 的能力图谱，自动补全的工具组合
Augustus
LLM安全测试框架，检测prompt注入、越狱等
爬虫lama
本地AI代理，通过Ollama回答问题
gptme Agent工作流
MCP · Agent · 工作流
LEANN AI技能包
MCP · Agent · 工作流
MassGen多智能体系统
MCP · Agent · 工作流
Arkiv媒体资产管理器
本地优先的媒体资产管理工具，集成AI语义搜索和专业相机元数据读取功能。支持DaVinci Resolve集成，适合视频编辑、摄影师和内容创作

❓ 常见问题 FAQ

obsidian-mcp-connector 是一款TypeScript开发的AI辅助工具。开源MCP工具：Add integrations like semantic search and custom Templater prompts to Claude or 。⭐8 · TypeScript 主要应用场景包括：Obsidian插件开发。
💡 AI Skill Hub 点评

总体来看，Obsidian MCP连接器 是一款质量优秀的MCP工具，在同类工具中具备一定竞争力。AI Skill Hub 将持续追踪其更新动态，建议收藏备用，结合自身场景选择合适时机引入使用。

⬇️ 获取与下载
⬇ 下载源码 ZIP

✅ MIT 协议 · 可免费商用 · 直接从 aiskill88 服务器下载，无需跳转 GitHub

📚 深入学习 Obsidian MCP连接器
查看分步骤安装教程和完整使用指南，快速上手这款工具
⚙️ 安装教程 📚 使用教程
🌐 原始信息
原始名称 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
🔗 原始来源
🐙 GitHub 仓库  https://github.com/istefox/obsidian-mcp-connector

收录时间：2026-06-01 · 更新时间：2026-06-01 · License：MIT · AI Skill Hub 不对第三方内容的准确性作法律背书。

📺 订阅 AI Skill Hub Daily Telegram 频道
每天 8 条精选 AI Skill、MCP、Agent 与自动化工具推送
加入频道 →