The connector is unavailable
The public MCP endpoint is https://api.mediathrive.com/mcp. The service and paid execution have separate rollout controls. During the pilot, an unavailable endpoint can mean the service has not been enabled. A connected assistant can also be unable to generate if paid execution remains disabled. Ask MediaThrive to confirm availability for your pilot before repeatedly reconnecting.
OAuth registration fails
The pilot requires a pre-registered public client ID. Dynamic registration and Client ID Metadata Documents are not supported. Check that the ID belongs to the client you are configuring and that the secret is empty. An endpoint-only setup can fail when the assistant attempts automatic registration.
For Claude web/Desktop, use the Claude web client registration. For Claude Code, use its separate registration and callback port 3118. For Codex or ChatGPT, have MediaThrive verify the exact callback produced by your client; callbacks cannot be guessed or substituted.
The browser returns a redirect mismatch
The callback must match the registered URL exactly, including hostname, port and path. localhost and 127.0.0.1 are different hostnames. Claude Code’s pilot registration includes both on port 3118. Keep the configured port available and use a supported client version.
Do not send the full redirect URL to support: it can contain an authorization code. Send only the client name/version, callback hostname/path without query parameters, and the non-secret error message.
Sign-in worked but a tool is denied
Check which team you selected, whether you still belong to it, and whether your role permits the tool. Read, edit and generation permissions are separate. Reconnect if the original consent did not include the needed scope. A revoked or expired connection needs a new sign-in.
A missing item may belong to another team. Lists are paginated; ask the assistant to fetch the next page rather than assume an item does not exist.
Paid generation is blocked
Ask your administrator to check the monthly and per-job MCP limits, existing holds and normal billing eligibility. A zero limit blocks paid work. An estimate does not reserve capacity, so another job may consume available budget before your request begins.
Do not repeatedly submit new jobs to work around a budget rejection. Ask for a smaller operation or have the administrator deliberately adjust the limit.
A draft changed or audio no longer fits
Inspect the draft again and use its latest revision. Another edit can make a saved revision stale. Editing narration removes old narration audio; generate or choose ready audio matching the new text before attaching it.
Attached audio must fit the existing scene duration. Audio synthesis does not automatically lengthen a scene. If the draft’s timing no longer works, prepare a new draft with suitable durations. Rendering requires existing, ready media; resolve missing or unsupported generated layers first.
A paid request timed out or remains running
Keep the operation ID and ask the assistant to check get_operation. Do not request a replacement generation with a new idempotency key. Work can have reached the provider even when the client loses its response.
Unknown outcomes and stale operations require MediaThrive to reconcile provider work and billing. Their holds remain until reconciliation; deleting a connection or lowering a budget does not settle them. Contact support with the operation ID and approximate time of the request, without credentials or private content.
The assistant does not use MediaThrive
Enable the connector for the conversation and ask explicitly: “Use MediaThrive’s list_media tool to list my team’s recent videos.” If tools changed after a rollout, refresh the connector’s tool list or start a fresh session. A skill or plugin package can guide the assistant, but it does not replace OAuth consent or grant team permissions.