Connect
- Claude.ai
- Claude Desktop
- ChatGPT
- Claude Code
- VS Code
- Cursor
- npx (local)
Connect via Custom Connectors on claude.ai.
1
Open connectors
Go to Settings → Connectors in Claude.
2
Add custom connector
Click + → Add custom connector, then paste:
3
Authorize
Click Add. A browser window opens — log in to your varg.ai account and click Approve. You’re connected.
Available tools
Generation
Start here. One tool per thing you want, with defaults chosen for you — describe the result and you get it in a single call.job_id immediately — pass wait: true to block instead.
The full catalog
The tools above cover the common cases with one model each. varg has hundreds, and each accepts its own options; a fixed tool per capability could only ever expose the fields they all share. So anything model-specific goes through the registry, where your assistant discovers the catalog at the moment it needs it.list_tools once, get_tool when it needs a model’s specifics, then call_tool. A model added to varg shows up immediately — there is no MCP release to wait for.
Jobs
Rendering and templates
Templates render as published — there is no variable substitution. To customise one, read its source with
get_template, edit the TSX, and pass it to render_video.Catalog and cost
Files and folders
Folders belong to one account, so
list_workspaces returns the ones in whichever team the connection works in. A personal folder is not visible from a team connection, and the reverse.
Teams
See Which account it works in.
Which account it works in
Each connection is bound to one account — your personal one, or a team you belong to. Generations are billed to that account’s balance and files land in its library. The binding is per connection, not per user. Claude Desktop, Cursor, and VS Code each register separately, so each gets its own. One agent can work in Marketing while another works in Product. You choose when you connect. The consent screen has a Works in picker listing your teams, defaulting to your personal account; if you are in no teams, it shows Personal and there is nothing to pick. To change it later, ask the assistant:set_team takes effect immediately, including for work already running, and is remembered for future sessions. It chooses among teams you are already in — it cannot grant you access to a new one. It also takes an optional workspace_id, the folder new output is filed into when a call does not name one. Settings → Connected Apps shows each connection’s account read-only.
If you are removed from a team a connection is bound to, that connection stops running anything and says so. It does not quietly fall back to your personal account — that would spend the wrong balance. Use
list_teams and set_team to move it, or ask a team owner to restore your membership.This applies to OAuth connections. In local stdio mode (
npx @vargai/mcp) the account is whichever one your API key belongs to.How it works
- Your client discovers the authorization server from
mcp.varg.ai - It registers itself automatically — no client id to copy
- You log in to varg.ai, pick which account it works in, and approve on a consent screen
- Your client receives a short-lived access token and a refresh token, and renews on its own
Inline media previews
generate_image, generate_video, generate_speech, call_tool, get_job, render_video, and use_template return an inline preview in your chat. It shows progress while the job runs, then picks a player from the result:
- Images — displayed inline with click-to-open fullscreen
- Videos — embedded player with play/pause controls
- Audio — compact player with progress bar and seek
Pricing
varg uses a credit system. 1 credit = $0.01 USD.
Cached results are free. Use
check_balance to see the remaining credits of the account the connection works in.
Get API Key
Sign up and get your API key
AI Models
Browse all available models with pricing
Templates
Pre-built video templates
API Reference
Full REST API documentation