Voyager · Setup & help

Voyager in ChatGPT, Claude and Codex

Add Voyager to the AI chat or coding agent you already use. Ask for a shot, a poster or a voiceover and it renders on Voyager with your existing account and credits.

Before you connect

Every client connects to the same Voyager server:

https://mcp.voyager.so/mcp

You sign in with your Voyager account and choose a workspace; there is no key to paste. Access follows that workspace’s current membership, plan and credits. Connecting does not create a separate credit allowance, and the Voyager desktop app does not need to be running.

The tools cover images, short videos, speech, music, sound effects and 3D models, plus your workspace’s brand kits, imported references, results and saved Cast. Start by asking for your account status and the available models; the server decides which operations your plan can use.

Leasing cloud GPU machines to render 3D with Blender or Vork uses a separate server; see Voyager Cloud.

ChatGPT

  1. Open Voyager in ChatGPT’s plugin directory and add it.
  2. Sign in with your Voyager account and choose your workspace.
  3. In a new chat, type @Voyager and ask for what you want to make.

Set it up by hand instead

You can add the same server as a custom MCP server if your ChatGPT workspace allows custom connections. In ChatGPT on the web, open Plugins, choose +, then Add custom MCP server. Name it Voyager, paste the server URL above, choose OAuth, and sign in. See OpenAI’s connection guide.

Claude

Voyager is not in Claude’s connector directory yet, so it takes four steps in Claude on the web or desktop:

  1. Open Settings → Connectors.
  2. Choose Add custom connector, name it Voyager and paste the server URL above.
  3. Click Connect and sign in with your Voyager account.
  4. In a new chat, open + → Connectors and turn on Voyager.

Claude Code

Add the server with one command:

claude mcp add --transport http voyager-cloud https://mcp.voyager.so/mcp

Then run /mcp in Claude Code, choose voyager-cloud and sign in with your Voyager account in the browser. The name voyager-cloud keeps this hosted connection apart from the desktop app’s local Voyager plugin.

Codex

Add the server and sign in:

codex mcp add voyager-cloud --url https://mcp.voyager.so/mcp
codex mcp login voyager-cloud

Finish signing in with your Voyager account in the browser window that opens. In Codex, check the connection with /mcp, then ask for a shot. See OpenAI’s MCP setup guide.

Credits and generation

Generation uses your Voyager workspace credits. A plain request generates directly; ask what a job will cost first if you want an estimate. An estimate does not hold credits and is not the final charge. There are no credit purchases or upgrade offers inside the plugin.

Every generation returns a job ID. Use it to check progress or recover a result after the conversation closes. You can ask to cancel an image, video or speech job; cancellation is best effort, and work a provider already did can still be charged. Music, sound effect and 3D jobs cannot be cancelled. If a download or preview fails, check the existing job before generating again.

Cast and voices

A real-person or licensed-character Cast card starts as a draft. Its creator must open the Voyager permission link in a browser, sign in, and review the exact version and reference images. An agent or embedded card cannot approve it. Changing its references needs another review.

Premade voices follow your account’s availability. Speech with a voice clone you already made in the Voyager app needs a plan that includes voice cloning (see pricing). The plugin does not create or record new clones. Cast saved here is separate from Cast stored in desktop projects; the two do not sync.

Disconnect and revoke access

Open Connected apps, find the app and workspace, then choose Revoke. Do this even if you already disconnected in ChatGPT or Claude or removed the server from Claude Code or Codex: those actions do not necessarily revoke the Voyager authorization.

Revoking stops new requests through that connection. Work already accepted may finish and be charged. It does not delete your saved Cast, retained results, or copies downloaded by another service. Delete unwanted assets or Cast separately.

References, results, and retention

  • Abandoned uploads: 24 hours.
  • Imported references: 7 days. Work already accepted may keep a reference available while the job runs, for at most 24 hours past its normal expiry.
  • Generated outputs: available to download for 30 days.
  • Saved Cast: cards and references explicitly saved into Cast persist until deleted.

Media links last at most 10 minutes and may expire sooner with the asset. New requests check current access. Revoking a connection or deleting an asset stops new authorized requests; it cannot recall a downloaded copy or bytes already streaming.

Expiry ends access before physical cleanup finishes. Deletion is queued and retried if it fails. Provider copies, chat history, and financial, security, or request records have separate retention rules; the media schedule does not delete those records.

See the Privacy Policy for what the hosted tools collect, who receives it, and the separate rules for job and billing records.

If something does not work

  • Sign-in works but access is refused: check which workspace you chose and that it has Voyager access and credits.
  • Voyager does not respond in Claude: turn it on for the chat under + → Connectors.
  • A preview or download link expired: links last at most 10 minutes. Ask for the asset again by its ID to get a fresh one.
  • The permission page says a card changed: refresh and review the new version before confirming.