FanPresence × your agent

Let your AI agent run your creator business.

Your agent can see what is working, test a better approach and make changes you can trace. Connect the assistant you already use.

Connect your agent Start free

Connect in three steps

1. Copy the prompt

Open Extra → MCP and copy the setup prompt into your agent.

2. Sign in

Your agent opens Presence. Sign in and approve its permissions.

3. Ask your agent

Start with a business question. Your agent loads context and proposes a test.

What agents can do

Full vault visibility

Browse folders, find forgotten inventory, inspect sales and restock your offer tiers.

Versioned persona

Change voice, offers and reply schedules with an author, a reason and a rollback path.

Test before going live

Try draft changes against fan archetypes and private copies of real conversations.

Safe rollouts

Start with a canary of new fans, compare results, then promote or restore the baseline.

Funnel analytics

Follow CTAs, clicks, offers and recorded purchases. See unknown attribution clearly.

Learnings that stay

Record your hypothesis, metric and observed result so the next change starts with evidence.

Campaigns and follow-ups

Inspect nudges and audiences, save drafts, manage schedules and review delivery history separately for Fanvue and Telegram Business.

Content and customs

Inspect Studio history and generated asset references, manage custom requests and organize vault captions, tags and pricing.

Integration readiness

Inspect connection state and webhooks, synchronize provider data and reconcile operation receipts.

Control stays with you

Configuration changes are versioned. Vault edits have undo protection. Coach changes wait for your approval; authorized external agents apply changes directly and leave an audit trail.

Live messaging is off by default and requires both account permission and a dedicated agent permission. Studio uploads and generated outputs receive minor-safety checks; failed checks block those Studio assets. Vault media is outside that moderation flow.

Disconnect an agent whenever you need to stop its access. Privacy filters mask identifying fan fields and common contact details in conversations.

Copy, paste, connect

Add the server URL, then authenticate from your agent. Presence asks you to sign in and approve access. No API key is needed.

https://www.fanpresence.app/api/mcp/mcp

Streamable HTTP works with Cursor, Claude, Codex and compatible MCP clients. Start with get_overview and use get_help to discover the bot, fan, vault, automation, content, analytics and integration tools. For clients without OAuth, create an API key in Extra → MCP and configure an Authorization: Bearer header. Disconnect OAuth agents or revoke keys on that page to stop future access.

{
  "mcpServers": {
    "fanpresence": {
      "url": "https://www.fanpresence.app/api/mcp/mcp"
    }
  }
}

Start with a real question

“Find why fans aren’t reaching Fanvue and fix it”

“Restock my $20 tier”

“Test a warmer voice before rolling it out”

“Compare the last two bot versions and record what worked”

Questions

Can an agent send messages?

Only when you enable agent live messaging and approve that permission. Existing account and fan controls still apply.

Can I undo a change?

Restore an earlier bot configuration as a new version. Undo vault edits when those items have not changed since the operation.

Will my agent see fan contact details?

Tools omit names and handles and mask common contact details in text. Automated text masking is best effort.

Does this work with my assistant?

Use the OAuth connection methods shown above. Extra → MCP also has advanced API keys for clients that cannot sign in.

Does a test affect real conversations?

Simulations use archetypes or private copies of history and never send messages to real fans. Model calls can use your AI budget.

What are the current limits?

Reply previews and generation use credits. Conversation masking is best effort. Historical revenue can have unknown attribution. Stored integration health and queued operations do not prove delivery. Saved schedules must be cancelled explicitly after disconnecting. Local vault prices do not update provider prices.

Give your agent the full picture.

Connect your agent