Varosity
Создавайте видео, изображения, озвучку и музыку с помощью 60+ ИИ-моделей (Veo 3.1, Kling 3.0, Seedance, FLUX, ElevenLabs, Suno) из одного аккаунта Varosity. Удалённый MCP-сервер с входом через OAuth или API-ключ; оплата за каждую генерацию с ежедневным лимитом расходов.
Размещённый MCP-сервер
npx add-mcp 'https://varosity.ai/api/mcp'Устанавливается в Claude Code, Codex, Cursor и другие
Документация
One server. Every media model.
Varosity is a remote MCP server (Streamable HTTP) with tools for video, image, voice and music generation across 60+ models. Connect with a sign-in or an API key; the full tool list is public in the server card below.
- 1. Get a key. Create an account → API Keys → new key (starts with vsk_). Most new accounts include a small starter credit.
- 2. Add the server to your agent using the matching block below.
- 3. Ask for something: “Use Varosity to make a 5-second clip of a neon city street in the rain.”
Want to see a result before signing up? An agent can POST {"prompt":"…"} to /api/demo/image for one draft image, no key needed.
MCP endpoint https://varosity.ai/api/mcp
Auth Authorization: Bearer vsk_… (or X-API-Key)
Server card /.well-known/mcp/server-card.json
Claude Code
Run once in your terminal:
claude mcp add --transport http varosity https://varosity.ai/api/mcp \
--header "Authorization: Bearer $VAROSITY_API_KEY"
No key yet? Add the server without the --header line, then run /mcp in Claude Code and choose Authenticate to sign in to Varosity in your browser.
Cursor
Add to.cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"varosity": {
"url": "https://varosity.ai/api/mcp",
"headers": {
"Authorization": "Bearer vsk_…"
}
}
}
}
Windsurf and Cline use the same shape in their MCP config files.
Grok Bot
Add a remote MCP server with these three fields:
Name: varosity
URL: https://varosity.ai/api/mcp
Header: Authorization: Bearer vsk_…
In the Grok app, add the same URL and header as a custom connector.
Gemini CLI
Add to ~/.gemini/settings.json:
{
"mcpServers": {
"varosity": {
"httpUrl": "https://varosity.ai/api/mcp",
"headers": {
"Authorization": "Bearer vsk_…"
}
}
}
}
Manus, Perplexity & other agents with custom MCP connectors
Add a custom (remote) MCP connector and choose API key / bearer authentication:
Server URL: https://varosity.ai/api/mcp
Auth header: Authorization: Bearer vsk_…
(or) X-API-Key: vsk_…
Any agent or app — plain REST
No MCP client? Call the API directly. The OpenAPI spec lists every endpoint:
# What will it cost? No key needed.
curl "https://varosity.ai/api/v1/video/estimate?modelId=kling-3.0&durationSec=5"
# Make the clip. Returns a jobId.
curl -X POST https://varosity.ai/api/v1/video/generate \
-H "Authorization: Bearer $VAROSITY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"prompt": "slow orbit around a ceramic mug on an oak table, morning light", "modelId": "kling-3.0", "aspectRatio": "16:9", "durationSec": 5}'
# Poll every few seconds until status is "succeeded", then read outputUrl.
curl https://varosity.ai/api/v1/jobs/JOB_ID -H "Authorization: Bearer $VAROSITY_API_KEY"
# Images return directly, no polling.
curl -X POST https://varosity.ai/api/v1/images \
-H "Authorization: Bearer $VAROSITY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"prompt": "studio product shot of a matte black bottle", "model": "flux-1-schnell", "aspect_ratio": "1:1"}'
# Every endpoint:
curl https://varosity.ai/api/openapi.json
Meta Muse, ChatGPT apps, Claude.ai connectors
These connect by signing in — no key to paste. Add a custom connector (or MCP server) with this URL and the app opens a Varosity sign-in:
https://varosity.ai/api/mcp
- ChatGPT: Plugins → Add → Add custom MCP server. Paste the URL and leave Authentication on OAuth.
- Claude.ai: Settings → Connectors → Add custom connector. Paste the URL.
Both tested October 2026. Then:
- 1. Sign in to Varosity (or create a free account) when prompted.
- 2. Review what the app is asking for and approve. It gets the same permissions as a default API key, with a $5/day spend cap.
- 3. Disconnect it any time under API keys, where you can also change the cap.
Standards: OAuth 2.1 with PKCE, client ID metadata documents or dynamic registration, discovery at /.well-known/oauth-protected-resource. API keys keep working exactly as before.
More: the agent guide, ready-made skills, every model and price, and llms.txt.