AgentHubAgentHub
Obsidian icon

Obsidian MCP Setup & Guide

MCP ServerMCP Hub 中国

io.mcp-cn.mcp-obsidian

Obsidian的MCP服务器，支持Obsidian的读取和写入

View on MCP Hub 中国 ↗

Copy the install config on this page first, then verify docs and permissions upstream.

Popularity

Uses39.1k

Overview

Obsidian的MCP服务器，支持Obsidian的读取和写入 Obsidian is a MCP Server listed from MCP Hub China. Transports: stdio. This page includes an overview, setup tutorial, install commands, and use cases for Trae, Tongyi Lingma, Cursor, Claude Code, and VS Code.

ObsidianMCP笔记

Use cases

China services

AgentHub Verified AvailabilityTested & Ready

Automated pipeline validated install commands, protocol & client compatibility

Verified At2026-09-29
Install Snippets TestedCLI & JSON config syntax verified
Protocol Handshake ReadyComplies with JSON-RPC 2.0 specifications
Origin Registry ActiveSourced from mcp-cn
Verified ClientsClaude Code、Claude Desktop、Cursor 等
Security Tier: A+ 级 · 零权限本地沙盒 (A+)·Scanned for high-risk vulnerabilities. Recommended to run with project-scoped permissions.

Copy by platform

Choose your platform

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window
Click to copy snippet
{
  "mcpServers": {
    "io-mcp-cn-mcp-obsidian": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-obsidian"
      ]
    }
  }
}

Setup tutorial

  1. Open the Obsidian page and confirm this MCP Server (source: MCP Hub China).
  2. Copy the Cursor, Claude Code, or VS Code snippet.
  3. Merge it into mcpServers and replace env placeholders with real secrets.
  4. Reload the window, then call the MCP tools from your agent chat.

Install commands

Install commands and setup steps are in the HTML so search engines and no-JS browsers can read them without running client JavaScript.

Claude Code (local)

  1. Install Claude Code CLI
  2. Copy the command below, replace <placeholders> with real env values, then run in terminal
  3. See Environment variables below if listed
claude mcp add io-mcp-cn-mcp-obsidian -- npx -y mcp-obsidian

Cursor — .cursor/mcp.json (local)

  1. Open or create .cursor/mcp.json in your project root
  2. Click Copy config and paste; merge only this mcpServers entry if others exist
  3. Replace <placeholders> in env with real secrets (see Environment variables below)
  4. Save, then Cmd+Shift+P → Reload Window
{
  "mcpServers": {
    "io-mcp-cn-mcp-obsidian": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-obsidian"
      ]
    }
  }
}

VS Code — .vscode/mcp.json (local)

  1. Install GitHub Copilot in VS Code with MCP support
  2. Open or create .vscode/mcp.json in your project root
  3. Click Copy config and paste; merge only this mcpServers entry if others exist
  4. Replace <placeholders> in env with real secrets
  5. Save and Developer: Reload Window
{
  "mcpServers": {
    "io-mcp-cn-mcp-obsidian": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-obsidian"
      ]
    }
  }
}

Claude Desktop — claude_desktop_config.json (local)

  1. Open Claude Desktop claude_desktop_config.json (see remote guide for paths)
  2. Click Copy config and merge under mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Fully quit and restart Claude Desktop
{
  "mcpServers": {
    "io-mcp-cn-mcp-obsidian": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-obsidian"
      ]
    }
  }
}

Trae — .trae/mcp.json (local)

  1. Trae → Settings → MCP, or edit .trae/mcp.json / global mcp.json
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env with real secrets
  4. Save and reload Trae
{
  "mcpServers": {
    "io-mcp-cn-mcp-obsidian": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-obsidian"
      ]
    }
  }
}

Cherry Studio — MCP settings (local)

  1. Cherry Studio → Settings → MCP Servers → Add (STDIO)
  2. Or import JSON: click Copy config and merge mcpServers
  3. Replace <placeholders> in env; ensure Node.js / uv (npx, uvx) are installed
  4. Enable the server and check tools load
{
  "mcpServers": {
    "io-mcp-cn-mcp-obsidian": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-obsidian"
      ]
    }
  }
}

