Connect ChatGPT and Codex

Use MediaThrive with a registered ChatGPT custom app or Codex MCP client.

MediaThrive has no public directory listing yet. ChatGPT setup is an assisted pilot: ask MediaThrive to register your app and exact OAuth callback before connecting. Codex uses the pre-registered pilot client below. Availability depends on your client version and workspace settings; these instructions do not certify an end-to-end production connection.

ChatGPT

If your account or workspace provides developer mode and custom MCP apps:

  1. Enable developer mode in ChatGPT’s app settings, following your workspace’s policy.
  2. Create a custom app for https://api.mediathrive.com/mcp and select OAuth authentication.
  3. Use the static public client ID registered by MediaThrive for your app. Leave the client secret empty. MediaThrive must register the exact callback shown by the setup flow.
  4. Connect, sign in to MediaThrive, and select the team and requested permissions.
  5. Select the app in your conversation and ask it to list existing team media before creating a draft.

If your setup requires a client secret or does not offer a compatible static public-client flow, contact MediaThrive with the non-secret client details. Do not invent a secret or choose unauthenticated access. Automatic client registration and Client ID Metadata Documents are not supported in this pilot. See OpenAI’s developer mode documentation.

Codex

Use Codex 0.153.4, the version tested for this callback configuration, or a newer compatible release. Codex 0.144.1 ignores the required callback configuration and cannot use this setup. In your Codex config.toml, add the pre-registered pilot client:

toml
[mcp_servers.mediathrive]
url = "https://api.mediathrive.com/mcp"
scopes = ["media:read", "media:write", "media:generate"]

[mcp_servers.mediathrive.oauth]
client_id = "064cd589-a73b-4586-9d29-fa2ef9a986b5"
callback_port = 3119
callback_url = "http://127.0.0.1:3119/callback"

This pilot client registers both http://localhost:3119/callback and http://127.0.0.1:3119/callback. Keep port 3119 available. End-to-end authentication is still being verified. If Codex appends a server-specific callback identifier, ask MediaThrive to check server/client compatibility; the actual callback must exactly match registration. Do not copy the Claude Code callback.

Then authenticate:

bash
codex mcp login mediathrive

Sign in, select the team, and approve the requested access. For read-only access, request only media:read. Your role must permit each requested capability. The Codex MCP guide describes configuration and login; the configuration reference documents the public client ID and callback options.

If your installed version cannot configure a pre-registered client, upgrade to a compatible version or contact MediaThrive. Do not use a Supabase key, an internal renderer key or another user’s bearer token as a workaround.

Optional Codex skill package

Download MediaThrive for Codex 0.1.0. The package includes the MCP configuration and three skills: create-video, refine-video and create-narration. Use Codex 0.153.4 or a newer compatible release, as described above. Use the package instead of adding a duplicate manual MediaThrive server configuration.

  1. Download the ZIP and compare its SHA-256 digest with SHA256SUMS.
  2. Unzip it into a folder you intend to keep. The archive contains a codex folder.
  3. In a terminal, run the following commands, replacing /path/to/extracted/codex with that folder’s absolute path:
bash
codex plugin marketplace add /path/to/extracted/codex
codex plugin add mediathrive@mediathrive

Open a new Codex task and connect MediaThrive when prompted. Complete browser sign-in and choose your team. You can then use $create-video, $refine-video, or $create-narration, or describe the MediaThrive task naturally.

This adds a local marketplace from the downloaded folder. It does not imply a public marketplace listing or install an app in ChatGPT. OAuth consent, team permissions, billing eligibility and MCP budgets still govern access and paid work.

Using MediaThrive

Ask your assistant to inspect a news item, prepare exact narration, save a draft, and estimate its cost. Generate narration and render only when that is part of your request. Team budgets govern paid execution, while ChatGPT or Codex may apply additional tool approval controls. Read credits and team security before enabling generation.