Generate video, image and audio ads from the AI assistant you already use — in your own account, against the credits you already hold. Nothing to install, no second bill, and every generation is quoted before it is charged.
Paste this into Claude, Cursor, Windsurf or any agent that can edit its own MCP configuration — it wires up the server itself and hands you the sign-in.
Add Creator City to this environment's MCP configuration: a remote MCP server named "creatorcity", URL https://www.creatorcity.ai/api/mcp, streamable HTTP transport, no API key — authentication is OAuth, handled in the browser. Use this client's own MCP config format or commands, and do not overwrite an existing server with the same name — stop and tell me instead. Start the connection, then pause while I complete the Creator City sign-in and approval in the browser. Once connected, list the available Creator City tools. Never run a generation without quoting its credit cost and asking me first.Claude takes the server URL and an OAuth client ID. Leave the client secret blank — this is a public client, and the ID is the same one for everybody.
https://www.creatorcity.ai/api/mcp8494db35-629d-4016-9ef4-349a4e4d473aIn Claude, open Settings → Connectors → Add custom connector, name it Creator City, and paste both fields.
Open Claude connector settingsThe client ID is worth entering: without it Claude registers a fresh connection every time it connects, and your connected-apps list fills with lookalike entries.
Claude sends you here to sign in with your normal account, then shows what the connection allows. Approve it once and ask Claude for an ad.
Create your accountClients other than Claude register themselves rather than using the published client ID, so each fresh connection adds an entry under Connected apps in your account. That is normal, and removing one there signs it out immediately.
You describe the ad in your assistant. It plans, quotes the exact cost, and only then generates — the work lands in your Creator City asset library.
I'll shape the product benefit into a natural creator concept, write a short script, then upload your product photo as the reference and price the render before anything is charged.
Generate a 9:16 UGC video from the attached product photo. Open with a relatable problem, show the unboxing hands-on, and finish with a casual piece-to-camera recommendation.
Your UGC ad is done and filed in your asset library — concept, script, creator performance and native captions, at exactly the quoted price.
Exactly what a connected assistant can do, spend and reach — and how to cut it off.
get_accountlist_workspaces | Who is connected, the credit balance and plan, and any team workspaces work can be billed to. |
list_modelslist_assetsupload_reference | The models available with what each accepts, and the library material to generate from. Uploading spends nothing. |
quote_image_generationquote_video_generationquote_audio_generation | Price a generation before it runs and report the balance it would leave. These never charge anything. |
generate_imagegenerate_videogenerate_audio | Render the work and file it in your asset library — from a prompt, or from your own assets. These spend credits. |
list_generationsget_generation_status | Find recent work and check whether a render has finished. |
Credits come from the balance already on your account — connecting an assistant creates no separate subscription, balance or bill. Before anything is charged the assistant must ask for a quote, and it hands that quoted figure back to generate. If the price changed in between, the generation is refused rather than charged differently; if a generation fails, the credits come back automatically.
It can generate from what is already in your library — an image as a video's opening frame, a product photo, one of your own clips — found with list_assets and named by id. The quickest way to add material is uploading it on your asset library; an assistant can also use upload_referencewhen it can actually read the file's bytes.
Team billing: if you hold a seat in a Team workspace, the assistant can bill that workspace by naming it. Work is billed to you personally unless a workspace is named, only workspaces you actually hold a seat in can be billed, and per-member monthly allowances still apply.
Approving the connection issues an access token that acts as you: it can read your account and asset library and spend your credits on generations. It cannot change your password, your billing details or your plan.
The approval screen shows the domain the token will be sent to — the one fact an app cannot fake, unlike its name. Apps Creator City recognises are labelled verified; unverified means only that we have not reviewed it.
To remove an assistant, open your account settings and find Connected apps. Removing one signs it out immediately — it does not wait for the token to expire.
Something off? Email hi@creatorcity.ai with the account address and roughly when it happened — assistant generations are recorded separately from studio ones, so we can trace exactly what ran and what it cost. See also our Terms of Use, Privacy Policy and PDPA Notice.