This page describes the first version of the package. For version 0.3, with every studio, API keys and price approval, see the new setup guide.

With the MCP server connected, Claude can operate the studios as tools: create images and videos, run try-ons, read the library and your characters, analyze and file floor plans, check the balance and quote prices. You describe the outcome; Claude sequences the calls. We use it daily, and the sessions that work share a shape: the assistant does the cheap, repetitive part on its own and asks before the expensive part.

What the server exposes

The yesilcam-studios package ships two commands. yesilcam is the CLI for the terminal; yesilcam-mcp is the server that speaks the Model Context Protocol. Both use your normal account and the same credit wallet. The tools mirror the app: image and video creation on a chosen tier, fashion try-on, job status, library assets, characters, balance, pricing, and Maket analyze and save. Nothing is exposed that you could not do yourself in the app, and nothing costs a different amount.

A good session

"Storyboard these six scenes on draft, show me the frames, then produce the two I pick on standard." The assistant creates six draft image jobs, waits, returns the URLs, and asks which two to produce. You answer, it runs the two standard jobs and returns them. Total human time: two decisions. Total credits: six drafts and two standards, and the pricing tool let it quote both figures before it started.

Another one we like: "Upload the garment photos in this folder, run each on model 77, and tell me which ones came back with a warning." The try-on tool runs one job per file, the job status tool reports each, and the assistant summarises. The ledger records provenance exactly as it would from the app.

What it will not do

Spend without a cost being visible. Every tool reports the job and its status; the pricing tool is there so the assistant can quote before it commits. The wallet is the same wallet, the price table is the same table, and a failed job is refunded the same way. There is no back door for automation, and we would not want one.

Keep a human at the tier change

Draft work can be autonomous: frames to look at, prompts to test, plan analyses to run. Standard and cinema production should wait for your yes. Say so in the instructions you give the assistant and it will ask. The rule is the same one we apply to ourselves: the cheap end of the pipeline is for exploring, the expensive end is for deciding, and a decision needs a person.

  • Let it storyboard, upload, analyze, list and quote on its own.
  • Ask it to confirm before any standard or cinema video, any character bible, and any batch over a size you name.
  • Ask it to report the balance at the start and the end of a session.

Setup

Install the package globally with npm and sign in with yesilcam login. Run yesilcam login --json and copy the token. Add the server to Claude Code with claude mcp add yesilcam -e YESILCAM_TOKEN=<token> -- yesilcam-mcp. Claude Desktop reads the same server from its configuration file; yesilcam mcp prints the snippet to paste. The guide has the exact commands. Keep the token private; it grants full access to the account.

Things we learned

Give the assistant the job ids. When it reports "job 4412 finished", keep that in the conversation; it is how you find the asset in the library and how the ledger explains the charge. Ask for sequential runs when order matters; the queue is shared with the app and parallel jobs finish in whatever order they finish. And be explicit about tiers in every request. "Make an image" defaults to a reasonable tier, but "make a draft image" costs less and is what you usually mean during exploration.

Where it fits

The MCP route is for people who think in outcomes and want the sequencing done for them. The CLI is for people who think in pipelines and want to own the script. The app is for people who want to see every frame. All three read the same library and spend from the same wallet, so you can start a film in one and finish it in another.

Frequently asked

Can the assistant spend my whole allowance by accident? Only if you let it run production without confirmation. Tell it to quote and ask before any standard or cinema job, and it will. The balance tool lets it check before every batch.

Does the server work with other MCP clients? It speaks the Model Context Protocol, and the guide documents Claude Code and Claude Desktop, which are the two we test.

Can it edit a film's scenes? It can create images and videos, read your library and characters, and file plans. Scene cards and the timeline are edited in the app; use the assistant to produce the pieces and the app to arrange them.