obsidian-plugin-skill MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

Obsidian Plugin API patterns (Plugin/Notice/MarkdownView)
manifest.json + versions.json + minAppVersion handling
Settings tab + editor extensions + commands
Release flow via GitHub tags for Community store
TypeScript + esbuild scaffold

라이브 데모

실제 사용 모습

obsidian-plugin-skill.replay ▶ 준비됨

0/0

설치

클라이언트 선택

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "obsidian-plugin-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/gapmiss/obsidian-plugin-skill",
        "~/.claude/skills/obsidian-plugin-skill"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "obsidian-plugin-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/gapmiss/obsidian-plugin-skill",
        "~/.claude/skills/obsidian-plugin-skill"
      ],
      "_inferred": true
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "obsidian-plugin-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/gapmiss/obsidian-plugin-skill",
        "~/.claude/skills/obsidian-plugin-skill"
      ],
      "_inferred": true
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "obsidian-plugin-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/gapmiss/obsidian-plugin-skill",
        "~/.claude/skills/obsidian-plugin-skill"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "obsidian-plugin-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/gapmiss/obsidian-plugin-skill",
        "~/.claude/skills/obsidian-plugin-skill"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

{
  "context_servers": {
    "obsidian-plugin-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/gapmiss/obsidian-plugin-skill",
          "~/.claude/skills/obsidian-plugin-skill"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add obsidian-plugin-skill -- git clone https://github.com/gapmiss/obsidian-plugin-skill ~/.claude/skills/obsidian-plugin-skill

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: obsidian-plugin-skill

How to build and release your first Obsidian plugin

👤 Obsidian power users who want to scratch an itch ⏱ ~120 min intermediate

언제 쓸까: You have a concrete workflow improvement and want a plugin in a day.

사전 조건

Node 18+ — nvm install 18
A local vault for testing — Create a new Obsidian vault just for development
Skill cloned — git clone https://github.com/gapmiss/obsidian-plugin-skill ~/.claude/skills/obsidian-plugin-skill

흐름

Scaffold the plugin

Scaffold an Obsidian plugin called 'smart-outline' with a command and a settings tab.✓ 복사됨

→ Folder with manifest, main.ts, build config
Add the feature

Implement: on command, open a modal showing the outline of the active note.✓ 복사됨

→ Working modal reading from the active MarkdownView
Side-load and test

Install into the dev vault's plugins folder and reload Obsidian.✓ 복사됨

→ Plugin shows up, command works
Prepare a release

Create versions.json and tag a v0.1.0 release.✓ 복사됨

→ GitHub release with main.js + manifest.json attached

결과: A working, installable plugin you can submit to the Community store.

함정

Forgetting versions.json — Community store rejects — Skill reminds; always keep it in sync with manifest.json
Referencing Obsidian internals that aren't part of the API — Stick to the public API; treat internals as volatile

함께 쓰기: filesystem · github

Add a proper settings tab to an existing plugin

👤 Existing plugin authors improving UX ⏱ ~30 min intermediate

언제 쓸까: Your plugin has grown and needs user-configurable options.

흐름

Design the settings

Based on my plugin's README, what settings should be user-configurable?✓ 복사됨

→ Short list with rationale
Implement PluginSettingTab

Add a PluginSettingTab with those controls.✓ 복사됨

→ Settings UI in Obsidian

결과: A settings tab users can actually use.

함정

Too many settings — Ruthlessly cut — unused settings are clutter

조합

다른 MCP와 조합해 10배 효율

obsidian-plugin-skill + filesystem

Read an existing plugin and extend it

Read my-plugin/, add a new command that exports the active note as PDF.✓ 복사됨

obsidian-plugin-skill + github

Automate tagging and release creation

Tag v0.2.0 and publish release with the built assets.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출
plugin-scaffolding	plugin intent	New plugin
feature-authoring	feature spec + API surface	Every feature
settings-tab	options	UX improvements
release-flow	version bump	Before publishing

비용 및 제한

운영 비용

API 쿼터: none
호출당 토큰: 5–20k per plugin
금액: free
팁: Work feature-by-feature rather than dumping a full plugin spec on Claude

보안

권한, 시크릿, 파급범위

자격 증명 저장: GitHub token for releases (if automating)

데이터 외부 송신: none at skill layer

Plugins run with full access to the vault — review before installing community plugins

문제 해결

자주 발생하는 오류와 해결

Obsidian doesn't load the plugin

Confirm manifest.json is valid JSON and in the right vault path; reload via Ctrl+R.

확인: cat .obsidian/plugins/my-plugin/manifest.json | jq .

Build produces no main.js

Run the esbuild command; check tsconfig target.

확인: ls main.js

대안

obsidian-plugin-skill 다른 것과 비교

대안	언제 쓰나	단점/장점
logseq	You're on Logseq rather than Obsidian	Different plugin API

obsidian-plugin-skill