craftdesk MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

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

라이브 데모

실제 사용 모습

craftdesk-skill.replay ▶ 준비됨

0/0

설치

클라이언트 선택

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

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

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

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

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

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

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

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

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

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

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

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

context_servers에 추가. 저장 시 Zed가 핫 리로드.

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

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: craftdesk

Manage a team-standard skill set across multiple developers

👤 Platform teams standardizing AI tooling ⏱ ~30 min intermediate

언제 쓸까: Team members each pick different skills; you want everyone on the same set.

사전 조건

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

흐름

Init a project manifest

craftdesk init — set up craftdesk.json for this repo.✓ 복사됨

→ craftdesk.json created
Add skills

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

→ Manifest updated, lockfile written
Team installs

Teammate runs craftdesk install on clone.✓ 복사됨

→ Same skills and versions land on their machine

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

함정

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

함께 쓰기: filesystem · github

Sync skills across Claude Code, Cursor, and Windsurf

👤 Developers using multiple agents ⏱ ~10 min beginner

언제 쓸까: You install a skill in Claude Code and want it in Cursor too.

흐름

Sync

craftdesk sync — make all installed crafts available to all my agents.✓ 복사됨

→ Per-agent install paths populated
Verify

craftdesk verify — any drift?✓ 복사됨

→ Green across agents

결과: Consistent tooling no matter which agent you open.

Publish an internal craft to a private registry

👤 Teams with proprietary skills ⏱ ~20 min intermediate

언제 쓸까: You built a skill for internal processes and want it installable by craftdesk add.

흐름

Publish

craftdesk publish — push this craft to our registry.✓ 복사됨

→ Published with version

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

함께 쓰기: github

조합

다른 MCP와 조합해 10배 효율

craftdesk-skill + github

Install crafts directly from GitHub URLs

craftdesk add https://github.com/org/skill✓ 복사됨

craftdesk-skill + filesystem

Embedded skills under ./skills/ get picked up automatically

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

도구

이 MCP가 노출하는 것

도구	입력	언제 호출
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

비용 및 제한

운영 비용

API 쿼터: None
호출당 토큰: Minimal — CraftDesk is CLI-driven
금액: Free
팁: Use the lockfile — avoids re-resolving on every install

보안

권한, 시크릿, 파급범위

자격 증명 저장: Registry tokens in env if publishing privately

데이터 외부 송신: Only to git hosts you install from + any configured registry

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

문제 해결

자주 발생하는 오류와 해결

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

대안

craftdesk 다른 것과 비교

대안	언제 쓰나	단점/장점
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

craftdesk