Scale with agents
Connect MCP once, then scale with skills, automations, and on-demand templates.
You already locked a face, batched stills, built carousels, and — on Presence — published to Fanvue. This is the last Start here step: how you scale without living in the UI.
MCP connects Claude, Cursor, ChatGPT, and coding agents to your studio account. Same credits, same characters, same History — but you drive create and publish from the AI tool you already use.
Once connected, three levers compound: skills (reusable agent instructions), automations (scheduled runs), and templates (gallery workflows you can search or ask the agent to build). MCP is the pipe; those three are how output keeps moving while you focus on the next batch.
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.
Copy theconnector URL
You'll paste this URL into Claude in the next step
https://mcp.unican.ai/mcpGo to Claude → Customize
In Claude desktop or claude.ai, go to Customize → Connectors. Name it UniCan and paste the URL.
Open Claude CustomizeAvailable tools
What you can do once connected
OAuth-secured access to your UniCan account. Endpoint: https://mcp.unican.ai/mcp
Scale levers
Skills
Skills are reusable instructions the agent follows across turns — your batch brief format, culling rules, caption tone, or Fanvue pricing habits. Pin skills in Chat so they load automatically, or ask the agent to save a new one after a workflow clicks.
Automations
Automations are scheduled agent runs: post a carousel on Tuesdays, refresh vault media weekly, or prep a slideshow draft before you wake up. Set the trigger once; the agent uses your characters, templates, and brand context on each run.
Request templates
Templates are reusable gallery workflows — photo sets, video lanes, slideshows. Browse Templates to run one, or ask Chat to search yours, inspect a slug, or create a new template from a brief you describe. Great when you want the same output shape every week without retyping the setup.
MCP vs in-app Chat
Same account either way. Use MCP when you want generation inside Claude, Cursor, Codex, or ChatGPT. Use in-app Chat when you want the studio skills UI, pinned instructions, and tool traces in one place. Many creators connect MCP for daily prompts and open Chat for heavy batch days.
Try an agent ask
Working with
You'll leave with
- You connected at least one external AI tool via MCP
- You know when to pin a skill vs run a one-off Chat turn
- You can tell Automations apart from manual agent sessions
- You can ask the agent to find or create a reusable template