Presence Studio logo
Presence Studio

More scale levers

Turn one MCP connection into repeatable workflows that keep producing.

You already locked a face, batched stills, built carousels, and — on Presence — published to Fanvue. The next step is to operate that workflow from the external AI tool where you already plan and work.

MCP connects Claude, ChatGPT, Cursor, Codex, and other supported clients to your studio account. The client can use the same credits, characters, assets, models, and History, so you do not need to rebuild context in another interface.

Once the connection works, scale comes from making the work repeatable: preserve a proven brief, schedule recurring production in a client that supports automation, and reuse templates instead of rebuilding every batch. MCP is the pipe that keeps those workflows attached to the studio.

Pick your AI tool, copy the connector steps, and sign in once. OAuth ties the external agent to your account and credits — same balance as the studio.

1

Copy theconnector URL

You'll paste this URL into Claude in the next step

https://artificialinfluence.tech/mcp
2

Go to Claude → Customize

In Claude desktop or claude.ai, go to Customize → Connectors. Name it Presence Studio and paste the URL.

Open Claude Customize
3

Connect, sign in and start

Sign in, then ask Claude to generate an image or video

ClaudeStart creating

Available tools

What you can do once connected

OAuth-secured access to your Presence Studio account. Endpoint: https://artificialinfluence.tech/mcp

get_accountlist_modelslist_generationssearch_generationsget_generationgenerate_imagegenerate_videogenerate_audio

Scale levers

Preserve proven instructions

Save the brief that already works in your MCP client: character rules, shot count, aspect ratio, culling standards, caption voice, and publish requirements. Reusing a complete operating brief is faster and more consistent than reconstructing it every session.

Connect MCP

Schedule through an MCP workflow

When your client supports scheduled runs, use the MCP connection for recurring batches: prepare a carousel every Tuesday, refresh a weekly content queue, or generate drafts before review. Keep publishing behind a review step until the workflow is proven.

Open Automations

Reuse output structures

Templates give the MCP client a stable output shape: a photo set, video lane, slideshow, or carousel structure. Search for an existing template first, then adapt it only when the recurring job genuinely needs a different structure.

Open Templates

Keep the studio as the source of truth

Your external client drives the work, but the studio remains the source of truth for credits, characters, assets, and generation History. Review results there, save the keepers, and refine the external workflow from what actually performed.

Open MCP