Fix missing OfflineCreator MCP tools

Verify the tool surface before changing the connection

A missing OfflineCreator MCP tool is not automatically a broken server. First identify the connection mode, then compare the tools your client currently shows with the published package. Version 0.1.2 maps `list_models` to `models`; `get_credits`, `list_generations`, `get_generation`, `wait_generation`, and `download_output` to `read`; and `generate`, `upload_input`, and `cancel_generation` to `generate`. When the server receives a non-empty scope set, it omits tools whose required scope is absent. When scopes are absent or empty, it registers every tool. The published stdio entry point starts the server without passing scopes, so a short stdio tool list is not explained by this registration filter.

Use this page against the public 0.1.2 package and the OAuth metadata retrieved on 2026-08-09. OfflineCreator's protected-resource metadata names exactly three supported scopes: `models`, `read`, and `generate`. Because this page has monthly freshness, recheck the metadata and the published package before relying on the matrix after 2026-09-17. Do not infer a production tool from an unpublished local build, an old screenshot, or a tool name suggested by a model.

Map every missing tool to its required scope

Treat the visible list as evidence, but apply the matrix only to a connection that supplies a non-empty scope set, such as the recommended remote OAuth path. There, if `list_models` is absent while account and generation tools remain, investigate `models`. If the five balance, history, status, wait, and download tools are absent as a group, investigate `read`. If `generate`, `upload_input`, and `cancel_generation` are absent together, investigate `generate`. A complete absence of all nine published tools points beyond one missing scope: confirm the endpoint, authentication, and discovery request.

For local stdio, version 0.1.2 calls `createOfflineCreatorServer(config)` without a scope option, and the server treats absent scopes as permission to register all nine tools. Do not use the matrix to explain missing stdio discovery entries; instead verify the package process and force a clean client rediscovery. The published package registers exactly those nine MCP tool names; a name outside that set cannot be restored by changing OfflineCreator MCP scopes.

models

list_modelsCatalog discovery and published credit-cost visibility.

read

get_credits · list_generations · get_generation · wait_generation · download_outputBalance, account history, status, bounded waiting, and completed-output URL retrieval.

generate

generate · upload_input · cancel_generationStart work, attach an image input, or cancel an eligible reserved generation.

Follow the symptom from discovery to the grant

Start with the client’s actual tool list, not with a prompt that assumes a tool exists. MCP defines `tools/list` as the discovery request and permits the returned set to vary with authorization, including returning only tools allowed by the caller's granted scopes. Therefore, a partial OfflineCreator list can be a valid scope-filtered response on a remote connection that supplies scopes. Record the endpoint, connection type, package version when using stdio, and exact visible names before changing anything.

Next, branch by mode. For remote OAuth, compare the missing names with the three supported groups and reconnect for only the permissions the workflow needs. For local stdio, the published entry point does not pass a scope set into tool registration, so missing names require process, package, configuration, or rediscovery checks rather than a broader key. Mixed individual omissions also do not match the published group filter and deserve a clean rediscovery before any credential change.

Finally, reconnect or reload the server through the client's normal control and request tool discovery again. Verify success by reading the newly returned names. Do not test recovery by starting a paid generation: `list_models` is the narrow verification for `models`, while a visible `generate` name verifies discovery of the `generate` group without spending credits.

Interpret a short tool list without overcorrecting

On a scope-filtered remote connection, only `list_models` visible matches the `models` group; read tools visible but generation tools absent matches a missing `generate` group; and generate tools visible but read tools absent matches a missing `read` group. Add only the scope required by the intended workflow rather than replacing the credential with an unrestricted one. These patterns do not diagnose local stdio, where version 0.1.2 registers all tools because its entry point supplies no scope set.

If all nine package tools are present but the model still says a tool is unavailable, separate host behavior from server discovery. Confirm that the host exposed the refreshed MCP list to the current conversation or agent, then begin a new client session if that host requires one. If the list itself is empty, return to endpoint, authentication, and transport diagnostics instead of treating the empty response as proof that every scope is missing.

The current MCP authorization specification says a server's `WWW-Authenticate` scope challenge is authoritative for the operation that produced it. During reauthorization, clients should include the challenged scopes alongside previously granted scopes so that gaining one permission does not discard another. This standards rule supports incremental elevation, but it does not prove that every client exposes the same reauthorization interface.

Recover with the smallest permission change

1. Capture the current `tools/list` result or the client’s visible tool names. 2. Identify remote OAuth or local stdio. 3. For a scoped remote connection, mark each expected name as `models`, `read`, or `generate`, then reconnect with only the task's required permissions. 4. For local stdio, do not broaden the key to repair discovery; verify the `npx` process, package version, client configuration, and clean restart. 5. Reload the connection and rediscover tools. 6. Verify the expected names appear before attempting the task.

Stop if the recovered names do not match the matrix. Do not repeatedly reconnect, broaden scopes, or regenerate keys without a changed observation. Preserve a redacted trace containing connection type, endpoint hostname, package version where applicable, expected tool, visible tools, requested scope group, and post-reconnect result. Never include bearer tokens, API keys, authorization codes, cookies, or signed output URLs.

The OfflineCreator setup page recommends browser OAuth for the remote endpoint and says a configured client can inspect tools authorized by its OAuth connection or fallback personal API key. That supports testing discovery after a grant change; it does not authorize a model to approve consent, reveal credentials, or choose broader access without a human decision.

Choose the next diagnostic from the observed result

Use the troubleshooting directory if no tools appear or the connection never completes. Move to the connection-closed guide when the MCP process or transport exits before discovery. Use the stdio startup guide when `npx @offlinecreator/mcp` terminates locally. Stay on this page when the connection is healthy and the missing names align with the `models`, `read`, or `generate` groups.

Keep this page limited to scope-filtered discovery

This page owns one symptom: an otherwise connected OfflineCreator MCP server exposes fewer tools than expected, and the observed names can be compared with the published scope-filtered registry. It does not claim that every missing tool is a scope problem, that every MCP client refreshes tools in the same way, or that an expanded grant fixes authentication, transport, package startup, model availability, credits, or generation failures.

The last30days run completed with the tracked plan and returned 22 items, but Digg was rate-limited, Instagram errored, Reddit was only partial after HTTP 429, X was not configured, and GitHub returned no results. Zero retrieved items were relevant to OfflineCreator tool visibility. No community anecdote is used for product behavior. The scope matrix instead relies on current first-party OAuth metadata, the immutable public 0.1.2 package, the current Studio setup page, and current MCP specifications. Consolidate this page into the troubleshooting directory if that page-specific registry can no longer be verified.