The yesilcam-studios package brings Yeşilçam Studios to your terminal and to AI assistants that speak MCP (Model Context Protocol). It installs two commands: yesilcam, the command line for scripts and pipelines, and yesilcam-mcp, a server that lets Claude Code, Claude Desktop, Cursor, VS Code, Windsurf and other MCP clients use the studios as tools. Version 0.3 covers every studio with 131 operations: Image, Film, Animation, Cinema, Design, Website, Fashion Try-On, Maket and AI Influencer Studio, plus your account and library. It uses the same account, the same token balance and the same prices as the web app. This guide takes you from installation to a first working conversation. For an overview, see the Developers page.

What do I need?

  • Node.js 18 or newer, which provides the npm command.
  • A Yeşilçam Studios account. Free, Basic and Pro all work; some features need Basic or Pro, exactly as in the app.
  • A terminal. For the assistant part, an MCP client such as Claude Code, Claude Desktop or Cursor.

How do I install it?

Install the package globally from the Yeşilçam Studios site:

npm install -g https://yesilcamstudios.com/downloads/yesilcam-studios.tgz
yesilcam --version
yesilcam --help

yesilcam --version should print 0.3.0. yesilcam --help lists the command groups, one per studio, and yesilcam <group> --help (for example yesilcam image --help) shows the commands and options of each group.

How do I sign in?

The recommended way is an API key. You create it in the app under Account → Developer. When you create a key you choose:

  • A name, so you can tell your keys apart later (for example "Laptop" or "Build server").
  • Access: Read only (balance, prices, library, job status) or Read and create, which can also start work and spend tokens.
  • Validity: 30, 90 or 365 days, or no expiry.

The key starts with ysk_ and is shown only once, so copy it straight away. Then run yesilcam login and paste it. The input is hidden, the key is never printed, and it is saved in ~/.config/yesilcam/config.json with permissions that only your user can read. Check that it worked:

yesilcam login
yesilcam account show

If you do not have a key yet, you can sign in with your email and password instead: yesilcam login --password. This saves a session in the same file. On a server or in CI, do not store anything on disk: set the key in the YESILCAM_API_KEY environment variable, or pipe it in with yesilcam login --key-stdin.

How do I connect Claude Code?

One command registers the server:

claude mcp add yesilcam -- yesilcam-mcp

The server reads the credentials saved by yesilcam login, so there is no key in the command and none in Claude Code's configuration.

How do I connect Claude Desktop, Cursor, VS Code or Windsurf?

These clients read MCP servers from a JSON configuration file: claude_desktop_config.json for Claude Desktop, ~/.cursor/mcp.json for Cursor, and the MCP settings of VS Code and Windsurf. Add this entry:

{"mcpServers":{"yesilcam":{"command":"yesilcam-mcp","args":[]}}}

If the file already lists other servers, add "yesilcam" inside the existing mcpServers object rather than creating a second one. Restart the client afterwards. You do not have to remember any of this: yesilcam mcp prints the ready-made snippets for every client.

Can I load fewer tools?

Yes. 131 tools is a long list, and if you only use a few studios a shorter list keeps the assistant focused. Pass the studios you want in args:

{"mcpServers":{"yesilcam":{"command":"yesilcam-mcp","args":["--studios","image,film,influencer"]}}}

The available names are image, film, animation, cinema, design, website, fashion, maket and influencer. Account and library tools are always loaded. Add "--read-only" to load only the tools that read, for example for an assistant that should report on your library but never start work.

What should my first conversation look like?

Start with something free: "What is my Yeşilçam token balance, and what does a draft image cost on my plan?" The assistant calls the balance and price tools and answers. Then try a small job: "Make a draft 16:9 image of a lighthouse at sunset. Tell me the price first, then save it to my desktop." The assistant first receives a quote and nothing is charged. It shows you the price, and only after you agree does it call the tool again with approval, wait for the image and download it. The token approval guide explains this step in detail, and the studio recipes show what to ask for next.

Troubleshooting

  • "command not found". The folder where npm puts global commands is not on your PATH. npm prefix -g shows the location; add its bin folder to PATH and open a new terminal.
  • "not signed in" (exit code 2). No saved credentials were found. Run yesilcam login again, or check that YESILCAM_API_KEY is set in the environment where the command runs.
  • The assistant does not show the Yeşilçam tools. Restart the client after editing its configuration. If it still cannot start the server, write the full path of the command (shown by which yesilcam-mcp on macOS and Linux) as "command".
  • The key is rejected. It may have expired or been revoked. Create a new key in Account → Developer and run yesilcam login again.
  • Creating is refused, or the assistant has no creating tools. The key was created with Read only access, or the server was started with --read-only.

Frequently asked

Does the CLI or the MCP server cost extra? No. Operations cost exactly what they cost in the app, with your plan's prices, and nothing is charged before you approve a quote.

Does my key end up in the assistant's configuration? No. The configuration only names the command yesilcam-mcp; the server reads the key that yesilcam login saved on your computer.

How do I sign out of a computer? Run yesilcam logout. It removes the saved credentials from that computer. An API key keeps working elsewhere until you revoke it in Account → Developer.

Can I use the app and the CLI at the same time? Yes. Work started from the terminal or an assistant appears in the same library and uses the same balance as the app.