The short answer
- 1Add one entry to your client. It starts
npx --yes skillry-cli@latest mcp(on Windowscmd /c npx …): nothing to download by hand and no API key. - 2Searching works without an account. The first time you install, the agent opens a browser page where you approve once; the approval stays in your OS keyring for 7 days.
- 3Pick your client below for the exact steps. Every client page ends with how to confirm the connection and what to do when it fails.
What you need
- A Mac or a Windows PC. Linux is not supported yet, because the approval is stored in the OS keyring and Skillry only supports Keychain and Credential Manager.
- Node.js 22 or newer. Check with
node --version; install the LTS build from nodejs.org if the command is missing. - One of the six clients below, signed in and up to date.
- A Skillry account only when you install. Searching and reading Skill details need nothing. A free account installs free Skills; Premium Skills need a purchase or a plan.
Pick your client
What happens, in order
You add Skillry to your client
The client starts the local server with npx the first time it needs it. That first start downloads the package and can take ten seconds or more; later starts are instant.
You describe what you want to make
The agent calls search_skills and shows candidates with preview links, inputs, dependencies and outside costs. No account is needed.
You pick one and say install
The agent calls get_skill_access. If your account is not connected yet, it opens the browser page described below.
You approve in the browser
The agent installs the Skill into the agent and scope you named. Installing never runs the Skill; the agent runs it later, when you ask.
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 your agent 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 the agent can’t see Skillry
Start with your client page, which lists the client’s own checks. These problems happen in every client:
| What you see | Likely cause | What to do |
|---|---|---|
| The agent says it has no Skillry tool | The entry was added for another project or scope, or the client was not restarted after the change | Run the check on your client page. If the server is missing, re-add it at user scope; if it is listed, restart or reload the client. |
| Searching works but installing is refused with a daily limit | Your account reached 50 Skill loads today | The limit resets at 00:00 UTC. Searching keeps working meanwhile. |
| 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. |
Limits and boundaries
50 a day
Skill loads per account, shared across MCP, the Skillry CLI and the website. Searching does not count.
7 days
How long one browser approval lasts. The agent asks again when it expires.
No API key
Nothing to paste. The approval is stored by your operating system, not by the agent.
12 tools
Search, inspect, install, update and account tools. Every argument is in the reference.
- Installing adds files to your agent’s Skills folder. Skillry never runs the Skill and never pays for model calls: a Skill that needs an image or video model uses your own tools or keys, and the agent shows that cost before you choose.
- The server runs on your computer and talks to skillry.dev only for the catalog, access checks and downloads. It treats catalog and package contents as untrusted data.
- You can disconnect at any time by asking the agent to disconnect your Skillry account, or by removing the entry from your client.
Every tool, in the reference
The Skillry MCP tool reference lists all 12 tools with their arguments, defaults, examples and recovery paths. You do not need it to get connected, but it answers “what can I ask for?” precisely.
Common questions
Do I need an API key?
No. Searching needs nothing, and installing needs a one-time approval of your Skillry account in the browser. The only stored secret is the approval your OS keyring keeps for 7 days.
Can I keep installing Skills the old way?
Yes. The install prompt, the Skillry CLI and ZIP downloads all stay. See Install a Skill.
Does the server send my files anywhere?
No. It runs locally and only contacts skillry.dev for the catalog, access checks and the Skill download you asked for.
Which client should I pick?
Use the client you already work in. Claude Code, Codex and Gemini CLI take a terminal command; Cursor and VS Code take an install link; Claude Desktop takes the Skillry .mcpb extension.
Sources
Did this guide help?
