Files
Shutong Wu 7bbc83ba5c docs(website): pull real wiki content into guides + architecture
Replaces AI-skeleton content with the actual CoplayDev/unity-mcp.wiki
pages so the docs site has the real install/repair/troubleshooting
material people have been linking to.

Wiki pages absorbed:
- 1.-Fix-Unity-MCP-and-Cursor,-VSCode,-Windsurf,-Rider → new
  /guides/uv-setup page. Covers Python 3.12+ install, uv install on
  macOS/Linux/Windows, common uv locations, the MCP for Unity window's
  "Choose UV Install Location" + "Repair Python Env" buttons, where
  the server lives per OS, macOS PATH gotchas. Replaces the shallow
  /guides/cursor page (deleted) — the cursor-specific Windows uv path
  fix moved into the new troubleshooting FAQ.

- 2.-Fix-Unity-MCP-and-Claude-Code → new /guides/claude-code-cli page.
  Native installer + NVM + Homebrew Node paths, macOS PATH workaround.

- 3.-Common-Setup-Problems → new /guides/troubleshooting page. macOS
  dyld ICU error, WSL2-to-Windows bridging (@aollivier82 contribution
  with port-proxy + firewall + WSL host IP discovery), Unity AI
  Assistant DLL conflict (@rkroska report), Claude Code / VS Code /
  Cursor FAQs.

- Project-Roadmap (wiki) → new /architecture/project-roadmap page.
  Distinct from the existing /architecture/roadmap (2026 deep-research
  feature plan). This is the living high-level roadmap with Current
  Focus / Mid-Term / Long-Term / Icebox / Recently Completed sections
  the wiki maintains.

Sidebar reorganized: Guides now leads with the install/setup pages
(uv-setup, claude-code-cli, client-configurators), then capability
(multi-instance, tool-groups, cli, cli-examples), then advanced
(custom-tools, remote-server-auth, roslyn), then troubleshooting last.

Verified: npm run build clean. One broken-anchor fix landed for the
em-dash heading "FAQ — Claude Code" which slugifies to faq--claude-code
(double dash).
2026-05-24 18:23:46 +08:00

1.9 KiB

id, slug, title, sidebar_label, description
id slug title sidebar_label description
claude-code-cli /guides/claude-code-cli Install or Repair Claude Code CLI Claude Code CLI Install or repair the Claude Code CLI (claude) so MCP for Unity can launch it.

Install or Repair Claude Code CLI

You need the Claude Code CLI (claude) available on your system.

:::caution Switching transport requires a restart If you change from http to stdio (or vice versa) in the MCP for Unity window, restart Claude Code for it to pick up the change. :::

macOS / Linux / WSL:

curl -fsSL https://claude.ai/install.sh | bash
claude doctor

Windows PowerShell:

irm https://claude.ai/install.ps1 | iex
claude doctor

Alternative: npm via NVM (installs under ~/.nvm)

# Install / select a Node version
nvm install v21.7.1
nvm use v21.7.1

# Install Claude Code CLI into this Node's global prefix
npm install -g @anthropic-ai/claude-code

# Verify it's under NVM
which claude
claude --version

Alternative: npm with system / Homebrew Node

# If you don't have Node yet (macOS):
brew install node

# Install Claude Code CLI globally
npm install -g @anthropic-ai/claude-code

# Verify it's on PATH (typical: /opt/homebrew/bin/claude or /usr/local/bin/claude)
which claude
claude --version

macOS PATH gotcha

On macOS, Unity launched from Finder / Hub may not inherit your shell PATH. If claude isn't found:

  • Either launch Hub from Terminal (so PATH propagates),
  • or use the MCP for Unity window's "Choose Claude Install Location" to set the absolute path.