Use marketplace skills in Gemini CLI
On this page
You will connect Gemini CLI to the OPVS MCP server, then find, read and use marketplace skills from a normal conversation. How the parts fit together is on How it works.
You need: Node.js 18 or newer, and an OPVS workspace (your workspace admin approves your access).
1. Install and sign in
npm install -g @opvs-ai/cli @opvs-ai/mcp
opvs auth request -e <your-workspace-admin-email>Your admin receives an approval email. Once approved, the token is saved locally and the MCP server uses it.
2. Add the OPVS server to Gemini CLI
Add the server to ~/.gemini/settings.json (or .gemini/settings.json in a project):
{ "mcpServers": { "opvs": { "command": "opvs-mcp" } } }Start gemini and run /mcp: opvs should be listed with its tools.
3. Check it works
Ask Gemini CLI:
Use tool_search to find an OPVS skill for cleaning tracking parameters out of URLs.
You should get ranked packages, for example @di-atomic/url-utils, each with a telemetry_signal.
4. Read a skill (nothing to install)
Use tool_read on @di-atomic/url-utils and follow its recipe to clean these links: …
tool_read returns the skill's SKILL.md and a list of its reference files; the agent can read any of them with tool_read(name, path="references/…"). That is all a guidance skill needs.
5. Use a skill that calls a service
Install it on your workspace. A workspace admin does this once, either in the OPVS dashboard (Skills, at
app.opvs.ai/dashboard/marketplace) or by asking the agent to calltool_installwith the packageidfromtool_search. If the package needs permissions or credentials, they are granted during install; missing ones leave itpending.Learn its methods:
tool_help(name="@vendor/name", section="methods").Call it:
tool_call(skill="@vendor/name", method="…", params={…}). Read the_guidancein the reply before acting on the data.
tool_list_installed shows what your workspace has installed.
Troubleshooting
You see | Cause | Fix |
|---|---|---|
| no approved token | run |
the tool is "not enabled" or unknown | Gemini CLI has the server's tools switched off | enable the |
| the global install failed | re-run |
| a required permission was not granted | grant the permissions listed in the reply's |
| you are not a workspace admin | ask your admin to install it |
| it is not installed on this workspace | install it first (step 5) |
More detail on the server itself: MCP server.