One MCP URL is not a second studio

https://mcp.versely.studio/mcp is a connector. Claude still is not captions, not 60 other models, not a second bill. Paste the URL; sign in; ask to generate.

/mcp is Settings → Connectors, a custom connector named Versely, that URL, Add → Connect, a Versely login, then "generate an image." That is the whole install. It is not a second product, not a second credit pool, and not a reason to stop naming the renderer. The host chat is still a chat. The jobs still run on Versely.

A connector, not a studio

MCP is how Claude, Perplexity, and any MCP-compatible client submit work to Versely. You paste one URL. You sign in. You ask. Images, videos, music, captions, and social posts can leave that conversation because the connector can call Versely, not because Claude grew a catalog.

A studio, in the sense this site uses the word, is the place you can pick the model the job needs, caption and deliver without a side door, keep a brand kit and a credit pool, and fail over when one family is the wrong row. The agent is that surface inside Versely. The MCP URL is a door into it. Doors are not buildings.

If you live in Claude Code, Cursor, or Codex, the page's own tip is to use the CLI instead — it auto-connects MCP and installs skills across every detected agent. The URL is for the connector tab. Do not treat the two as competing studios. They are two ways to point a host at the same bill.

What this URL still is not

1. Not captions

Pasting the connector does not turn Claude into a caption renderer. Burned-in, platform-native, word-timed captions are still an editor job on Versely. You can ask Claude to caption through the connector. The pixels still come from the Versely tool that burns type, on the Versely charge for that job. The chat window is not a typesetter.

2. Not sixty other models

Claude does not become the catalog. Generation models live on GET /api/v1/agentic/models and on the public catalog. The connector lets the host call those tools. It does not replace picking Kling 3 Turbo or Seedance 2.5 when the clip has to match. "Sixty other models" is the same boundary as Flow: a launcher is not the roster. Name the renderer in the brief.

3. Not a second bill

You sign in with the Versely account you already have. Jobs spend that balance. There is no parallel MCP tariff and no free generate because the host is Claude. Chat tokens and generations still bill on two meters inside the agent. Changing the host UI does not change the meter.

4. Not a second chat brain

The in-app planner is still whatever /chat-models says is default — documented as runpod/kimi-k2.7-code in the two-catalog write-up — or the chat_model you pin. GLM 5.3 is z-ai/glm-5.3, a custom OpenRouter id, text-only, not the default. Grok 4.6 is x-ai/grok-4.6 and can see a still. Connecting MCP does not pick those for you. Picking the chat model behind the agent is the two-catalog rule; the nine-id list is 9 chat models to pin.

5. Not a substitute for skills

Skills tell the host when and how to call Versely. MCP is the pipe the call runs through. Skills install with npx skills add AI-XLabs-Innovation/versely-skills — generate, slideshow, movie, ugc, music, social, analytics, pipeline. Cloning that repo is not a generate. Pair skills with the connector (or let the CLI wire both) so the agent can actually run jobs.

6. Not the in-app agent

The Versely agent still has brand kit, memories, conversation media, workflows, in-flight tasks. A Claude thread with MCP attached can submit jobs. It does not inherit every in-app extra unless you are in the app. Use the host for the conversation you are already in. Use /agent when the lasting preference and the media library are the work.

Paste, sign in, ask to generate

On claude.ai (or the desktop app):

1. Open Settings → Connectors.
2. Add a custom connector. Name it Versely. Paste https://mcp.versely.studio/mcp.
3. Add → Connect, sign in with Versely, then ask it to generate.

The invoke line the setup UI uses is "Generate an image with Versely." Swap in a video or a slideshow once the connector is live, and name the model in the same sentence if matching matters. Docs live on the versely-mcp GitHub repo.

Skills and CLI sit beside the connector

The setup section is three tabs on purpose: MCP, CLI, Skill. They are not three studios.

• MCP — one URL, host-agnostic, the connector tab.
• CLI — npm install -g @versely/cli, then versely auth login, then versely install. One line that handles skill install, auth, and MCP wiring across Claude Code, Cursor, Codex, Windsurf, Copilot, and the rest of the 50+ list.
• Skills — npx skills add AI-XLabs-Innovation/versely-skills, then sign in through the CLI so the skills can submit jobs.

If you only paste the URL and never install skills, the host can still call tools it discovers. If you only install skills and never connect MCP, the host knows the recipes and cannot run them. The tip on the MCP tab is the practical one: in Claude Code, Cursor, or Codex, use the CLI.

FAQ

Does connecting MCP give me a second Versely subscription?

No. You sign in with the existing account. Generates spend that credit balance. The connector is not a second bill.

Will Claude burn captions and pick Kling by itself?

Only if the job you ask for actually calls those tools, and only if the renderer is named or routed. Paste the URL so the host can call Versely. Pin the model in the brief if the clip has to match. Claude is still not the catalog.

Is GLM 5.3 the planner I get after I paste the URL?

No. Treat /chat-models as live. The documented default at the time of the two-catalog post is runpod/kimi-k2.7-code. GLM 5.3 is a custom OpenRouter id you send or save. MCP does not change that.

Do I need this if I only use the in-app agent?

No. /agent already is the studio. Use MCP when the conversation is already in Claude (or another MCP client) and you want that thread to submit Versely jobs without becoming a second app.