mcp-obsidian
Use when reading, writing, searching, or organizing notes in an Obsidian vault. Triggers on Obsidian, Obsidian vault, read note, write note, update note, search vault, global search, list notes, manage tags, frontmatter, wikilinks, knowledge base, save to Obsidian, Obsidian MCP, search and replace in vault, delete note, note organization, vault maintenance, atomic notes, Zettelkasten.
소스 정보
- 저장소
- george11642/george-plugins
- 최근 소스 활동
- 2026년 3월 11일 22:42
- 감지된 SKILL.md 언어
- 영어
- 스타
- 2
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- mcp-obsidian
- description
- Use when reading, writing, searching, or organizing notes in an Obsidian vault. Triggers on Obsidian, Obsidian vault, read note, write note, update note, search vault, global search, list notes, manage tags, frontmatter, wikilinks, knowledge base, save to Obsidian, Obsidian MCP, search and replace in vault, delete note, note organization, vault maintenance, atomic notes, Zettelkasten.
# MCP Obsidian
Knowledge base management via Obsidian MCP (lazy-loaded via ToolSearch).
## Loading
```
ToolSearch: +obsidian
```
## MCP Tools
| Task | Tool | Key Params |
|------|------|------------|
| Read note | `mcp__obsidian__obsidian_read_note` | path |
| Update note | `mcp__obsidian__obsidian_update_note` | path, content |
| Search vault | `mcp__obsidian__obsidian_global_search` | query |
| List notes | `mcp__obsidian__obsidian_list_notes` | folder (optional) |
| Manage tags | `mcp__obsidian__obsidian_manage_tags` | path, tags |
| Frontmatter | `mcp__obsidian__obsidian_manage_frontmatter` | path, key, value |
| Search & replace | `mcp__obsidian__obsidian_search_replace` | search, replace |
| Delete note | `mcp__obsidian__obsidian_delete_note` | path |
## Workflows
### Research Capture
1. `global_search` -- check if topic already exists
2. If not: `update_note` to create new note with findings
3. `manage_frontmatter` -- add date, status, source metadata
4. `manage_tags` -- add relevant tags for discoverability
### Knowledge Retrieval
1. `global_search` with topic keywords
2. `read_note` on best matches
3. Synthesize across multiple notes if needed
### Vault Maintenance
1. `list_notes` to scan a folder
2. `read_note` on stale entries
3. `manage_frontmatter` to update status (draft/review/published)
4. `search_replace` for bulk renames or link updates
## Note Structure Best Practices
### Frontmatter Template
```yaml
---
date: 2026-03-08
status: draft | review | published
tags: [topic, subtopic]
source: URL or reference
---
```
### Content Conventions
- **Wikilinks**: `[[Related Note]]` for internal connections
- **Tags**: `#topic/subtopic` for cross-cutting categorization
- **Headings**: H2 for sections, H3 for subsections -- enables outline navigation
- **Callouts**: `> [!note]` / `> [!warning]` for emphasis
### Naming Conventions
- Use descriptive titles: "React Server Components Patterns" not "RSC"
- Prefix with date for journal entries: "2026-03-08 Research Session"
- Use folders for broad categories, tags for cross-cutting concerns
## Best Practices
- **Search before creating** -- avoid duplicates in the vault
- **Frontmatter on every note** -- date and tags at minimum
- **Link liberally** -- wikilinks are cheap, orphan notes are expensive
- **One idea per note** -- atomic notes compose better than monoliths
- **Update status** -- mark notes as draft/review/published for triage
GitHub에서 보기