obsidian-plugin-skill MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

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

Démo en direct

Aperçu en pratique

obsidian-plugin-skill.replay ▶ prêt

0/0

Installer

Choisissez votre client

~/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
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.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 utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

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

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "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
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.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 utilise un tableau d'objets serveur plutôt qu'une map.

~/.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"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : obsidian-plugin-skill

How to build and release your first Obsidian plugin

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

Quand l'utiliser : You have a concrete workflow improvement and want a plugin in a day.

Prérequis

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

Déroulement

Scaffold the plugin

Scaffold an Obsidian plugin called 'smart-outline' with a command and a settings tab.✓ Copié

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

Implement: on command, open a modal showing the outline of the active note.✓ Copié

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

Install into the dev vault's plugins folder and reload Obsidian.✓ Copié

→ Plugin shows up, command works
Prepare a release

Create versions.json and tag a v0.1.0 release.✓ Copié

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

Résultat : A working, installable plugin you can submit to the Community store.

Pièges

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

Combiner avec : filesystem · github

Add a proper settings tab to an existing plugin

👤 Existing plugin authors improving UX ⏱ ~30 min intermediate

Quand l'utiliser : Your plugin has grown and needs user-configurable options.

Déroulement

Design the settings

Based on my plugin's README, what settings should be user-configurable?✓ Copié

→ Short list with rationale
Implement PluginSettingTab

Add a PluginSettingTab with those controls.✓ Copié

→ Settings UI in Obsidian

Résultat : A settings tab users can actually use.

Pièges

Too many settings — Ruthlessly cut — unused settings are clutter

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

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.✓ Copié

obsidian-plugin-skill + github

Automate tagging and release creation

Tag v0.2.0 and publish release with the built assets.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler
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

Coût et limites

Coût d'exécution

Quota d'API: none
Tokens par appel: 5–20k per plugin
Monétaire: free
Astuce: Work feature-by-feature rather than dumping a full plugin spec on Claude

Sécurité

Permissions, secrets, portée

Stockage des identifiants : GitHub token for releases (if automating)

Sortie de données : none at skill layer

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

Dépannage

Erreurs courantes et correctifs

Obsidian doesn't load the plugin

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

Vérifier : cat .obsidian/plugins/my-plugin/manifest.json | jq .

Build produces no main.js

Run the esbuild command; check tsconfig target.

Vérifier : ls main.js

Alternatives

obsidian-plugin-skill vs autres

Alternative	Quand l'utiliser	Compromis
logseq	You're on Logseq rather than Obsidian	Different plugin API

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills