The short answer
- 1Download Skillry .mcpb, then select it in Settings → Desktop app → Extensions → Manage → Advanced settings → Install Extension…. Check the tools under + → Connectors.
- 2If you already added Skillry manually, remove only its entry from
claude_desktop_config.jsonbefore enabling the extension. Keep other servers. Downloading a file does not confirm a connection. - 3Claude Desktop supplies Node.js 22+; no separate Node.js installation is needed for the extension. Manual configuration below requires Node.js 22+ and npx.
Install the Skillry desktop extension
Download Skillry .mcpb, then select it in Settings → Desktop app → Extensions → Manage → Advanced settings → Install Extension…. Check the tools under + → Connectors.
Claude Desktop supplies Node.js 22+; no separate Node.js installation is needed for the extension. Manual configuration below requires Node.js 22+ and npx.
If you already added Skillry manually, remove only its entry from claude_desktop_config.json before enabling the extension. Keep other servers. Downloading a file does not confirm a connection.
Before you start
Menu names checked on 30 October 2026 against Claude Desktop 4.4212 and the Claude Help Center. The full setup has not yet been run end to end; if a step differs on your machine, use Report an issue at the bottom.
- Claude Desktop on macOS or Windows, updated: Claude menu → Check for Updates….
- Claude Desktop supplies Node.js 22+; no separate Node.js installation is needed for the extension. Manual configuration below requires Node.js 22+ and npx.
Download Skillry .mcpb, then select it in Settings → Desktop app → Extensions → Manage → Advanced settings → Install Extension…. Check the tools under + → Connectors.
| System | Config file |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
Manual configuration (alternative)
- 1
In Claude Desktop’s menu, choose Help → Troubleshooting → Enable Developer Mode…, then Enable. Skip this step if you already see a Developer menu.
You should see: A Developer menu next to the others.
- 2
Choose Developer → Open App Config File.
You should see:
claude_desktop_config.jsonopens in your default editor. Claude Desktop creates the file if it does not exist. - 3
Merge this into the
mcpServersobject, keeping any servers already there. If the file has nomcpServersyet, add it as shown.macOS { "mcpServers": { "skillry": { "command": "npx", "args": [ "--yes", "skillry-cli@latest", "mcp" ] } } } - 4
On Windows use this entry instead.
Windows { "mcpServers": { "skillry": { "command": "cmd", "args": [ "/c", "npx", "--yes", "skillry-cli@latest", "mcp" ] } } } - 5
Save the file, then choose Developer → Reload MCP Configuration.
You should see:
skillryunder Connectors, as in the next section.If Skillry does not appear, quit Claude Desktop completely and open it again: on macOS use Quit from the Claude menu (⌘Q), on Windows exit from the tray icon.
Check that Claude Desktop is connected
- 1
In a conversation, select + in the message box, then Connectors.
You should see:
skillryin the list with its tools, starting withsearch_skills. - 2
For its status, open Settings → Desktop app, select Manage next to Extensions and look under Local MCP servers (in the older settings layout: Settings → Developer). Developer → Open MCP Log File opens the log.
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 Claude Desktop 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 Claude Desktop can’t see Skillry
| What you see | Likely cause | What to do |
|---|---|---|
| There is no Developer menu | Developer Mode is off | Choose Help → Troubleshooting → Enable Developer Mode…. Or open the file directly at the path in Before you start. |
| Nothing under Connectors after reloading | A JSON error in the file, or the app has not reloaded it | Validate the JSON (no trailing commas, skillry inside mcpServers), choose Developer → Reload MCP Configuration, or quit and reopen the app. Developer → Open MCP Log File names the problem. |
| Windows: the entry is in the file but Skillry never loads | The Windows installer packages Claude Desktop as MSIX, and the app can read a packaged copy of the file instead | Merge the same entry into %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\claude_desktop_config.json, then quit and reopen the app. |
mcp-server-skillry.log says npx was not found | Node.js is not installed, or the app cannot see it | Install the LTS build from nodejs.org, then quit and reopen Claude Desktop. |
Windows: the log mentions ${APPDATA} in a path | npm is not installed globally for the app’s environment | Add "env": { "APPDATA": "C:\\Users\\<you>\\AppData\\Roaming\\" } to the entry and run npm install -g npm once, then reopen the app. |
| 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
To remove the extension, disable or uninstall Skillry in Extensions. For manual setup, remove only the skillry configuration entry.
- 1
Delete the
skillryentry fromclaude_desktop_config.json, save, then choose Developer → Reload MCP Configuration.You should see:
skillrygone from Connectors.
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
| Item | macOS | Windows |
|---|---|---|
| Config file | ~/Library/Application Support/Claude/claude_desktop_config.json | %APPDATA%\Claude\claude_desktop_config.json |
| Open it | Developer → Open App Config File | same |
| Apply changes | Developer → Reload MCP Configuration | same |
| Logs | ~/Library/Logs/Claude/mcp*.log | %APPDATA%\Claude\logs |
| Launch command | npx --yes skillry-cli@latest mcp | cmd /c npx --yes skillry-cli@latest mcp |
| Check | + → Connectors | same |
{
"mcpServers": {
"skillry": {
"command": "npx",
"args": [
"--yes",
"skillry-cli@latest",
"mcp"
]
}
}
}The config file format is described in the Model Context Protocol documentation; its screenshots show an older settings window with an Edit Config button that current versions no longer have.
Common questions
Is there a one-click install?
Download Skillry .mcpb, then select it in Settings → Desktop app → Extensions → Manage → Advanced settings → Install Extension…. Check the tools under + → Connectors.
Where did Edit Config go?
Current versions of Claude Desktop open the file from Developer → Open App Config File, after Help → Troubleshooting → Enable Developer Mode….
Do I need Node.js?
Claude Desktop supplies Node.js 22+; no separate Node.js installation is needed for the extension. Manual configuration below requires Node.js 22+ and npx.
Can I use the same entry in Claude Code?
The JSON is the same, but Claude Code reads ~/.claude.json. Follow the Claude Code page to add it there.
Sources
Did this guide help?
