OfflineCreator Cursor MCP setup

Use a dated Cursor acceptance checklist

Record whether the configuration is project-specific or global, then restart or reload the MCP server from the Cursor build being tested. Confirm the server appears in Customize, complete the browser OAuth flow, and inspect the tools Cursor discovers. The expected OfflineCreator authorization surface is models, read, and generate; the package currently maps those permissions to model and balance discovery plus generation-lifecycle tools. Do not assume an older screenshot or another client's setup proves the current Cursor flow.

Perform read-only checks first: list models and read the account credit balance. Before a paid test, choose an inexpensive approved model, confirm its displayed credit cost, and write down the prompt and maximum attempts. Submit once, retain the returned job identifier, check status, and retrieve the completed result. If Cursor reports a timeout, reconcile the recorded or recent job instead of immediately starting a duplicate.

Finish by revoking the test connection in Studio settings and confirming protected tools no longer work. Capture the Cursor version, operating system, configuration location, observed OAuth result, visible tools, and revocation result in the acceptance record. This research pass verifies the current schemas and first-party documentation but did not execute that desktop test, so the page remains support-qualified rather than claiming confirmed compatibility for a specific build.

Put the remote MCP URL in Cursor, then connect with OAuth

Cursor's current MCP documentation uses the mcpServers object for custom servers and supports remote Streamable HTTP URLs with OAuth. Put a project-specific configuration in .cursor/mcp.json or a global configuration in ~/.cursor/mcp.json. For OfflineCreator, add an offlinecreator entry whose url is https://mcp.offlinecreatorstudio.com/mcp. Do not add an API key, header, or query parameter to the recommended OAuth configuration.

Reload MCP servers in Cursor, select Connect for OfflineCreator, and complete Studio sign-in and consent in the browser. The product page publishes the same JSON shape for Cursor and says no API key is stored in that file. This is documentation-backed setup guidance; this research pass did not operate the Cursor desktop UI.

Use the fallback only when OAuth cannot be used

OfflineCreator also documents a local stdio fallback using npx and a scoped API key. Cursor supports stdio entries with command, args, and environment variables. Keep any fallback key in secret configuration, never in a URL or repository, and revoke it if it may have leaked. The legacy remote header path is a separate fallback and should not be confused with the recommended endpoint.

The retrieval pass returned 24 Reddit records but remained partial after an HTTP 429 response. X was absent because optional credentials were not configured, and Instagram failed with repeated HTTP 404 responses. Eleven YouTube records were retained even though none fell inside the requested date window, and several duplicated the same undated videos. No community or media item established successful OfflineCreator setup on a specific Cursor build. Compatibility therefore remains support-qualified until a dated hands-on acceptance test is completed.

Verify discovery and the authorized tool scope

After connection, ask Cursor to list the available OfflineCreator tools or inspect them in Customize. The live protected-resource metadata advertises models, read, and generate scopes. The package documents tools for model and credit discovery, generation, source-image upload, status, bounded waiting, recent jobs, completed-output download, and cancellation; what appears should match the authorization granted to the connection.

Begin with list_models and get_credits before a paid generation. If the server is missing or stale, verify which configuration location Cursor loaded, reload the server, and inspect MCP Logs in Cursor's Output panel. Do not repeatedly submit generation while troubleshooting an uncertain response; retain the job identifier and reconcile status first.

Related reading