craftdesk MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

Install from GitHub URL or git repo (auto URL normalization)
Monorepo subdirectory + single-file support
Recursive dependency resolution
craftdesk.json + lockfile for reproducibility
Multi-agent sync: Claude Code, Cursor, Windsurf, Continue.dev
Checksum verification for integrity
Embedded (local-to-repo) skills supported
Collections for bundled crafts

Démo en direct

Aperçu en pratique

craftdesk-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": {
    "craftdesk-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/mensfeld/craftdesk",
        "~/.claude/skills/craftdesk"
      ],
      "_inferred": true
    }
  }
}

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

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

{
  "mcpServers": {
    "craftdesk-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/mensfeld/craftdesk",
        "~/.claude/skills/craftdesk"
      ],
      "_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": {
    "craftdesk-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/mensfeld/craftdesk",
        "~/.claude/skills/craftdesk"
      ],
      "_inferred": true
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

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

~/.continue/config.json

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

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json

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

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

claude mcp add craftdesk-skill -- git clone https://github.com/mensfeld/craftdesk ~/.claude/skills/craftdesk

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

Cas d'usage

Usages concrets : craftdesk

Manage a team-standard skill set across multiple developers

👤 Platform teams standardizing AI tooling ⏱ ~30 min intermediate

Quand l'utiliser : Team members each pick different skills; you want everyone on the same set.

Prérequis

CraftDesk installed — git clone https://github.com/mensfeld/craftdesk ~/.claude/skills/craftdesk or npm install -g craftdesk (per project)

Déroulement

Init a project manifest

craftdesk init — set up craftdesk.json for this repo.✓ Copié

→ craftdesk.json created
Add skills

craftdesk add planning-with-files agent-skill-tdd swing-skills — pin versions.✓ Copié

→ Manifest updated, lockfile written
Team installs

Teammate runs craftdesk install on clone.✓ Copié

→ Same skills and versions land on their machine

Résultat : A reproducible skill environment like a package.json for AI.

Pièges

Committing secrets from embedded skills — Embedded skills shouldn't carry creds — keep those in env

Combiner avec : filesystem · github

Sync skills across Claude Code, Cursor, and Windsurf

👤 Developers using multiple agents ⏱ ~10 min beginner

Quand l'utiliser : You install a skill in Claude Code and want it in Cursor too.

Déroulement

Sync

craftdesk sync — make all installed crafts available to all my agents.✓ Copié

→ Per-agent install paths populated
Verify

craftdesk verify — any drift?✓ Copié

→ Green across agents

Résultat : Consistent tooling no matter which agent you open.

Publish an internal craft to a private registry

👤 Teams with proprietary skills ⏱ ~20 min intermediate

Quand l'utiliser : You built a skill for internal processes and want it installable by craftdesk add.

Déroulement

Publish

craftdesk publish — push this craft to our registry.✓ Copié

→ Published with version

Résultat : An internal library of crafts versioned like any code dependency.

Combiner avec : github

Combinaisons

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

craftdesk-skill + github

Install crafts directly from GitHub URLs

craftdesk add https://github.com/org/skill✓ Copié

craftdesk-skill + filesystem

Embedded skills under ./skills/ get picked up automatically

Create an embedded skill at ./skills/custom-review and run craftdesk sync.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler
craftdesk init	none	Start of a new project
craftdesk install	(reads craftdesk.json + lockfile)	After clone / pull
craftdesk add	name or URL	Add a dependency
craftdesk list	none	Inventory check
craftdesk sync	none	After install or update
craftdesk publish	craft path	Internal release
craftdesk verify	none	Sanity check

Coût et limites

Coût d'exécution

Quota d'API: None
Tokens par appel: Minimal — CraftDesk is CLI-driven
Monétaire: Free
Astuce: Use the lockfile — avoids re-resolving on every install

Sécurité

Permissions, secrets, portée

Stockage des identifiants : Registry tokens in env if publishing privately

Sortie de données : Only to git hosts you install from + any configured registry

CraftDesk installs arbitrary code from URLs — pair with repo-forensics before adding unknown crafts.

Dépannage

Erreurs courantes et correctifs

Install fails with checksum mismatch

Upstream changed; pin to a commit sha or reconcile the lockfile deliberately

craftdesk sync misses one agent

Confirm the agent path exists and is writable; see craftdesk config

Alternatives

craftdesk vs autres

Alternative	Quand l'utiliser	Compromis
Manual git clone into skills dir	Single machine, no team	No pinning, no sync
gsd-skill-creator	You want skills authored for you, not managed	Different problem

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills