Faster path from Cursor or Claude Code to Copilot
Guided actions to port MCP, sync rules or CLAUDE.md, merge project .mcp.json, migrate skill folders, and scaffold a memory bank—without memorizing file formats.
Copilot Toolbox
Github Copilot ToolBox (MCP, Skills, Cursor/Claude → Copilot)
Stop losing time to scattered rules, MCP config, and “skills” folders. Give your team a single, honest hub in VS Code or JetBrains IDEs (same MCP & skills UI).
After you install: In VS Code, use the Activity Bar (icons on the
far left) → click Copilot Toolbox (outline brain icon — twin lobes, matches default Activity Bar scale) → in the Side Bar click
MCP & skills. That opens the hub (Intelligence, MCP, Skills, Workspace, Awesomeness). The Awesomeness tab is for Awesome Copilot — copy a Copilot Chat prompt, register the CLI plugin marketplace, and open the catalog site (the extension does not mirror the catalog). If you use the secondary sidebar beside Chat, that view’s title is also Copilot Toolbox. The hub’s main tabs use emoji labels and a distinct color per section. Reload the window
if you don’t see the icon yet.
One Click & Copilot CLI: From Intelligence, One Click Setup can run both migration tracks (Cursor and Claude Code), then follow-ups including optional Copilot CLI + Chat User settings and
npm install -g @github/copilot (terminal prints npm bin -g for PATH — PowerShell on Windows). You can skip Copilot CLI + Chat for this run only in the confirmation modal. In Chat, Local vs Copilot CLI is the session type in the footer or command palette — not the # Toolbox context chip.
Claude Code (Anthropic): This extension migrates repo files toward Copilot; it does not sign you in to Anthropic’s Claude Code extension or CLI — those still use their own login when prompted.
JetBrains (IntelliJ IDEA, etc.): Install Github Copilot ToolBox from the
JetBrains Marketplace
(plugin id
com.amitchorasiya.github.copilot.toolbox) or build from the
monorepo with npm run package:intellij and Install Plugin from Disk…. The plugin embeds the same hub (MCP & skills) in a tool window via JCEF. Details:
github-copilot-toolbox-intellij/README.md.
This page: Light / Dark in the header remembers your choice in this browser only (not on our servers).
In plain terms: Copilot only works as well as the setup around it—but that setup is
usually scattered across files, machines, and habits.
Github Copilot ToolBox (MCP, Skills, Cursor/Claude → Copilot) is one dedicated Copilot Toolbox in VS Code: see
what’s configured, standardize how teams move to Copilot (including from Cursor), and give Chat better
context while each developer still chooses what to share.
For engineering teams
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, instructions, memory bank—aligned with what you shipped.
Smarter context for Chat
Context packs and readiness flows with explicit choices so teams agree on what Copilot is allowed to see.
One Click Setup & Thinking Machine Mode
Two highlighted controls on the Intelligence tab turn messy, one-off Copilot 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. By default both tracks are on: Cursor → Copilot (MCP port, rules, optional .cursorrules, .cursor/skills → .agents/skills) and Claude Code → Copilot (CLAUDE.md → copilot-instructions.md, .claude/skills → .agents/skills, workspace .mcp.json → VS Code mcp.json). Then memory bank init, MCP & Skills awareness scan, readiness, config scan, optional Copilot Chat toggles (including Claude cloud agent and Copilot CLI + Chat User settings), optional global npm install -g @github/copilot with npm bin -g printed for PATH, and best-effort New Copilot CLI Session. The modal can skip Copilot CLI + Chat for that run only. Cursor bridge CLIs use the
bundled Node CLIs (no npx fetch).
Why it matters: Onboarding and “make this repo Copilot-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 .github/) plus a
context pack copied for Copilot Chat, 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: Copilot works best when Chat starts 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.
What you get in VS Code
JetBrains: the same hub ships in the plugin’s tool window. First (VS Code): after install, open Copilot Toolbox in the Activity Bar (left edge), then MCP & skills in the Side Bar—that is the hub. Below: access walkthrough, then high-resolution hub captures. Click any image for fullscreen.
Ready in the Marketplaces
VS Code: install the extension, then open Copilot Toolbox in the activity bar → MCP & skills. JetBrains: install from the Marketplace, then View → Tool Windows → Github Copilot ToolBox.
VS Code — Github Copilot ToolBox JetBrains — Github Copilot ToolBox
VS Code did not open? Open the VS Code Marketplace in your browser. JetBrains: open Marketplace search.
code --install-extension amitchorasiya.github-copilot-toolbox