Lion-1209/dsh-plugin-wiki-skills / skills/wiki
wiki
VerifiedClaude + Obsidian knowledge companion. Sets up a persistent wiki vault, scaffolds structure from a one-sentence description, and routes to specialized sub-skills. Use for setup, scaffolding, cross-project referencing, and hot cache management. Triggers on: "set up wiki", "scaffold vault", "create knowledge base", "/wiki", "wiki setup", "obsidian vault", "knowledge base", "second brain setup", "running notetaker", "persistent memory", "llm wiki".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.6 KB |
| references/css-snippets.md | markdown | 4.2 KB |
| references/frontmatter.md | markdown | 2.1 KB |
| references/git-setup.md | markdown | 1.1 KB |
| references/mcp-setup.md | markdown | 4.3 KB |
| references/modes.md | markdown | 7.8 KB |
| references/plugins.md | markdown | 3.4 KB |
| references/rest-api.md | markdown | 2.1 KB |
references/mcp-setup.md
View on GitHub# MCP Setup
MCP lets Claude read and write vault notes directly without copy-paste. Four options ordered from simplest to most featureful.
> [!tip] Recommendation
> If you have **Obsidian v1.12 or newer**, start with **Option D: Obsidian CLI**. It needs no MCP server, no plugins, and no TLS workarounds. Use Options A or B only if you need persistent MCP integration or are on an older Obsidian version.
---
## Step 1: Install the Local REST API Plugin
You must do this in Obsidian (Claude cannot do it programmatically):
1. Obsidian > Settings > Community Plugins > Turn off Restricted Mode
2. Browse > Search "Local REST API" > Install > Enable
3. Settings > Local REST API > Copy the API key
The plugin runs on `https://127.0.0.1:27124` with a self-signed certificate.
Test it:
```bash
curl -sk -H "Authorization: Bearer <YOUR_KEY>" https://127.0.0.1:27124/
```
You should get a JSON response with vault info.
---
## Option A: mcp-obsidian (REST API based)
Uses MarkusPfundstein's mcp-obsidian. Requires the Local REST API plugin running.
```bash
claude mcp add-json obsidian-vault '{
"type": "stdio",
"command": "uvx",
"args": ["mcp-obsidian"],
"env": {
"OBSIDIAN_API_KEY": "<YOUR_KEY>",
"OBSIDIAN_HOST": "127.0.0.1",
"OBSIDIAN_PORT": "27124",
"NODE_TLS_REJECT_UNAUTHORIZED": "0"
}
}' --scope user
```
> [!warning] Security
> `NODE_TLS_REJECT_UNAUTHORIZED: "0"` **disables TLS certificate verification process-wide** for the MCP server. It is required here because the Local REST API plugin uses a self-signed certificate. This is acceptable for `127.0.0.1` (localhost) connections only. Never use this setting for any non-loopback connection. If you are uncomfortable with the global TLS bypass, prefer **Option D (Obsidian CLI)** or **Option B (filesystem-based)** which avoid this entirely.
Capabilities: read notes, write notes, search, patch frontmatter fields, append under headings.
---
## Option B: MCPVault (filesystem based)
No Obsidian plugin needed. Reads the vault directory directly.
```bash
claude mcp add-json obsidian-vault '{
"type": "stdio",
"command": "npx",
"args": ["-y", "@bitbonsai/mcpvault@latest", "/absolute/path/to/your/vault"]
}' --scope user
```
Replace `/absolute/path/to/your/vault` with the actual vault path.
Tools available: `search_notes` (BM25), `read_note`, `create_note`, `update_note`, `get_frontmatter`, `update_frontmatter`, `list_all_tags`, `read_multiple_notes`.
---
## Option C: Direct REST API via curl
No MCP needed. Use curl in bash throughout the session. See `rest-api.md` for all commands.
---
## Option D: Obsidian CLI (recommended for v1.12+)
Obsidian shipped a native CLI in v1.12 (2026). It exposes vault operations directly to the terminal. No REST API plugin, no MCP server, no self-signed certs, no TLS workarounds. Claude calls it through the Bash tool.
**Check if available:**
```bash
which obsidian-cli 2>/dev/null && obsidian-cli --version
# or, on flatpak:
flatpak run md.obsidian.Obsidian --cli --version
```
**Common operations:**
```bash
# List all notes in a folder
obsidian-cli list /path/to/vault wiki/
# Read a note
obsidian-cli read /path/to/vault wiki/index.md
# Create or update a note
obsidian-cli write /path/to/vault wiki/new-note.md < content.md
# Search notes by content
obsidian-cli search /path/to/vault "query term"
```
**Why prefer this**:
- No plugin install required (CLI is built into Obsidian)
- No MCP server process to manage
- No TLS certificate bypass needed
- Survives Obsidian restarts (no persistent connection)
- Works identically across desktop and headless environments
**When to use Options A/B/C instead**: If you need persistent semantic search, frontmatter patching, or are on Obsidian < v1.12.
The `kepano/obsidian-skills` repo includes an `obsidian-cli` skill that wraps these commands as reusable patterns. Install it alongside this plugin for first-class CLI support.
---
## Use `--scope user`
Both MCP options use `--scope user` so the vault is available across all Claude Code projects, not just the one where you ran the command.
---
## Verification
After setup:
```bash
claude mcp list # confirm the server appears
claude mcp get obsidian-vault # confirm the path or URL is correct
```
In a Claude Code session, type `/mcp` to check connection status.
Then test: "List all notes in my wiki folder."
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |