Claude-Code-Game-Studios MCP — ユースケース, インストール & ライブデモ

なぜ使うのか

主な機能

49 role-specific agents (designer, gameplay programmer, level designer, audio, …)
72 workflow skills (sprint plan, retro, playtest, bug triage)
Engine-agnostic — wraps your tool of choice
Sprint cadence templates (1-week / 2-week)
MIT licensed

ライブデモ

実際の動作

準備完了

インストール

クライアントを選択

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "game-studios-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/Donchitos/Claude-Code-Game-Studios",
        "~/.claude/skills/Claude-Code-Game-Studios"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config を開く。保存後、アプリを再起動。

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

{
  "mcpServers": {
    "game-studios-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/Donchitos/Claude-Code-Game-Studios",
        "~/.claude/skills/Claude-Code-Game-Studios"
      ],
      "_inferred": true
    }
  }
}

Cursor は Claude Desktop と同じ mcpServers スキーマを使用。プロジェクト設定はグローバルより優先。

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "game-studios-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/Donchitos/Claude-Code-Game-Studios",
        "~/.claude/skills/Claude-Code-Game-Studios"
      ],
      "_inferred": true
    }
  }
}

Cline サイドバーの MCP Servers アイコンをクリックし、"Edit Configuration" を選択。

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "game-studios-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/Donchitos/Claude-Code-Game-Studios",
        "~/.claude/skills/Claude-Code-Game-Studios"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop と同じ形式。Windsurf を再起動して反映。

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "game-studios-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/Donchitos/Claude-Code-Game-Studios",
        "~/.claude/skills/Claude-Code-Game-Studios"
      ]
    }
  ]
}

Continue はマップではなくサーバーオブジェクトの配列を使用。

~/.config/zed/settings.json

{
  "context_servers": {
    "game-studios-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/Donchitos/Claude-Code-Game-Studios",
          "~/.claude/skills/Claude-Code-Game-Studios"
        ]
      }
    }
  }
}

context_servers に追加。保存時に Zed がホットリロード。

claude mcp add game-studios-skill -- git clone https://github.com/Donchitos/Claude-Code-Game-Studios ~/.claude/skills/Claude-Code-Game-Studios

ワンライナー。claude mcp list で確認、claude mcp remove で削除。

ユースケース

実用的な使い方： Claude-Code-Game-Studios

Run a 1-week sprint on your indie game

👤 Solo / 2-person indie teams ⏱ ~45 min intermediate

使うタイミング： You're making a game solo and discipline is what's failing, not ideas.

前提条件

Skill installed — git clone https://github.com/Donchitos/Claude-Code-Game-Studios ~/.claude/skills/game-studios
GDD or design brief — Even a rough design doc is enough to anchor

フロー

Plan

Use game-studios. I'm solo-devving a platformer in Godot. Plan this week's sprint — here's the GDD: <brief>✓ コピーしました

→ Sprint with tasks in role buckets (design/code/art/audio), sized
Daily standup

What should I do today to hit the sprint goal? What can slip?✓ コピーしました

→ Prioritized day plan with slip allowance
Retro

Sprint done. What slipped? What to carry over? What to change next sprint?✓ コピーしました

→ Honest retro with specific improvements

結果： A game in motion with cadence you can sustain.

注意点

Over-planning for a solo dev — Use the 1-week cadence, skip the enterprise workflows

組み合わせ： filesystem

Run a structured playtest and synthesize feedback

👤 Indie devs pre-Early-Access ⏱ ~60 min intermediate

使うタイミング： You just ran 5 playtests and have 5 video recordings + notes to make sense of.

前提条件

Playtest artifacts — Notes, timestamps, transcripts in /playtests/

フロー

Ingest

Use game-studios/playtest. Ingest /playtests/session-*/ and tag feedback by type (bug, UX, mechanic, audio).✓ コピーしました

→ Tagged feedback inventory
Cluster

Cluster by feedback theme. What came up across multiple sessions?✓ コピーしました

→ Cross-session patterns, not per-person complaints
Prioritize

For each theme: frequency, severity, effort to fix. Feed into next sprint.✓ コピーしました

→ Prioritized changes ready to plan

結果： Next sprint's work driven by real player data, not hunches.

注意点

Treating one playtester's strong opinion as general — Theme needs to appear in ≥2 sessions to qualify

組み合わせ

他のMCPと組み合わせて10倍の力を

game-studios-skill + filesystem

Keep the whole studio context in /studio/ folder

Organize /studio/sprints/, /studio/playtests/, /studio/retros/.✓ コピーしました

game-studios-skill + github

Issues per task, milestones per sprint

Create GitHub issues from the sprint plan; make a milestone for this sprint.✓ コピーしました

ツール

このMCPが提供する機能

ツール	入力	呼び出すタイミング
sprint_plan	brief, duration	Start of each sprint
role_review	role, artifact	Gut-check before shipping
playtest_synthesize	sessions[]	After playtests
retro	sprint_notes	End of each sprint

コストと制限

運用コスト

APIクォータ: N/A
呼び出しあたりのトークン: Plans are cheap; role-review of big artifacts (levels, art) can be expensive
金額: Free (MIT)
ヒント: Don't ask every role to review every artifact — pick who's relevant

セキュリティ

権限、シークレット、影響範囲

認証情報の保管： None

データ送信先： None

トラブルシューティング

よくあるエラーと対処法

Plans feel AAA-studio, not indie

Pin your scope explicitly: "solo dev, 1 hour/day, 3 month timeline"

Role advice conflicts

That's realistic — pick the one that serves the next milestone

Skill doesn't know Godot specifics

Prepend Godot docs or relevant GDScript examples; it's engine-agnostic by default

代替案

Claude-Code-Game-Studios 他との比較

代替案	代わりに使う場面	トレードオフ
Notion / Trello board	You want project management without LLM synthesis	No playtest synthesis, no role critique
game-specific communities	You want human feedback on design	Slow, and people are biased by their own games

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

🔍 400以上のMCPサーバーとSkillsを見る