The short answer
- 1Gemini CLI: run
gemini mcp add --scope user --transport stdio skillry npx -- --yes skillry-cli@latest mcp. Without--scope userit applies to the current project only. - 2Antigravity: merge the
skillryentry into~/.gemini/config/mcp_config.json, then type/mcpin Antigravity CLI. - 3In either tool,
/mcpinside a session lists the server and its tools.
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.
- Gemini CLI (
gemini --version) or Antigravity CLI (agy) installed and signed in. Ifgeminitells you it has been replaced, use the Antigravity tab. - Node.js 22 or newer (
node --version).
| Tool | Config file | Check |
|---|---|---|
| Gemini CLI | ~/.gemini/settings.json (user) or .gemini/settings.json (project) | gemini mcp list or /mcp |
| Antigravity CLI, app and IDE | ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace) | /mcp in the CLI; Installed MCP Servers in the app |
Add Skillry to Gemini CLI or Antigravity
- 1
Run this in any terminal. The
--separates Gemini’s own options from the arguments passed tonpx.macOS gemini mcp add --scope user --transport stdio skillry npx -- --yes skillry-cli@latest mcpYou should see: No error, and
gemini mcp listnow includesskillry. - 2
On Windows, run this instead so Windows can start
npx:Windows (PowerShell or Command Prompt) gemini mcp add --scope user --transport stdio skillry cmd -- /c npx --yes skillry-cli@latest mcp - 3
Start a new Gemini CLI session.
You should see:
skillryin the/mcplist with its tools.
- 1
Open
~/.gemini/settings.json(for one project,.gemini/settings.jsoninside it). - 2
Merge this into the
mcpServersobject, keeping any servers already there.macOS { "mcpServers": { "skillry": { "command": "npx", "args": [ "--yes", "skillry-cli@latest", "mcp" ] } } } - 3
On Windows use this entry instead.
Windows { "mcpServers": { "skillry": { "command": "cmd", "args": [ "/c", "npx", "--yes", "skillry-cli@latest", "mcp" ] } } } - 4
Save and start a new session.
You should see:
skillryin the/mcplist.
- 1
Open or create
~/.gemini/config/mcp_config.json. For one workspace, use.agents/mcp_config.jsoninside it instead. - 2
Merge this into the
mcpServersobject. The format is the same as Gemini CLI’s.macOS { "mcpServers": { "skillry": { "command": "npx", "args": [ "--yes", "skillry-cli@latest", "mcp" ] } } } - 3
On Windows use this entry instead.
Windows { "mcpServers": { "skillry": { "command": "cmd", "args": [ "/c", "npx", "--yes", "skillry-cli@latest", "mcp" ] } } } - 4
In Antigravity CLI type
/mcpto open the MCP manager and refresh. In the Antigravity app open Settings, then Customizations, find Installed MCP Servers and select Refresh.You should see:
skillrylisted with its tools.
Check that the connection works
- 1
Gemini CLI: list the configured servers.
Terminal gemini mcp listYou should see:
skillrywith its command and a connected status. - 2
Either tool: type
/mcpin a session.You should see:
skillrywith its tools, starting withsearch_skills.
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 Gemini CLI or Antigravity 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
| What you see | Likely cause | What to do |
|---|---|---|
gemini mcp list is empty in another folder | The server was added with the default project scope | Add it again with --scope user, or move the entry to ~/.gemini/settings.json. |
gemini says the CLI has been replaced | Your plan was moved to Antigravity CLI | Use the Antigravity tab. The entry is the same JSON in a different file. |
| Antigravity does not pick the file up | The file has a JSON error, or was not refreshed | Validate the JSON, then /mcp in the CLI or Refresh in 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
- 1
Gemini CLI: remove the server from your user settings.
Terminal gemini mcp remove -s user skillry - 2
Antigravity: delete the
skillryentry frommcp_config.jsonand refresh. To keep it but stop it loading, set"disabled": trueon the entry.
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 |
|---|---|---|
| Gemini CLI user settings | ~/.gemini/settings.json | %USERPROFILE%\.gemini\settings.json |
| Antigravity global config | ~/.gemini/config/mcp_config.json | %USERPROFILE%\.gemini\config\mcp_config.json |
| Launch command | npx --yes skillry-cli@latest mcp | cmd /c npx --yes skillry-cli@latest mcp |
| Check | gemini mcp list or /mcp | same |
{
"mcpServers": {
"skillry": {
"command": "npx",
"args": [
"--yes",
"skillry-cli@latest",
"mcp"
]
}
}
}Gemini CLI’s --scope, --timeout and --trust options are in the Gemini CLI MCP documentation; Antigravity’s file format and the app’s MCP settings are in the Antigravity MCP documentation.
Common questions
Is Gemini CLI going away?
Google moved free-tier and Google One users to Antigravity CLI on 18 June 2026; paid plans keep Gemini CLI. The Skillry entry is the same JSON in both tools.
Why --scope user?
Gemini CLI’s default scope is the current project. User scope puts the entry in ~/.gemini/settings.json, so it works in every folder.
Do the Antigravity app and CLI share the entry?
Yes. The app, the CLI and the IDE all read ~/.gemini/config/mcp_config.json.
Sources
Did this guide help?