Tongyi Lingma — MCP config (local)

  1. Lingma Settings → MCP → + → STDIO or config file
  2. Click Copy config and merge mcpServers
  3. Replace <placeholders> in env; need Node.js 18+ (npx) or uv (uvx)
  4. Confirm connected before using tools in agent chat
{
  "mcpServers": {
    "io-mcp-cn-mcp-obsidian": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-obsidian"
      ]
    }
  }
}

Windsurf — mcp_config.json (local)

  1. Edit ~/.codeium/windsurf/mcp_config.json
  2. Click Copy config and merge mcpServers (stdio same as Cursor)
  3. Replace <placeholders> in env, save, refresh Cascade
{
  "mcpServers": {
    "io-mcp-cn-mcp-obsidian": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-obsidian"
      ]
    }
  }
}

Cline — MCP Servers (local)

  1. Cline panel → Settings → MCP Servers
  2. Click Copy config and merge
  3. Replace <placeholders> in env, then save
{
  "mcpServers": {
    "io-mcp-cn-mcp-obsidian": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-obsidian"
      ]
    }
  }
}

WorkBuddy — .workbuddy/mcp.json (local)

  1. Edit ~/.workbuddy/mcp.json (user) or project .workbuddy/mcp.json
  2. Or Plugins → MCP Servers → Configure MCP and paste the JSON below
  3. Replace <placeholders> in env; on Windows prefer absolute paths for command/scripts
  4. Save, restart WorkBuddy, confirm connector status is green
{
  "mcpServers": {
    "io-mcp-cn-mcp-obsidian": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-obsidian"
      ]
    }
  }
}

Troubleshooting & Common ErrorsFAQ

Common connection errors and verified fixes for Obsidian

Getting 'connection closed' or exit code 1 in Cursor / Claude Code for Obsidian?

Usually caused by missing runtime paths or IDE environment inheritance. Fix steps: 1. Verify Node.js 18+ (npx) or Python 3.10+ (uvx) is installed; 2. Run 'which npx' or 'which uvx' in terminal, and replace 'command' with absolute path; 3. Reload or restart the client window after modifying config.

Fix Snippet
# Check binary path in terminal:
which npx
node -v
Getting 'spawn npx ENOENT' or 'command not found'?

The editor background process does not inherit your full terminal PATH. Solution: Globally install the package, or set the absolute binary path (e.g. C:\Program Files\nodejs\npx.cmd on Windows, or /usr/local/bin/npx on macOS).

Tool calls timing out or failing to download packages?

First-time package downloading might be slow or timeout due to network limits. Configure a reliable mirror or check outbound proxy settings.

Still not connecting? Read the MCP troubleshooting guide →

Tool Mock Playground

Sandbox

Obsidian Tool Interface Simulation · Preview tool schema & outputs without local runtime

Sandbox Ready
fn: io_mcp_cn_mcp_obsidianExecute the core tool interface of Obsidian
Request ArgumentsJSON Schema
{
  "target": "Obsidian",
  "action": "execute",
  "options": {
    "mode": "standard",
    "timeoutMs": 5000
  }
}
💡Parameters generated dynamically by Agent runtime
Agent Tool Output

Click 'Run Mock' above

to preview the raw response returned to the LLM

Env: AgentHub Virtual SandboxJSON-RPC 2.0

Decision Guide: Why & When to Use

Assess suitability before installing to save trial-and-error time

Best Suited For
  • Feishu docs
  • China maps routing
  • WeCom notifications
When NOT to Use
  • Teams with no China accounts
  • Cross-border data compliance concerns
Recommended Workflow Pairing:View Scenario →

Obsidian + Scenario Prompt → Complete Agent Automation

MCP hands-on: install to visible results

Follow the full lab (expected UI/output + contrast checks). After installing this item, verify with the tutorial prompts.

Open tutorial →

Related resources

Often paired with

PC Build Assistant

v0.1.43

SkillClawHub5.1k

io.clawhub.gongyu0918-debug/pc-builder-assistant

