OfflineCreator MCP troubleshooting directory

Route the symptom before changing configuration

Use the failure boundary as the first decision. A connection failure prevents the client from listing tools. An authentication failure carries an HTTP status or OAuth challenge. A scope problem changes which tools appear. API and tool exceptions can return isError, while wait_generation can normally return a terminal failed status without that status itself being an isError result. Upload and output problems happen only after a generation ID exists.

For the recommended remote path, use https://mcp.offlinecreatorstudio.com/mcp and complete browser sign-in and consent. Local stdio and the legacy https://offlinecreatorstudio.com/mcp endpoint are API-key fallbacks. Do not move an API key into a URL while troubleshooting.

Cannot connect

Check endpoint, transport, and process startupConfirm Streamable HTTP for the recommended URL, or confirm that the configured stdio command starts and stays running.

401 during remote OAuth

Inspect the challenge and discovery flowA protected remote server can answer the first unauthenticated request with 401 so the client can discover authorization metadata and start OAuth.

Tools are missing

Compare the visible list with granted scopesOfflineCreator registers model, read, and generation tools only when the corresponding models, read, or generate scope is present.

API or tool exception returned isError

Read status and nested details before retryingThe MCP server preserves the Studio API status and body in the tool error result.

Upload or output failed

Keep the same generation IDCheck whether the job is reserved, queued, completed, or failed before uploading again or asking for a download URL.

Match the exact error contract to the next action

401 on recommended OAuth endpoint

Let the client follow WWW-AuthenticateVerify protected-resource and authorization-server discovery, then sign in and consent. A stale or invalid token also requires re-authorization.

API key appears in the URL

Remove the query parameterUse the recommended OAuth endpoint, an Authorization: Bearer header on the legacy endpoint, or OFFLINECREATOR_API_KEY for local stdio.

Expected tool absent

Reconnect with the required scopemodels exposes list_models; read exposes credits, status, wait, output, and history; generate exposes generation, upload, and cancellation.

Tool result has isError true

Read the returned error, status, and detailsCorrect the tool arguments or account condition described by the result before deciding whether a retry is appropriate.

Generation status is failed

Reconcile status and credits before a replacement retryKeep the same generation ID, confirm the terminal status with get_generation or wait_generation, then call get_credits. OfflineCreator says failed jobs refund reserved credits automatically; verify the balance before starting a replacement.

Use the generation ID as the recovery key

If generate returns status reserved with uploadRequired true, the selected model needs an image. On remote MCP, send imageBase64; local filePath is disabled. On stdio, filePath must remain under the configured upload root. PNG, JPEG, WebP, and GIF are accepted after content sniffing, with a 10 MiB limit.

After upload_input submits the reserved job, use get_generation or wait_generation with the same ID. Ask for download_output only after status completed. If wait_generation times out, it returns the latest status with timedOut true; a timeout is not proof that the provider failed.

Continue with the narrowest corrective guide

Use the 401 guide when discovery or bearer authentication is the first failing boundary. Use the query-key guide when a key was placed in the endpoint URL. Use the OAuth discovery guide when the client never reaches browser sign-in. Return to the MCP and CLI setup page when the endpoint or transport itself is wrong.

Editorial ownership boundary

This directory owns broad OfflineCreator MCP triage and the first decision after an error. The linked help pages own individual codes, OAuth stages, client behaviors, and reproducible fixes. Consolidate this page into /mcp-cli if the current error contracts and runbooks can no longer be verified.

The complete evidence refresh retained 57 item-level records: 17 Digg clusters, four general-web results, 17 Reddit threads, 12 TikTok videos, and seven YouTube videos. Item review classified eight as marginal, eight as promotional, 36 as irrelevant, four as unverifiable, and one as unsafe because it recommended broad administrator access and configuration changes without adequate safeguards. None verified an OfflineCreator error contract or runbook, so no community source, claim, or citation was added.

Coverage remains degraded. Reddit returned 17 records before HTTP 429, Instagram failed with HTTP 404, the jobs lane failed DNS resolution, and X was unavailable because optional credentials were not configured. All seven YouTube records lacked publication dates and reported zero captured views, likes, and comments. General troubleshooting anecdotes may suggest questions to test, but they cannot establish OfflineCreator status mappings, retry safety, client compatibility, or production behavior without a reproducible run.