Discover
List the current Studio models, workflows, and published credit costs before a paid call.







Connect an agent or the CLI to the same Studio catalog, credits, and signed quote flow you use in the browser—then generate with disclosed cloud models.
One interaction loop for Studio, MCP, CLI, and the API. Technical install steps stay below.
List the current Studio models, workflows, and published credit costs before a paid call.
Studio signs the option-aware credit quote and reserves that charge before work starts.
Submit the job, wait or poll for status, and download the completed output through the same account.
Jump from this setup hub into CLI task guides, client setup pages, and the dual payment rails for insufficient credits.
Check Node.js requirements and choose npx or a durable local install.
Route users by models, balance, generation, status, download, cancel, and top-up tasks.
PAYMENT-REQUIRED vs legacy insufficient credits
Distinguish legacy INSUFFICIENT_CREDITS from x402 PAYMENT-REQUIRED, then recover with Stripe or a wallet rail.
Add the OfflineCreator MCP URL in Cursor, connect with OAuth, then list models and generate. The recommended path stores no API key in mcp.json.
Connect the current Codex client without borrowing another client's config schema.
Settle a locked quote and keep generating
Related Studio pages: OfflineCreator Studio vs LocalForge: cloud or offline AI · AI video generator · AI 3D model generator · Video Creator · Community · Sora API replacement · Imagen 4 API shutdown and migration · Lyria 3 API
Published command pages, x402 runbooks, client setup guides, comparison pages, and hosted API notes.
OfflineCreator CLI task directory · Install and run the OfflineCreator MCP CLI · Animate an image with the OfflineCreator CLI · Authenticate the OfflineCreator CLI with a scoped API key · Cancel a generation and recover reserved credits · Check generation status from the command line · Check Studio credits from the command line · Download a completed generation from the CLI · Generate a video with the OfflineCreator CLI · Generate an image with the OfflineCreator CLI · List available image and video models from the CLI · List recent image and video generations from the CLI · OfflineCreator CLI JSON output and exit-code handling · Point the OfflineCreator CLI at a trusted API base · Preflight generation cost with the OfflineCreator CLI · Restrict CLI image uploads to an approved directory · Retry a CLI generation without creating duplicate work · Script a repeatable image generation workflow · Use OfflineCreator CLI in CI without leaking secrets · Wait for an OfflineCreator generation from the CLI
Pay-as-you-go · Diagnose 402 · Credit top-up · Stripe vs x402 · Wallet setup
OfflineCreator Cursor MCP setup · OfflineCreator MCP compatibility with Codex · Add OfflineCreator as a Claude custom connector · Configure OfflineCreator MCP in Hermes · Configure OfflineCreator MCP in VS Code and Copilot · Configure OfflineCreator MCP in Windsurf · Connect Claude Code to OfflineCreator MCP · How MCP clients reload configuration and cache tools · MCP client capability matrix for media generation · MCP client configuration file locations by operating system · MCP protocol-version compatibility across current clients · OfflineCreator MCP client setup directory · OfflineCreator MCP compatibility with Cline · OfflineCreator MCP compatibility with Goose · Set up OfflineCreator as a local stdio MCP server · Set up the recommended remote OAuth MCP connection · Use the API-key MCP fallback safely · Verify an OfflineCreator MCP client connection
OfflineCreator Studio vs LocalForge: cloud or offline AI · Claude Desktop vs Claude Code for OfflineCreator MCP · Cursor vs Claude Code setup for OfflineCreator MCP · Managed generation credits vs direct provider billing · MCP generation comparison and migration directory · MCP vs a native client integration for media generation · MCP vs CLI for image and video generation · MCP vs REST API for OfflineCreator generation · Migrate a provider-specific script to OfflineCreator REST · Migrate OfflineCreator from stdio to remote MCP · Migrate OfflineCreator MCP from API keys to OAuth · OAuth vs API keys for OfflineCreator MCP · OfflineCreator Studio vs using fal.ai directly · Polling vs webhooks for long-running media generation · Remote MCP vs a local CLI for generation automation · Remote OAuth MCP vs local stdio for OfflineCreator
Sora API replacement · Imagen 4 API shutdown and migration · Lyria 3 API
Choose your client, paste the OAuth configuration, and sign in to Studio in your browser. The same credits, model costs, moderation, and automatic refunds apply outside the browser.
OAuth is the recommended remote connection. Local stdio and the legacy API-key remote remain available through @offlinecreator/mcp.
.cursor/mcp.json or %USERPROFILE%\.cursor\mcp.json
{
"mcpServers": {
"offline-creator-studio": {
"url": "https://mcp.offlinecreatorstudio.com/mcp"
}
}
}Reload MCP servers, select Connect, and complete the Studio browser sign-in. No API key is stored in the file.
OAuth connections can be revoked from Settings. Keep fallback API keys out of URLs and source control.
Ask in natural language. Your agent selects Studio tools, shows the model and cost, then returns the finished media to your workflow.
I’ll carry one visual direction across a poster and a social motion asset, while choosing the right model for each format.
The models, provider, aspect ratios, and lowest published credit costs stay visible before either generation starts.
Your coordinated campaign assets are ready.
Made with disclosed models
Create faster without surrendering clarity—know where processing happens, who holds your media, and when credits come back.
Source files and outputs stay behind your account—not a public dump of every generation.
You always know which cloud model runs the job. No mystery APIs, no silent handoffs.
Reserved credits return when a generation fails, so privacy-minded creators aren’t punished for retries.
Studio is the transparent cloud path. LocalForge stays the on-device option when nothing should leave your machine.
Seedance 2.5 adds reference-guided video, image animation, and prompt-driven video to the Studio workflow.
No. MCP and CLI use the same paid Studio subscription credits as the web Studio. Every plan starts billed at checkout, with no free trial. Plus-alias addresses of a mailbox that already had a Studio subscription or trial cannot start another plan.
A configured MCP client can inspect available models and use the Studio generation workflow through tools authorized by your OAuth connection or fallback personal API key.
No. Remote OAuth does not require pasting a key. If you use the local stdio or legacy remote fallback, keep its API key only in secret configuration and revoke it immediately if it may have leaked.
Yes. Web, MCP, CLI, and API generations use the same account credit balance and published per-model costs.
Two shapes exist. A legacy insufficient-credits 402 is a human Stripe or Studio top-up signal. An x402 challenge also carries a PAYMENT-REQUIRED header so a configured agent wallet can settle USDC. See the 402 help guide and the x402 payments page.
Start at the CLI task directory for models, balance, generate, wait, download, and cancel workflows, or open the install guide for Node and npx setup.
No. MCP and CLI are interfaces to the cloud Studio service. Generation inputs go to the disclosed cloud provider for the selected model.
Subscribe to Starter, pick a disclosed model, and generate with private media delivery—plus an offline path when you need it.