Use for budget desktop PC build planning and recommendations, PC hardware DIY, upgrades, configuration completion, compatibility checks, hardware guidance, local LLM GPU/VRAM/RAM sizing, and gaming, streaming, creator, aesthetic, compact or ITX builds. Bundled prices are China-market CNY references; explicit user overlays keep currencies separate. 中文支持预算装机、装机 DIY、整机推荐、旧机升级、配置补全、搭配或兼容检查、硬件问答，以及游戏直播、生产力、本地 AI、外观海景房和紧凑或 ITX 主机。 Do not use for laptops, server procurement, ordering or payment, remote control, security isolation, or standalone software, game or agent tutorials.

source
View on ClawHub

微信小程序开发 · WeChat Mini Program Development

v1.28.65

SkillClawHub5k

io.clawhub.binggg/miniprogram-development

WeChat Mini Program development skill for building, debugging, previewing, testing, publishing, and optimizing mini program projects (小程序开发、调试、预览、发布). Covers project structure and config (`project.config.json`, `appid`, `miniprogramRoot`, `tabBar`, routing/navigation, icon assets), WeChat Developer Tools Nightly workflows (`wechatide` CLI, WeChat IDE Skills/MCP), `miniprogram-ci` preview/upload, console/network debugging, message push (消息推送) and customer-service auto-reply (客服消息), mini program SEO / search indexing (小程序搜索优化、页面收录、搜索推广、mpcrawler), and CloudBase integration (`wx.cloud`, 腾讯云开发, 云开发) when explicitly used. Use when users create, develop, modify, debug, preview, deploy, publish, or promote WeChat Mini Programs. NOT for Web frontend (use web-development), pure backend services (use cloudrun-development / cloud-functions), or UI-design-only tasks (use ui-design).

source
View on ClawHub

Keep exploring AgentHub

Most people compare similar tools or check scenario guides before installing—start here.

Browse more like thisSearch similarPick by scenarioPrompt playbooksMCP hands-onReviews & comparisons

Listing badge: put AgentHub on your site

Copy either snippet into your project homepage, docs, or GitHub README. The badge is a hotlinked SVG — nothing to host — and it links back to this page so visitors can find the install steps.

PreviewListed on AgentHub: Obsidian
HTML
<a href="https://myagenthub.cn/p/io.mcp-cn.mcp-obsidian" title="Listed on AgentHub: Obsidian" target="_blank" rel="noopener">
  <img src="https://myagenthub.cn/badge/io.mcp-cn.mcp-obsidian?lang=en" alt="Listed on AgentHub: Obsidian" height="20" style="border:0"/>
</a>
Markdown (GitHub README)
[![Listed on AgentHub: Obsidian](https://myagenthub.cn/badge/io.mcp-cn.mcp-obsidian?lang=en)](https://myagenthub.cn/p/io.mcp-cn.mcp-obsidian)

Badges are generated on the fly from /badge/<package-id>, so name and listing changes propagate automatically. Keep the link target unchanged — it is what counts as the referral.

Unified Manifest

{
  "id": "io.mcp-cn.mcp-obsidian",
  "type": "mcp-server",
  "version": "latest",
  "displayName": "Obsidian",
  "description": "Obsidian的MCP服务器，支持Obsidian的读取和写入",
  "author": {
    "name": "Henry Mao"
  },
  "iconUrl": "https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcQGpiHGQgbhtPgCcf7nNhSR14ckMAkfH2TCwQ&s",
  "homepage": "https://mcp-cn.com/server/101",
  "distribution": {
    "packages": [
      {
        "registryType": "npm",
        "identifier": "mcp-obsidian",
        "runtimeHint": "npx",
        "transport": "stdio"
      }
    ],
    "remotes": []
  },
  "dependencies": [],
  "installTargets": [
    "claude-code",
    "claude-desktop",
    "cursor",
    "vscode",
    "trae",
    "cherry-studio",
    "lingma",
    "windsurf",
    "cline",
    "workbuddy"
  ],
  "keywords": [
    "use_count:39131",
    "Obsidian",
    "MCP",
    "Obsidian",
    "笔记"
  ],
  "provenance": {
    "origin": "mcp-cn",
    "originalId": "mcp-obsidian",
    "originalUrl": "https://mcp-cn.com/server/101",
    "isOfficial": false,
    "status": "active"
  }
}