Sign Up

Connect Claude

Set up MediaThrive as a custom Claude connector or Claude Code MCP server.

Pilot setup requires an enabled MediaThrive service and a registered public client ID. Use the client ID below for your specific Claude client. Client IDs identify an application; they are not API keys. No client secret is required.

Claude web and Claude Desktop

Use Claude’s remote custom connector flow. The remote connector is associated with your Claude account and can be used in Claude Desktop; it does not require a local server configuration file.

  1. Open Add MediaThrive to Claude, or open Claude’s Customize → Connectors and add a custom connector. The link prefills only the name and endpoint; you must still enter the client ID in Advanced settings below. For an organization, an owner first adds it in Organization settings → Connectors.
  2. Name it MediaThrive and enter https://api.mediathrive.com/mcp as the remote server URL.
  3. Open Advanced settings and enter 2a257cab-2947-4cdf-a245-5363ffe87b2c as the public OAuth client ID for Claude web/Desktop. Leave the client secret empty.
  4. Add the connector, select Connect, and sign in to MediaThrive.
  5. Review the requested access, choose your team, and approve the connection. Enable the connector in the conversation’s tools menu if needed.
  6. Ask Claude to list your team’s recent media to verify access before generating anything.

Claude’s remote connection comes from Anthropic’s servers, including when you use the desktop app. A successful browser visit to the endpoint does not test the connector’s authentication.

MediaThrive registers https://claude.ai/api/mcp/auth_callback for this client. Do not substitute the Claude Code client ID. This is a custom connector setup, not a directory installation. See Claude’s custom connector guide.

Claude Code

Use a Claude Code release that supports preconfigured OAuth clients; the callback flow was checked with Claude Code 2.1.266. The registered Claude Code client is configured below:

bash
claude mcp add --transport http --scope user \
  --client-id d9f0a3fe-cf8d-4d1b-9f0d-a0a99786d3d1 \
  --callback-port 3118 \
  mediathrive https://api.mediathrive.com/mcp

Open Claude Code, run /mcp, select MediaThrive and authenticate in the browser. Choose the team and permissions on the MediaThrive consent screen. You can inspect the saved configuration with:

bash
claude mcp get mediathrive

The pilot uses port 3118 and registers both http://localhost:3118/callback and http://127.0.0.1:3118/callback to accommodate client versions. Keep that port available. Changing it requires a matching client registration.

Do not add --client-secret: this is a public OAuth client using PKCE. The pilot does not support automatic dynamic client registration; adding only the endpoint URL is insufficient. See Claude Code’s MCP authentication documentation.

Optional Claude Code skill package

Download MediaThrive for Claude Code 0.1.0. This optional package includes the MCP connection configuration and three skills for creating videos, refining scenes and generating narration. You can use it instead of the standalone Claude Code server configuration above. Avoid adding both copies of the same server.

  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 claude-code folder.
  3. In Claude Code, run the following commands, replacing /path/to/extracted/claude-code with that folder’s absolute path:
text
/plugin marketplace add /path/to/extracted/claude-code
/plugin install mediathrive@mediathrive
/reload-plugins
/mcp

Select MediaThrive and complete browser sign-in and team consent. Try /mediathrive:create-video, /mediathrive:refine-video, or /mediathrive:create-narration.

This is a downloadable local plugin package, not a listing in the Claude hosted connector directory. It is for Claude Code; Claude web and Claude Desktop use the remote custom connector flow above. Installing the package does not grant team permissions or enable paid work. Pilot availability and budget requirements still apply.

After connecting

Ask Claude to use MediaThrive explicitly if it chooses another tool. Review the selected team before creating drafts. Paid generation uses normal MediaThrive credits within your team’s MCP limits. For expired connections, sign in again; for a failed paid job, follow the operation recovery guidance.

The prefilled setup link follows Claude’s documented custom connector install-link format. It does not approve permissions or complete authentication for you.