Connect Vixdeo to ChatGPT — MCP connector

Vixdeo is an AI editorial video production platform; it is not ViX (TelevisaUnivision's streaming service) nor Videx.

What it does and what it requires

The connector gives Claude the SAME contract the human director uses: it creates a piece from an idea, follows its production to the finished video and corrects scenes with the same operations as the Studio. Vixdeo is the AI video producer: it turns an idea or a script into a finished piece - fact-checked script, voice, music and visuals directed scene by scene - operable by people and by agents.

Requires: a Vixdeo account (Google Sign-In), and a balance in your organization’s wallet — or a platform-operator account, which is not charged. The first video of an account is on the house.

Steps

ChatGPT on the web, on Plus, Pro, Business, Enterprise and Edu plans, with developer mode enabled.

  1. Settings → Apps → Advanced and turn on developer mode.
  2. In a conversation’s app picker, hit + and paste the URL: https://vixdeo.com/v1/mcp.
  3. Authorize with your Vixdeo account: the server uses OAuth and asks for no manual credentials.
  4. Ask it to start with whoami and to price with estimate before producing.

⚠️ OpenAI’s rules forbid selling or charging inside the app: topping up the wallet happens on vixdeo.com, not in ChatGPT. If the wallet is short, production waits for funds and you top up outside.

Verified against the documentation of ChatGPT on 2026-09-16.

Vixdeo also connects to: Claude · Claude Code · Gemini · Copilot · Perplexity · Le Chat · n8n · Goose.

Write permissions

Every tool declares whether it is read-only (readOnlyHint) or a write. Read-only tools run without asking. Write tools —run_op, direct, commit, generate_script, judge_script, rewrite_script, produce, cancel, set_head, request_upload, complete_upload, assign_material— ask for your approval on every call, unless you mark the tool (or the connector) as trusted / “always allow” in the connector’s settings.

If Claude says “No approval received”, the server did not fail: the write call was waiting for your approval and did not get it (the prompt was dismissed or timed out). Ask again, or mark the tool as trusted under Settings → Connectors → Vixdeo.

The ones that also spend your organization’s wallet are run_op (only rewrite_scene, tighten_hook), direct, generate_script, judge_script, rewrite_script, produce. estimate prices the same request at $0 first; the script (first station) is written and charged BEFORE any wallet check; the studio build and the final render do check the wallet and stop the line at waitingForFunds if it does not cover them.

Canonical flow

  1. whoami — who you are, scopes, wallet and whether you operate the platform
  2. list_referents — the formats, the duration and writing profiles, the defaults
  3. estimate — the price band and whether the request is complete, BEFORE spending ($0)
  4. generate_script — creates the piece; with auto_produce=true the line runs on its own to the video
  5. get_project_status — the status; polled every 60-120 s because the server never pushes

The agent receives no notifications: it has to ask again. Publishing to a channel is not in the connector.

Example prompts

Quote without launching anything ($0)

Tools exercised: whoami · list_referents · estimate

Using Vixdeo: tell me who I am and my wallet balance, list the available formats and quote a 3-minute educational explainer in Spanish about “how an mRNA vaccine works”. Do not launch anything: I want the price band, whether the request is complete, and at which station the line would stop if the wallet did not cover it.

Launch the script without producing, then edit a scene

Tools exercised: list_cast · generate_script (auto_produce=false) · get_project_status · get_project_vbp · run_op · commit

Using Vixdeo: find a male Spanish voice in list_cast and use its id. Create a short critical essay in Spanish about “silence in Bresson’s cinema” with production.auto_produce=false and that voice in cast.voice. When the script is ready (check the status every minute), read the blueprint, halve the narration of scene 0 with run_op set_scene_fields, commit, and tell me the id and sequence of the new version. Do not produce the video.

Review versions, move the cut and report publication

Tools exercised: list_projects · list_versions · set_head · get_project_status

Using Vixdeo: find my most recent project in FINAL_REVIEW or STUDIO_READY, list its versions with sequence, origin and isHead, and if an earlier version has the same number of scenes make it the cut with set_head. Then report the publication state (publication) and the final video URL if it exists. Publishing to a channel is not available from the connector: it is a human decision in the app.

Privacy, terms and support