3 installable objects every coding agent should get in 2026

Versely is three objects, not one plugin: paste https://mcp.versely.studio/mcp, run npm install -g @versely/cli then versely install, and npx skills add AI-XLabs-Innovation/versely-skills — skills are procedures, MCP is the callable, the CLI wires both.

This is the install list for Claude Code, Cursor, Codex, and the rest of the hosts the CLI detects. The developer page is the same three tabs. Installing one layer and expecting the other two is how you get a connected agent that still retries a 402. The in-app agent already has procedures baked in. You do not install skills there. This page is the host-tool install.

Three objects, not one plugin

A plugin implies a single binary that both knows the job and does the job. Versely splits that on purpose.

• MCP is the callable surface: tools with schemas, invoked in a conversation.
• Skills are markdown procedures: when to call, how to poll, what a 402 means.
• CLI is wiring: a credential on disk, MCP written into agent configs, skills on the machine if you take the bundled path.

Skills or MCP tools: instructions and callables is the two-layer rule. CLI, MCP, or API is who initiates the request. This page is the three objects you put on the laptop. Same catalog, same credit balance, same async jobs. There is no free generate allowance. The objects change how the agent reaches the catalog, not what it bills.

The three

1. MCP — paste https://mcp.versely.studio/mcp

The hosted server is the resource. In Claude: Settings → Connectors, add a custom connector named Versely, paste that URL, Connect, sign in. The MCP page is that setup.

Once connected, the agent sees mcp__versely__* tools. There is no key to paste in a chat client. There is also no runbook inside the tool for “check the balance first.” The callable does the work you asked.

A wrong host, a missing /mcp, or http:// is a different resource. The token’s aud is that URL. Paste it exactly. MCP-only is fine while you are in the loop. In a terminal agent it is the common failure: tools appear, then the first batch spends without a pre-flight.

2. CLI — npm install -g @versely/cli then versely install

The CLI is a credential and wiring tool, not a job runner. There is no versely generate. CLI lists the commands.

Install globally. Sign in with versely auth login and approve access in the browser. Then versely install writes the MCP server into the configs of the agents on that machine: Claude Code, Cursor, Codex, and the rest of the detected list.

The key lands at ~/.versely/config.json. Headless jobs still need a minted vsk_ key in the environment. VERSELY_API_KEY takes precedence over the file.

npx @versely/cli setup is the opinionated one-pass: skills, auth, MCP wiring. The three named objects stay three objects. Restart the agent after a write. MCP config is not reloaded in place.

3. Skills — npx skills add AI-XLabs-Innovation/versely-skills

One command pulls the eight packs — generate, slideshow, movie, ugc, music, social, analytics, content-pipeline — into the host. The skills page is that tab.

Each pack is a folder with a SKILL.md. The body is the operating procedure: which endpoint, how to poll GET /api/v1/status/:requestId, and the error ladder (401 bad key, 402 credits, 403 scope, 429 back off).

Skills do not mint a key and do not write an MCP config. If you run the npx command and then wonder why the agent cannot generate, you installed instructions and no callable. Pair them with MCP, or export VERSELY_API_KEY and let the pack curl.

Skills are procedures; MCP is the callable

Watch a request like “generate a 9:16 product clip, then caption it.”

MCP alone. The agent sees tools. It may skip the credit check. It may treat a 402 as a retryable blip. None of that is the tool’s fault.

Skills alone. You get the runbook. You lose the typed schema. It works. It is also how you discover image_url went to an endpoint that wanted images: [...].

Both. The skill names the path. MCP executes it. The skill is why the agent checks credits first and does not retry a 402.

MCP is capability. Skills are discipline. Capability without discipline spends credits.

The CLI wires both

Paste the connector when you live in a chat client. Add the skills when the agent needs the job written down. Run the CLI when the machine should have a durable credential.

Chat client, MCP only: fine for one-shot “make an image of X.” Terminal agent, skills only: fine if a key is already in the environment. Terminal agent, MCP only: tools appear, then the first batch has no pre-flight. Terminal agent, both: the intended setup.

npm install -g @versely/cli then versely install is the wiring half. npx skills add AI-XLabs-Innovation/versely-skills is the procedure half. Together they are the 2026 default on a coding agent you use more than once.

The in-app agent is a fourth door, not a fourth object on this list. Pin a chat model there (runpod/kimi-k2.7-code is the documented default) when you are in the app. That brain is not this install.

FAQ

Do I need all three if I only use Claude in the browser?

Paste https://mcp.versely.studio/mcp and sign in. That is MCP. Skills and the CLI matter when the host is a terminal agent on your machine. Browser Claude with the connector is a valid MCP-only setup.

Does versely install generate video?

No. The CLI wires MCP and stores a credential. Generation still goes through the catalog, billed in credits. There is no versely generate.

Can I install skills without MCP?

Yes. The packs can curl https://api.versely.studio with Authorization: Bearer $VERSELY_API_KEY. You keep the polling rules. You lose the typed schema. For a coding agent you use weekly, install both.

Is this the same as pinning GLM 5.3 or Grok 4.6 in the Versely app?

No. z-ai/glm-5.3 and x-ai/grok-4.6 are chat models behind the in-app agent. This page is host-tool objects: connector, CLI, skills. Same catalog. Different door.