Connect Skillry MCP in Cursor (Link or mcp.json)

The short answer

1On skillry.dev/mcp choose Cursor, select Add to Cursor, and confirm the server inside Cursor.
2Or merge the skillry entry into ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project).
3Check on Cursor’s Customize page: skillry should be switched on and list its tools.

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

Before you start

Checked against the official documentation on 28 October 2026. Not yet run on a real installation of this client; if a step differs on your machine, use Report an issue at the bottom.

Cursor installed and signed in.
Node.js 22 or newer (node --version). Cursor starts the server with npx.

File	Applies to	Use it when
`~/.cursor/mcp.json`	Every project on this computer	You want Skillry everywhere. This guide.
`.cursor/mcp.json` in a project	That project only	You want to share it with a team through the repository.

Add Skillry to Cursor

Fastest. Cursor shows you the entry before it saves it

1
Open skillry.dev/mcp, choose Cursor and your operating system.
2
Select Add to Cursor. Your browser asks whether to open Cursor; allow it.
3
In Cursor, review the server named skillry and its npx command, then confirm.
You should see: skillry in the MCP list on the Customize page.
Cursor opening is not the same as Skillry being connected. Check the Customize page, or run the first search below.

When you want to see exactly what is saved

1
Create or open ~/.cursor/mcp.json. For one project, use .cursor/mcp.json inside that project instead.

Merge this into the mcpServers object, keeping any servers already there.

macOS

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

On Windows use this entry instead.

Windows

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

4
Save the file. Cursor picks the change up; if the server does not appear, restart Cursor.
You should see: skillry in the MCP list on the Customize page.

Check that Cursor is connected

1
Open Customize from the sidebar and find skillry among the MCP servers.
You should see: The server switched on, with a healthy status and its tools listed, starting with search_skills.
2
If it shows an error, select it to read the log; the first start downloads the package and can take ten seconds or more.

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 Cursor’s agent chat 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 Cursor 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 Cursor can’t see Skillry

What you see	Likely cause	What to do
`skillry` is not on the Customize page	The file is in the wrong place, or the JSON is invalid	Check the path (`~/.cursor/mcp.json` for every project) and validate the JSON: no trailing commas, and `skillry` inside `mcpServers`.
The Add to Cursor link did nothing	The browser blocked the `cursor://` link	Allow the browser to open Cursor, or use the Edit mcp.json tab.
The server is switched off	It was toggled off on the Customize page	Switch it on; Cursor keeps the entry either way.
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
On the Customize page remove skillry, or delete its entry from mcp.json. To keep it but stop it loading, switch it off there instead.
You should see: skillry gone from the MCP 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

Item	macOS	Windows
Global config file	`~/.cursor/mcp.json`	`%USERPROFILE%\.cursor\mcp.json`
Project config file	`.cursor/mcp.json`	same
Launch command	`npx --yes skillry-cli@latest mcp`	`cmd /c npx --yes skillry-cli@latest mcp`
Check	Customize page	same

The entry Cursor stores (macOS)

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

The Add to Cursor link is cursor://anysphere.cursor-deeplink/mcp/install?name=skillry&config=…, where config is the same entry, base64-encoded. Cursor decodes it and shows it to you before saving. Details are in the install links documentation.

Common questions

Is the Add to Cursor link safe?

It carries only the server name and the launch command, base64-encoded. Cursor shows both before you confirm, and nothing runs until you do.

Global or project file?

Global (~/.cursor/mcp.json) for yourself. Project (.cursor/mcp.json) when a team should get it from the repository.

Does Cursor need a restart?

Usually not: the Customize page refreshes when the file changes. Restart Cursor if the server never appears.

Sources

Did this guide help?

PreviousCodex NextVS Code