Connect Skillry MCP in Claude Code (macOS and Windows)

The short answer

1Run claude mcp add --scope user --transport stdio skillry -- npx --yes skillry-cli@latest mcp once in any terminal. Without --scope user the server exists only in the folder you ran it from.
2Confirm with claude mcp get skillry. The status line should read ✔ Connected.
3The entry lives in ~/.claude.json (Windows: %USERPROFILE%\.claude.json). You can also paste the JSON there by hand.

Start here:Add it Check it Authorize It isn’t working

Before you start

Tested on macOS with Claude Code 2.1.296 on 28 October 2026. The Windows command follows the official documentation and has not been run on a real machine yet.

Claude Code installed and signed in. claude --version should print a 2.x version.
Node.js 22 or newer (node --version). Claude Code starts the server with npx, which ships with Node.
Nothing to download from Skillry: npx fetches the package the first time the server starts.

Claude Code stores a server at one of three scopes. This guide uses user scope, so Skillry is there in every project.

Scope	Flag	Stored in	Use it when
User	`--scope user`	`~/.claude.json`, top level	You want Skillry in every project. This guide.
Local (default)	none	`~/.claude.json`, under the current project’s path	You want it in this folder only.
Project	`--scope project`	`.mcp.json` in the repository	You want teammates to get it from the repo. Each of them approves it on first run.

Add Skillry to Claude Code

Fastest. Works in any shell, including PowerShell and Command Prompt

1
Open a terminal in any folder and run:
macOS
```
claude mcp add --scope user --transport stdio skillry -- npx --yes skillry-cli@latest mcp
```
You should see: Added stdio MCP server skillry with command: npx --yes skillry-cli@latest mcp to user config, then File modified: ~/.claude.json.
2
On Windows, run this instead. The cmd /c wrapper lets Windows start npx, which is a script rather than a program.
Windows (PowerShell or Command Prompt)
```
claude mcp add --scope user --transport stdio skillry -- cmd /c npx --yes skillry-cli@latest mcp
```
3
Start a new Claude Code session, or type /mcp in one that is already open.
You should see: skillry in the /mcp list. Select it to see its 12 tools.

When you would rather manage the file yourself

1
Open ~/.claude.json in an editor. On Windows the file is %USERPROFILE%\.claude.json. Claude Code creates it the first time it runs.
2
Merge this into the top-level mcpServers object, keeping any servers already there.
macOS
```
{
  "mcpServers": {
    "skillry": {
      "command": "npx",
      "args": [
        "--yes",
        "skillry-cli@latest",
        "mcp"
      ]
    }
  }
}
```
Top level means next to the other keys at the root of the file. An entry under a project path only loads in that project.

On Windows use this entry instead.

Windows

{
  "mcpServers": {
    "skillry": {
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "--yes",
        "skillry-cli@latest",
        "mcp"
      ]
    }
  }
}

4
Save the file and start a new session.
You should see: skillry in the /mcp list.

Check that Claude Code is connected

1
In a terminal, run:
Terminal
```
claude mcp get skillry
```
You should see: Scope: User config (available in all your projects), Status: ✔ Connected, and the npx command you added.
2
To see every server with its health at once, run claude mcp list. Inside a session, /mcp shows the same list and lets you open a server’s tools.

The first check starts the server, and the first start downloads skillry-cli. Give it ten seconds or more. A ✘ Failed to connect that stays after that means Node or npx is missing; see below.

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 Code 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.

Authorize when you install

Installing checks your Skillry account. You do not type a password or paste a key into the agent: the first time, it opens a page in your browser and you approve it there.

1
Ask Claude Code to install the Skill you chose, for example Install it for this project.
You should see: The agent reports that it needs to connect your account and opens your browser. In a terminal client it may print the link instead; open it yourself.
2
Check that the device code on the page matches the one the agent shows, sign in to Skillry if asked, then select Approve.
You should see: Authorization approved, with a note to return to your agent. The agent notices within a few seconds and finishes the install.

The approval lasts 7 days and is stored in your operating system’s keyring (Keychain on macOS, Credential Manager on Windows). When it expires the agent simply asks you to approve again. To sign out early, ask the agent to disconnect your Skillry account.

If /mcp doesn’t list Skillry

What you see	Likely cause	What to do
`/mcp` does not list skillry	It was added at local scope in another folder, or the session started before you added it	Run `claude mcp get skillry`. If it says `Scope: Local config`, remove it and add it again with `--scope user`. If it says user scope, start a new session.
`claude mcp add` prints “was not saved”	Claude Code could not write `~/.claude.json`	Close other Claude Code sessions, check that the file is not read-only, and run the command again.
Connected on your Mac, failing on your Windows PC	The Windows entry starts `npx` without `cmd /c`	Run `claude mcp remove skillry -s user`, then add the Windows command from this page.
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
Remove the server from your user configuration:
Terminal
```
claude mcp remove skillry -s user
```
You should see: Removed MCP server skillry from user config.
2
To keep the server but switch it off for one project, toggle it in /mcp; Claude Code remembers that per project.

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 (user and local scope)	`~/.claude.json`	`%USERPROFILE%\.claude.json`
Launch command	`npx --yes skillry-cli@latest mcp`	`cmd /c npx --yes skillry-cli@latest mcp`
Check	`claude mcp get skillry`	same
Remove	`claude mcp remove skillry -s user`	same

The entry Claude Code stores (macOS)

{
  "mcpServers": {
    "skillry": {
      "command": "npx",
      "args": [
        "--yes",
        "skillry-cli@latest",
        "mcp"
      ]
    }
  }
}

Scope precedence, project approval and every other option are in the official MCP documentation.

Common questions

Do I have to run the command in every project?

No. --scope user makes Skillry available in all your projects. The default local scope would tie it to the folder you ran the command in.

Does Claude Code need a restart?

A new session picks the server up. In an open session, /mcp shows it after the health check.

Can my team share the entry?

Yes. --scope project writes it to .mcp.json in the repository, and each teammate approves it the first time they open Claude Code there.

Sources

Did this guide help?

PreviousOverview NextCodex