Run Apatero From Claude With npx apatero-mcp

The most requested Apatero feature of the year was not a model. It was a location. People wanted the studio inside Claude, where they already plan content, write scripts, and argue with their outlines.

That is what the Apatero MCP does, and the npx bridge is the fastest way to wire it into Claude Code and Claude Desktop. This post is the full walkthrough. What the bridge is, why there is no Python involved, setup for both clients, your first generation from chat, and how auth works.

If you just want every install option on one page, the MCP install guide covers all four paths. This post goes deep on one of them.

What npx apatero-mcp Actually Is

The apatero-mcp package on npm is a small Node bridge. When Claude launches it, the bridge connects your Claude client to the Apatero studio and exposes twenty tools to the conversation.

Those tools cover the real studio, not a demo slice. Image and video generation, Souls for persistent characters, the influencer pipeline with Insta Dump batches, talking avatars, illustrated stories, plus utility tools for credits, models, and your gallery.

The important mental model is that nothing generates on your machine. Apatero is a hosted AI creative studio. The bridge passes your requests up and your results back. Your laptop contributes a network connection, not a GPU.

That is also why the install is boring, in the best way. There is no model download, no weights folder eating 40 GB, no CUDA version roulette. The bridge is tiny because the studio is elsewhere.

Why There Is No Python in This Path

Plenty of MCP servers ship as Python packages, and Python is exactly where non-Python people get hurt. Wrong interpreter, broken virtualenv, a pip install that works on the blog post's machine but not yours.

The npx path skips the whole category. If Node is installed, npx fetches and runs the current version of the bridge on demand. There is nothing to activate and nothing to update by hand, since each launch resolves the latest release.

Node people get the same courtesy in reverse, by the way. If your stack is Python and uv, the studio also ships as apatero-studio-mcp on PyPI, runnable with uvx. Same server, different runner. Pick whichever runtime already lives on your machine.

Set It Up in Claude Code

One command registers the bridge with Claude Code.

claude mcp add apatero -- npx apatero-mcp

That is the entire setup. Open a new Claude Code session and the Apatero tools are available. You can confirm with the /mcp command inside Claude Code, which lists connected servers and their status.

The first time a tool runs, the bridge opens a browser window so you can sign in to your Apatero account. Approve it once and the session is remembered. If you do not have an account yet, signup takes a minute and your first generation is free.

Set It Up in Claude Desktop

Claude Desktop reads its MCP servers from a JSON config file. Add the same bridge there.

{
  "mcpServers": {
    "apatero": {
      "command": "npx",
      "args": ["-y", "apatero-mcp"]
    }
  }
}

The file is claude_desktop_config.json, reachable from Claude Desktop's settings under the developer options. Paste the block, save, and restart the app. Desktop only reads the config at launch, so the restart is not optional.

After the restart, the Apatero tools show up in the tools menu of a new conversation. Same browser sign-in on first use, same remembered session afterward.

Your First Generation From Chat

Open a fresh conversation and ask for something concrete.

"Generate an image of a ceramic robot tending a greenhouse at dusk, cinematic lighting, 16:9."

Claude asks permission to run the Apatero tool. Approve it. A few seconds later the image renders inline in the conversation with a full-resolution link attached. It is also sitting in your Apatero gallery, exactly as if you had made it in the app.

Now push it further, because this is where chat starts beating the tab-switching workflow. Ask for three variations. Ask to remix the best one with warmer light. Ask to animate it into a short video clip.

Then try the tools that carry real production weight. Create a Soul from reference images and generate the same character across ten scenes. Kick off an Insta Dump batch and check its status while you keep writing. Turn a portrait into a talking avatar with a script you drafted two messages earlier.

The conversation becomes the pipeline. Planning, prompting, reviewing, and iterating all happen in one place, and the gallery quietly collects everything.

Consistency workflows translate especially well here. If you have read the character lock walkthrough, the same discipline applies from chat. Lock the identity first, then vary scenes, and let the Soul hold the face steady across the batch.

Check Status, Balance, and the Gallery

Three utility tools keep longer sessions honest.

Generation status polls a specific render, which matters for video since renders take minutes. Recent generations lists your latest results when you want to pull an earlier image back into the conversation. Credit balance tells you what you have left before you start a batch.

Ask in plain language. "How many credits do I have" and "show me my last five generations" both route to the right tools. You never memorize tool names, Claude picks them.

OAuth or an API Key

The bridge supports two ways to prove you are you.

OAuth is the default and the right answer on a personal machine. First tool call opens the browser, you sign in, done. No secrets land in any config file, and you can revoke the session from your Apatero account at any time.

API keys exist for everywhere a browser prompt is unwelcome. Servers, CI jobs, shared automation. Create one at app.apatero.ai/developer, and note that real keys start with ap_live_. Then pass it through the environment when you register the bridge.

claude mcp add apatero --env APATERO_API_KEY=ap_live_your_key -- npx apatero-mcp

In the Claude Desktop JSON, the same key goes in an env block on the server entry. Treat keys like passwords. Rotate them from the developer page if one leaks, and prefer OAuth on machines where a human is present.

Where to Go From Here

The npx bridge is one of four install paths. The hosted connector URL needs no install at all, uvx serves the Python crowd, and Homebrew ships a standalone binary. The MCP page lists all four with copy-paste snippets, and a follow-up post comparing them lands here on the Journal next week.

If your next step is content production, the selfie to fifty-pack build shows what a persona pipeline looks like at volume. Every step of it is now runnable from a Claude conversation.

Set aside ten minutes tonight. Install the bridge, generate one image from chat, and feel how short the distance between idea and render has become.

Create your free Apatero account, your first generation is free →