One place for Claude Code-related setup.

Stop losing time to scattered rules, MCP config, and “skills” folders. Give your team a single, honest view inside VS Code.

After you install: In VS Code, use the Activity Bar (icons on the far left) → click Cloude Code ToolBox → in the Side Bar click MCP & skills. That opens the hub (Intelligence, MCP, Skills, Workspace). Reload the window if you don’t see the icon yet.
In plain terms: Claude Code in VS Code only works as well as the setup around it—but that setup is usually scattered across files, machines, and habits. Cloude Code ToolBox is one dedicated toolbox in VS Code: see what’s configured, standardize how teams adopt Claude Code (including from Cursor and optional GitHub Copilot migration steps), and build explicit context while each developer still chooses what to share.
VS Code: Activity Bar Cloude Code ToolBox icon and Side Bar MCP & skills. Click to view fullscreen.
Cloude Code ToolBox hub: Intelligence tab with Cursor to VS Code and Claude Code bridges. Click to view fullscreen.

For engineering teams

Faster path from Cursor to Claude Code

Guided actions to port connections (MCP), rules, and scaffold a memory bank—without memorizing file formats.

Discover and add from one hub

Browse MCP registry and skills catalogs, see what’s installed, fewer raw JSON edits by hand.

One checklist view

Workspace vs personal setup, local skill folders, rules, CLAUDE.md, memory bank—aligned with what you shipped.

Smarter context for Claude Code

Context packs and readiness flows with explicit choices so teams agree on what Claude Code is allowed to see.

One Click Setup & Thinking Machine Mode

Two highlighted controls on the Intelligence tab turn messy, one-off Claude Code setup into something your team can repeat and reason about.

One Click Setup

What it does: After you confirm you understand the risk, it runs the sequence you configured in Settings — typically migration tracks for Cursor → Claude Code and optional GitHub Copilot → Claude Code: port Cursor MCP into VS Code mcp.json, Claude-oriented memory bank init, Cursor rules into CLAUDE.md, optional .cursorrules merge, skills migration, MCP & Skills awareness (under .claude/) with optional merge into CLAUDE.md, readiness summary, config scan, and follow-ups. Bridges use the bundled Node CLIs shipped with the extension (no npx fetch).

Why it matters: Onboarding and “make this repo Claude-ready” shouldn’t depend on who remembers which README or which CLI flag. One Click encodes your team’s playbook once, then anyone can execute the same steps and review the same terminals and files.

Thinking Machine Mode

What it does: A master switch for session priming — optional MCP & Skills awareness (writes under .claude/) plus optional merge into CLAUDE.md, and a context pack for Claude Code, with settings for confirmations and defaults. The first time you enable it, VS Code asks you to Engage (or cancel to turn the mode off again). Turning the mode off clears that acknowledgment so the next enable shows the dialog again.

Why it matters: Claude Code works best when sessions start from accurate, explicit context — what MCP servers exist, where skills live, and a structured snapshot of the workspace — not from guesswork. Thinking Machine Mode makes that priming a deliberate, repeatable gesture instead of a forgotten manual step.

Ready in the Marketplace

In the Marketplace, search for Cloude Code ToolBox (MCP, Skills, Cursor/Copilot → Claude) or use the buttons below. After install, open Cloude Code ToolBox in the activity bar, then MCP & skills.

Install in VS Code

VS Code did not open? Open the Marketplace in your browser instead.

code --install-extension amitchorasiya.cloude-code-toolbox-vscode