The short answer
- 1You need GitHub Copilot enabled in VS Code (the free tier is enough). Without it the MCP commands are not offered.
- 2Fastest: Add to VS Code on skillry.dev/mcp, or one
code --add-mcpcommand in a terminal. - 3Confirm with MCP: List Servers in the Command Palette:
skillryshould be running.
Before you start
The code --add-mcp route was tested on macOS with VS Code 1.141 on 28 October 2026. The other routes follow the official documentation and have not been run on a real installation yet.
- VS Code with GitHub Copilot signed in and AI features enabled. The free Copilot tier is enough.
- Node.js 22 or newer (
node --version). VS Code starts the server withnpx. - VS Code has two file formats: its own
mcp.jsonwith aserverskey, and the portable Copilot file~/.copilot/mcp-config.jsonwith anmcpServerskey. Either works; this page tells you which one each route writes.
| Route | Writes to | Good when |
|---|---|---|
| Add to VS Code link | Your user profile mcp.json | You are already on skillry.dev/mcp |
| MCP: Add Server in the Command Palette | ~/.copilot/mcp-config.json (Copilot Global) | You prefer clicking through VS Code |
code --add-mcp in a terminal | Your user profile mcp.json | You like one command |
Edit mcp.json yourself | Whichever file you open | You want to see the entry |
Add Skillry to VS Code
- 1
Open skillry.dev/mcp, choose VS Code and your operating system, then select Add to VS Code. Allow the browser to open VS Code.
- 2
VS Code shows the server name and command and asks you to confirm. Select Install.
You should see: The entry in your user
mcp.json, with a Start action above it. Select it, or wait for the server to start on first use.
- 1
Open the Command Palette (⇧⌘P on macOS, Ctrl+Shift+P on Windows) and run MCP: Add Server.
- 2
Choose Command (stdio) and enter the launch command:
npx --yes skillry-cli@latest mcpon macOS,cmd /c npx --yes skillry-cli@latest mcpon Windows. - 3
Enter
skillryas the server ID. - 4
Choose Global, then Copilot Global when prompted. This writes
~/.copilot/mcp-config.json.You should see: A trust prompt for the new server. Accept it to let VS Code start it.
- 1
Run this in a terminal. On Windows use PowerShell, where the single quotes work as written.
macOS code --add-mcp '{"name":"skillry","type":"stdio","command":"npx","args":["--yes","skillry-cli@latest","mcp"]}'You should see:
Added MCP servers: skillry. VS Code opens or comes to the front. - 2
On Windows, run this instead so Windows can start
npx:Windows (PowerShell) code --add-mcp '{"name":"skillry","type":"stdio","command":"cmd","args":["/c","npx","--yes","skillry-cli@latest","mcp"]}'
- 1
Run MCP: Open User Configuration from the Command Palette. It opens your user profile
mcp.json, creating it if needed. - 2
Merge this into the
serversobject, keeping any servers already there.macOS { "servers": { "skillry": { "type": "stdio", "command": "npx", "args": [ "--yes", "skillry-cli@latest", "mcp" ] } } } - 3
On Windows use this entry instead.
Windows { "servers": { "skillry": { "type": "stdio", "command": "cmd", "args": [ "/c", "npx", "--yes", "skillry-cli@latest", "mcp" ] } } } - 4
Save. VS Code shows Start above the entry; select it.
You should see: The server running in MCP: List Servers.
Check that VS Code is connected
- 1
Run MCP: List Servers from the Command Palette and select
skillry.You should see: A running server with actions such as Stop, Restart and Show Output. If it is stopped, select Start.
- 2
Open Chat, switch to Agent mode and open the tools picker.
You should see: The Skillry tools, starting with
search_skills, available to tick.
Try your first search
Searching needs no account, so this is the quickest way to prove the connection works.
- 1
Start a new conversation in Copilot Chat’s agent mode and paste this request.
Prompt your agent Use the Skillry MCP connected to https://skillry.dev to find three product presentation Skills. Show their preview links, required inputs, dependencies and external costs. Do not install or run anything.You should see: Three Skill candidates, each with a preview link, the inputs it needs, its dependencies and any outside costs. Nothing is installed.
- 2
If the agent answers that it has no Skillry tool, or the request hangs, go to It isn’t working.
If VS Code can’t see Skillry
| What you see | Likely cause | What to do |
|---|---|---|
| MCP: Add Server is not in the Command Palette | Copilot is not signed in or AI features are disabled | Sign in to GitHub and enable Copilot. The MCP commands appear once Chat is available. |
| The server is listed but stopped, or shows an error | It was never started, or npx failed | Select Start in MCP: List Servers, then Show Output to read the error. A missing npx means Node.js is not installed for the shell VS Code uses. |
| The tools never appear in Chat | Chat is not in Agent mode, or the tools are unticked | Switch to Agent mode, open the tools picker and tick the Skillry tools. |
| The server is listed but shows as failed, or never starts | npx is not installed, Node.js is older than 22, or the first start timed out while downloading the package | Run node --version and npx --version in a terminal. Then run npx --yes skillry-cli@latest mcp once by hand, wait for it to start, press Ctrl+C, and try the client again: the package is now cached. |
| On Windows the server exits as soon as it starts | The entry starts npx directly, and Windows needs a shell to run it | Use the Windows entry from this page: the command is cmd and the arguments start with /c, npx. |
| The browser page says the request is invalid or expired | The device code was approved too late, or belongs to an earlier attempt | Ask the agent to connect again and approve the new code within a few minutes. |
| Installing stops with a Premium or purchase message | The Skill is Premium and your account has neither a plan nor a purchase for it | Follow the link the agent shows to buy the Skill or subscribe, then ask again. Nothing is charged until you do. |
Remove or disconnect
- 1
Run MCP: List Servers, select
skillry, then Uninstall; or delete the entry from the file that holds it.You should see:
skillrygone from the list.
Removing the entry does not sign you out of Skillry. To revoke the stored approval as well, ask the agent to disconnect your Skillry account first, or remove the entry and let the approval expire after 7 days.
Reference
| File | macOS | Windows |
|---|---|---|
User profile mcp.json (servers key) | ~/Library/Application Support/Code/User/mcp.json | %APPDATA%\Code\User\mcp.json |
Copilot file (mcpServers key) | ~/.copilot/mcp-config.json | %USERPROFILE%\.copilot\mcp-config.json |
| Workspace file | .vscode/mcp.json in the project | same |
| Launch command | npx --yes skillry-cli@latest mcp | cmd /c npx --yes skillry-cli@latest mcp |
{
"servers": {
"skillry": {
"type": "stdio",
"command": "npx",
"args": [
"--yes",
"skillry-cli@latest",
"mcp"
]
}
}
}Every field, the install URL format and the two file formats are in the MCP configuration reference.
Common questions
Do I need Copilot?
Yes. VS Code’s MCP support lives in Copilot Chat’s agent mode. The free Copilot tier is enough.
Which file should I use?
Any one of them. The link and code --add-mcp write the user profile mcp.json; MCP: Add Server writes the Copilot file. Do not add Skillry to both.
Can I share it with my team?
Put the entry in .vscode/mcp.json in the repository (servers format). Teammates get a trust prompt the first time VS Code starts it.
Sources
Did this guide help?
