craftdesk MCP — Casos de uso, Instalar & Demo ao vivo

Por que usar

Principais recursos

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

Demo ao vivo

Como fica na prática

craftdesk-skill.replay ▶ pronto

0/0

Instalar

Escolha seu cliente

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

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

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

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

Cursor usa o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a global.

VS Code → Cline → MCP Servers → Edit

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

Clique no ícone MCP Servers na barra lateral do Cline, depois "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Mesmo formato do Claude Desktop. Reinicie o Windsurf para aplicar.

~/.continue/config.json

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

O Continue usa um array de objetos de servidor em vez de um map.

~/.config/zed/settings.json

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

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

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

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do mundo real: craftdesk

Manage a team-standard skill set across multiple developers

👤 Platform teams standardizing AI tooling ⏱ ~30 min intermediate

Quando usar: Team members each pick different skills; you want everyone on the same set.

Pré-requisitos

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

Fluxo

Init a project manifest

craftdesk init — set up craftdesk.json for this repo.✓ Copiado

→ craftdesk.json created
Add skills

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

→ Manifest updated, lockfile written
Team installs

Teammate runs craftdesk install on clone.✓ Copiado

→ Same skills and versions land on their machine

Resultado: A reproducible skill environment like a package.json for AI.

Armadilhas

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

Combine com: filesystem · github

Sync skills across Claude Code, Cursor, and Windsurf

👤 Developers using multiple agents ⏱ ~10 min beginner

Quando usar: You install a skill in Claude Code and want it in Cursor too.

Fluxo

Sync

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

→ Per-agent install paths populated
Verify

craftdesk verify — any drift?✓ Copiado

→ Green across agents

Resultado: Consistent tooling no matter which agent you open.

Publish an internal craft to a private registry

👤 Teams with proprietary skills ⏱ ~20 min intermediate

Quando usar: You built a skill for internal processes and want it installable by craftdesk add.

Fluxo

Publish

craftdesk publish — push this craft to our registry.✓ Copiado

→ Published with version

Resultado: An internal library of crafts versioned like any code dependency.

Combine com: github

Combinações

Combine com outros MCPs para 10× de alavancagem

craftdesk-skill + github

Install crafts directly from GitHub URLs

craftdesk add https://github.com/org/skill✓ Copiado

craftdesk-skill + filesystem

Embedded skills under ./skills/ get picked up automatically

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

Ferramentas

O que este MCP expõe

Ferramenta	Entradas	Quando chamar
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

Custo e limites

O que custa rodar

Cota de API: None
Tokens por chamada: Minimal — CraftDesk is CLI-driven
Monetário: Free
Dica: Use the lockfile — avoids re-resolving on every install

Segurança

Permissões, segredos, alcance

Armazenamento de credenciais: Registry tokens in env if publishing privately

Saída de dados: Only to git hosts you install from + any configured registry

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

Solução de problemas

Erros comuns e correções

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

Alternativas

craftdesk vs. outros

Alternativa	Quando usar	Troca
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

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills