Quick connect
Add Fanvue to your assistant in one click. The same server URL works with every client:Add to Claude
One click adds the connector, then you sign in with Fanvue on first use. Requires a Claude plan with custom connectors.
Add to Cursor
Opens Cursor with the Fanvue server pre-filled, then sign in on first use.
Other clients
ChatGPT, Claude Code, Codex and any MCP client. Jump to the step-by-step setup.
Detailed setup
Pick your client and follow the steps below.Claude
ChatGPT
Cursor
Claude Code
Codex
- Other clients
Open connector settings
In the Claude desktop app or claude.ai, go to Customize → Connectors, click the
+ button, and select Add custom connector.
On first connection you’ll authorize through Fanvue’s standard OAuth flow in your browser. There are no API keys to copy or paste.
One connection, your whole account
The MCP server exposes the full Fanvue API as tools your assistant can call directly.Auto-reply to fans
Read unread chats, draft on-brand replies, and send messages, keep conversations warm around the clock.
Pull account info
Fetch your profile, followers, subscribers and notifications so the assistant always has live context.
Manage posts
Create, edit, pin, repost and schedule content, spin up a post from a prompt and publish to your feed.
Insights on demand
Ask for earnings, top spenders and subscriber trends in plain language, pulled from the Insights API.
Media & vault
Browse the vault, organise folders, upload media and grant access, all through natural language.
Mass messaging & lists
Build smart and custom lists, then send targeted mass messages to the right segment of your audience.
Agencies: run every creator from one place
With agency scopes, the same connection lets your assistant act across all managed creators, review
chats, check the chatter leaderboard, pull per-creator earnings, and manage posts and messages for each account.
Just ask
Once connected, you run your account in plain language, for example:Clear the inbox
More example prompts
A library of ready-to-use prompts for chats, insights, posts, mass messaging, the Vault, and agency. Copy one and adapt it.
Secure by design
You stay in control of access at every step.OAuth 2.0
Connecting runs the standard Fanvue OAuth flow, no API keys to copy, paste or leak.
Revoke any time
The assistant acts on your behalf and can only do what your own account can do. You approve access when you first connect, and can revoke it from your Fanvue settings at any time.
Rate-limited
Every call respects the same rate limits and safeguards as the rest of the Fanvue API.
FAQ
Which assistants can connect?
Which assistants can connect?
Any client that supports the Model Context Protocol, including Claude (web and desktop), ChatGPT
(Developer mode), Claude Code, Cursor and Codex. Use the custom-connector flow in apps with a UI, or
the CLI/config approach for terminal-based tools.
Do I need to write any code?
Do I need to write any code?
No. Connecting is a settings change in your AI client, and authorisation happens through Fanvue OAuth
in your browser. Developers who prefer to self-host can run the open-source
fanvue-api-mcp server instead.
What can the assistant actually access?
What can the assistant actually access?
Everything your authorised scopes allow on the Fanvue API: chats and messages, posts, media and vault,
insights, followers and subscribers, lists, tracking links, and agency endpoints. See the
API Reference for the full surface.
Can agencies use it across multiple creators?
Can agencies use it across multiple creators?
Yes. With agency scopes the connection works against the creator-scoped endpoints, so your assistant
can manage chats, posts, media and insights for every creator you manage from a single connection.
How do I disconnect?
How do I disconnect?
Remove the connector in your client’s settings (for example
claude mcp remove Fanvue in Claude Code),
then revoke the app’s access from your Fanvue account settings.