Until now, the yesilcam command line and the yesilcam-mcp server handled a handful of jobs: images, video clips, fashion try-ons, Maket plans and a look at your library. Version 0.3 changes the scope. Every studio is now available from a terminal and from AI assistants that speak MCP, such as Claude Code, Claude Desktop, Cursor, VS Code and Windsurf: 131 operations across Image, Film, Animation, Cinema, Design, Website, Fashion Try-On, Maket and AI Influencer Studio. Same account, same token balance, same prices as the web app.

What is new in 0.3?

  • All studios. Story to Film and Flow, 25 animation styles including Ink Landscape and Inkmation, Cinema Studio export, narration and subtitles, Design Studio posters with print-ready export, Website Studio sites, Website Promo videos, Assemble / Disassemble, the full Fashion Try-On set, Maket plans from photos and photoreal renders, and AI Influencer Studio with long videos and automations.
  • One catalog, two interfaces. Every MCP tool has an identical CLI command, generated from the same catalog. What you try in a conversation, you can put in a script word for word.
  • A price before every charge. Anything that spends tokens first returns a quote and charges nothing. The assistant asks you, and only your yes starts the work.
  • API keys. Create a key in Account → Developer with Read only or Read and create access and a validity of 30, 90 or 365 days or no expiry. Keys cannot pay, buy tokens, delete the account or create other keys.
  • Waiting and downloading. Long jobs report progress, and the tools can wait for the result and save it to a folder you choose.
  • Fewer tools when you want them. Load only the studios you use with --studios, or only reading tools with --read-only.

What does it look like in practice?

You write to your assistant: "Plan a 60-second long video on three tips for better phone photos with my influencer, show me the storyboard and the total quote, and ask me before producing." The assistant calls the planning tool, which returns its own price first. You approve the planning. Sam writes chapters, scenes and shots, and the assistant shows you the storyboard and the production quote. You ask for a change in one scene, it saves the edited storyboard, and when you approve the quote the video is produced chapter by chapter.

The same steps from a terminal:

yesilcam longvideo plan --influencer-id 70 --topic "3 tips for better phone photos" --seconds 60 --format mixed --yes --wait
yesilcam longvideo get <id>
yesilcam longvideo produce <id> --yes

Or something smaller: "Design an A3 retro poster for a jazz night with the texts Jazz Night and Friday 21:00, and export a print-ready PDF." Two tools, two quotes, one PDF in your folder.

Who is it for?

  • People who already work with an AI assistant and would rather describe the result than click through each studio.
  • Agencies and studios that repeat the same production steps for many clients and want them in a script.
  • Developers who want to connect Yeşilçam Studios to their own tools, with a read-only key for reporting and a create key only where work should be produced.

What stays in the app?

Everything that concerns money and security: buying tokens and plans, billing, automatic top-ups, creating and revoking API keys, connecting social accounts and deleting the account. Also the parts that need a visual editor: Maket furnishing and landscape design, and the Cinema Studio timeline. Social publishing commands are included but report "coming soon" until publishing opens for your account.

How do I start?

Install the package with npm install -g https://yesilcamstudios.com/downloads/yesilcam-studios.tgz (Node 18 or newer), sign in with yesilcam login and connect your assistant. The setup guide walks through each step, including signing in with yesilcam login --password if you do not have a key yet. The token approval guide explains quotes and key limits, and the studio recipes give you commands to copy. The full tool list is on the Developers page.

Frequently asked

Is the CLI a separate subscription? No. It uses your existing account and token balance, and every operation costs what it costs in the app.

Which assistants work with it? Any client that supports MCP servers over standard input and output. Setup is documented for Claude Code, Claude Desktop, Cursor, VS Code and Windsurf.

Can my assistant spend tokens without asking? The tools return a quote first and are built to ask you before approving. For extra safety, set a limit with max_tokens, or use a read-only key.

Do I need to change anything if I used the earlier version? Install 0.3 the same way. The short commands of earlier versions, such as yesilcam balance and yesilcam tryon, still work, and API keys are now the recommended way to sign in.