10 agent hosts the setup page names in 2026

The setup surface lists ten hosts that take the same MCP URL and skill pack: Claude Code, Cursor, Codex, Gemini CLI, Windsurf, Copilot, Cline, Continue, Goose, and Replit — the hero only rotates five of them.

That list is the footer chip row on /developer, /mcp, /cli, and /skills. The headline cycles five names. The install objects do not change with the headline. Paste https://mcp.versely.studio/mcp. Run npx skills add AI-XLabs-Innovation/versely-skills. Wire both with the CLI when the host lives on your machine. There is no tenth MCP URL.

The hero rotates five; the footer lists ten

The H1 substitutes one word on a timer: CLAUDE, CURSOR, CODEX, WINDSURF, COPILOT. Those five are the marketing rotation. Under “Works with 50+ AI agents” the page prints ten chips, in this order: Claude Code, Cursor, Codex, Gemini CLI, Windsurf, Copilot, Cline, Continue, Goose, Replit.

The hero is not a filter. Gemini CLI, Cline, Continue, Goose, and Replit never occupy the H1 and are still on the named list. “50+” is the rest of the CLI detection set.

Tabs are the same three objects: MCP, CLI, Skill. The developer page is the standalone. /mcp, /cli, and /skills are the same block with a different initial tab.

The in-app agent is a different door. You do not install these hosts there. Pin a chat model there when you are in the app. Treat /chat-models as live; the documented default is runpod/kimi-k2.7-code. That brain is not this list.

The ten

Each row takes the same two objects. Host-specific furniture — a connectors panel, an mcp.json — is the host’s problem. Versely’s problem is one URL and one skill pack.

1. Claude Code

Named in the hero as CLAUDE and in the chips as Claude Code. The MCP tab’s example UI is Claude in the browser (Settings → Connectors). The tip on that tab says if you are in Claude Code, Cursor, or Codex, use the CLI instead: it auto-connects MCP and installs skills across every detected agent.

2. Cursor

Named in the hero and the chips. versely install writes MCP into configs it finds, including Cursor. Restart the agent. MCP config is not reloaded in place.

3. Codex

Named in the hero and the chips. Same CLI path: npm install -g @versely/cli, versely auth login, versely install. Same skill pack. Do not invent a Codex-only MCP host.

4. Gemini CLI

On the chip row. Not in the five-name rotation. Still the same URL and the same npx skills add AI-XLabs-Innovation/versely-skills. Missing the headline is not a missing install.

5. Windsurf

Named in the hero as WINDSURF and in the chips. If the CLI detects it, versely install wires MCP. If it does not, paste the connector URL the host’s MCP UI asks for.

6. Copilot

Named in the hero as COPILOT and in the chips. Same MCP URL. Same skill pack. Copilot’s agent surface is a host, not a second Versely catalog.

7. Cline

Chip only. Same two objects. Do not wait for a Cline-branded Versely plugin. Paste the URL or let the CLI write the config the host reads.

8. Continue

Chip only. Same two objects. Continue is an agent host on this list, not a second skill repo.

9. Goose

Chip only. If Goose is on the machine and the CLI detects it, versely install is the write. If you only have a connectors field, paste https://mcp.versely.studio/mcp.

10. Replit

Chip only. A cloud IDE is still a host. The credential is still a Versely key. There is no Replit-only generate row.

Same MCP URL, same skill pack

MCP is the callable. The hosted server is https://mcp.versely.studio/mcp. In a chat client: add a custom connector named Versely, paste that URL, Connect, sign in. A wrong host, a missing /mcp, or http:// is a different resource. Paste it exactly. MCP is that tab.

Skills are procedures. One command pulls the eight packs — generate, slideshow, movie, ugc, music, social, analytics, pipeline — into the host. Skills is that tab. Cloning markdown is not a generate.

The CLI wires both. npm install -g @versely/cli, then versely auth login, then versely install. npx @versely/cli setup is the one-pass: skills, browser sign-in, MCP into every detected agent. CLI is that tab. 3 installable objects every coding agent should get in 2026 is the three-object contract this list sits on.

The invoke smoke test on the setup surface is “Generate an image with Versely.” That sentence does not pick a renderer and does not pin z-ai/glm-5.3 or x-ai/grok-4.6. Name the generate row in the brief when matching matters. GLM 5.3 is text-only custom OpenRouter. Grok 4.6 is vision. Neither is a host on this list.

The hero is not the install list

Operators stall in two places. They see CLAUDE in the H1 and skip Gemini CLI. They see “50+” and assume the ten chips are decoration. The chips are the named roster. The hero is a subset for the animation. Install for the host you actually run.

MCP-only is fine in a browser connector. Terminal agent, MCP only: tools appear, then the first batch has no pre-flight. Terminal agent, both: the intended setup. One key, one MCP write, one skill add, then restart each agent you will use. A chip on the marketing row is not a connected session.

FAQ

Why does the headline only show five names?

Because the H1 rotates CLAUDE, CURSOR, CODEX, WINDSURF, and COPILOT. The footer still prints ten chips. Gemini CLI, Cline, Continue, Goose, and Replit are on the named list. The install objects are the same for all ten.

Do I paste a different MCP URL for Cursor than for Claude Code?

No. The URL is https://mcp.versely.studio/mcp on every host that takes a connector. The CLI writes that same server into detected configs. A missing /mcp is a different resource, not a different product.

Is the in-app Versely agent one of the ten?

No. The ten are coding-agent hosts. The in-app agent already has procedures baked in. Pin a chat model there; do not run npx skills add inside the web app expecting these files to load.

Does installing the skill pack pin GLM 5.3 or Grok 4.6?

No. Skills call Versely. They do not set chat_model. z-ai/glm-5.3 and x-ai/grok-4.6 are planner ids behind the in-app agent, not generate rows and not this host list.