One AI Character, Every Project: Souls in the MCP

Here is the workflow most people are stuck in. You have a character you like, so you keep a reference photo in a folder. Every time you want a new image, you open a tool, upload the reference, tune the settings, hope the face holds, and half the time it drifts anyway.

That is a lot of friction for something you do fifty times a week. The fix is to stop treating your character as a file you carry around and start treating it as a saved identity the tool already knows. That is what a Soul is, and once you wire the Apatero MCP into Claude, reusing that character becomes a sentence in a chat.

Quick Answer: A Soul is a persistent character saved inside Apatero, a locked face and identity held server-side. Once you have created a Soul, the Apatero MCP lets you generate that same person into any new scene from a Claude conversation without re-uploading a reference. You list your Souls, name the one you want, describe the scene, and the exact character comes back. One saved identity, reused across every project, driven from chat.

What a Soul Actually Is

A Soul is a saved persona inside Apatero. Think of it as the character's identity stored as a reusable asset rather than a reference file you manage yourself.

The important part is that it lives server-side. You are not keeping a folder of reference photos and hoping you grabbed the right one. The face and identity are held by the studio, tagged with a name, and available to any generation you fire. That is the same character-lock idea behind holding a character across fifty images, except the lock is permanent and portable instead of something you rebuild each session.

Because the identity is saved, consistency stops being a per-session battle. You do not defend the face with prompt tricks and weight tuning every time. The face is already decided. You just call it.

How Do You Create a Soul?

There are two paths in, and both end with a saved character you can reuse forever.

The first is from reference photos. If you already have a character, real or generated, you create a Soul from those images and the studio saves the identity. This is the move when you have a specific look you want to lock and keep.

The second is to generate a fresh character. You can spin up a new influencer portrait set from scratch, and the process saves the resulting Soul for you automatically. This is the move when you are starting a persona from nothing and want the studio to both design and save it in one step. It pairs naturally with building a character sheet from a single reference when you want a defined look before you lock it.

Either way, the output is the same. A named Soul sitting in your account, ready to be dropped into any scene. You do this part once per character.

Generating That Character From Claude

This is where the MCP earns its place. Once the server is connected, your saved Souls are visible to Claude, and putting that character into a new scene is a plain-language request.

You ask Claude to list your Souls first so you can see what is available by name. Then you name the one you want and describe the scene. Generate my persona in a rooftop bar at golden hour, dressed up, holding a drink, candid. Claude calls the generate-with-Soul tool, the same locked character comes back in that new setting, and the result lands with a full-resolution link.

The mental shift is real. Your prompt is now entirely about the scene. Setting, wardrobe, mood, framing, light. None of it is about who the person is, because that is handled by the Soul. That is why prompt work after a Soul is locked leans on expression clauses and wardrobe looks rather than face-defending boilerplate.

If you have never connected the server, the four install paths cover every client, and the npx bridge in Claude Code is the usual pick for developers. The hosted connector URL works everywhere including the phone.

Why One Soul Beats a Folder of References

The real unlock is not convenience, it is reuse across projects. A saved character is not tied to one content line. It is one identity you can deploy anywhere.

The same Soul can be your Instagram persona this week, the model in a product catalog shoot next week, and the face of a short video the week after. You are not rebuilding the character for each context. You are reusing one locked asset across every context, which is exactly the economics the revenue stack depends on.

Here is the difference laid out plainly.

A folder of reference photos is a character you have to reassemble constantly. A Soul is a character that already exists. Multiply that across the hundreds of generations a real operation runs and the difference is enormous.

Fitting Souls Into Real Production

Once you think in Souls, production gets simple. Build the character once, then spend all your time on scenes.

The clean loop is to create the Soul in the studio, where the design and lock work benefits from a real UI, then produce against it from chat, where describing scenes in plain language beats clicking through setup screens. This is the build-in-studio, run-from-chat pattern, and it scales because the expensive part, defining the character, is done exactly once.

You can also run more than one Soul. Different personas for different audiences, all saved, all callable by name. When a scene needs two of your characters together, the same identity-lock idea extends to multi-character scenes with two locked identities. And because generation draws from your credit balance the same way regardless of how you trigger it, you can check that balance from the chat before a big run.

FAQ

Do I Have to Recreate My Soul Each Session?

No. A Soul is saved server-side, so it persists across every conversation, session, and device. You reference it by name and the locked identity comes back with no re-upload. Creating it is a one-time step per character.

Can One Soul Be Used for Totally Different Projects?

Yes, and that is the main advantage. A single saved character can appear in your social feed, a product shoot, and a video, all from the same identity. You reuse one locked asset instead of rebuilding the character for each content line.

What Do I Actually Say to Claude to Generate?

Name the Soul and describe the scene. Something like generate my persona in a sunlit kitchen making coffee, casual sweater, candid. Claude calls the generate-with-Soul tool and the same character comes back in that setting. The prompt is about the scene, not the person.

Is a Soul the Same as a Trained LoRA?

They solve the same problem, character consistency, by different means. A Soul is a hosted, saved identity you call by name with no training pipeline to manage. I compared the hosted-versus-trained tradeoff in Apatero versus Civitai LoRAs.

Can I Make Video From a Soul Too?

Yes. The same saved character animates into short clips, so a Soul is not limited to stills. Video renders take minutes, so kick one off from the chat and check status later. The still-to-talking-clip workflow covers the motion side in detail.

What If the Character Looks Slightly Off in One Image?

Regenerate that single shot or nudge the scene wording. Because the identity lives in the Soul rather than the prompt, an off image is almost always the scene description, not the character. One reroll usually fixes it.

Wrapping Up

A reference photo in a folder is a character you have to reassemble every time you use it. A Soul is a character the studio already holds, locked and callable by name, and the Apatero MCP turns calling it into a sentence in a Claude conversation.

Create the Soul once, from reference photos or a fresh portrait set. Then reuse that one identity across every project, describing only the scene while the character stays constant. Build in the studio, run from chat, and stop re-uploading the same face into every tool you touch.

Create your first Soul in Apatero, first generation free →