Fanvue API Documentation

Connect once and your assistant can act across your whole Fanvue account in plain language, no code required.

Quick connect

Add Fanvue to your assistant in one click. The same server URL works with every client:

https://mcp.fanvue.com/mcp

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.

Open connector settings

In the Claude desktop app or claude.ai, go to Customize → Connectors, click the + button, and select Add custom connector.

Add the Fanvue server

Name it Fanvue and paste the server URL:

https://mcp.fanvue.com/mcp

Connect and sign in

Click Add → Connect, authorize with Fanvue, then try asking Claude to check your messages.

Enable developer mode

In ChatGPT (Plus, Pro, Business, Enterprise or Edu), open Settings → Apps & Connectors → Advanced settings and turn on Developer mode.

Create the connector

Go to Settings → Connectors → Create. Name it Fanvue and enter the server URL:

https://mcp.fanvue.com/mcp

Authorize and enable

Save and sign in with Fanvue when prompted. In a chat, enable Fanvue from the + (apps) menu, then start asking.

Custom MCP connectors in ChatGPT use Developer mode, currently in beta.

Open MCP settings

In Cursor, go to Settings → Cursor Settings → Tools & MCP → New MCP Server, or edit ~/.cursor/mcp.json directly.

Add the server

~/.cursor/mcp.json

{
  "mcpServers": {
    "fanvue": {
      "url": "https://mcp.fanvue.com/mcp"
    }
  }
}

Authorize

Cursor prompts you to sign in with Fanvue on first use.

Add the server from your terminal:

claude mcp add --transport http Fanvue https://mcp.fanvue.com/mcp

On first use, Claude Code opens your browser to authorize with Fanvue.

Add the server to ~/.codex/config.toml:

~/.codex/config.toml

[mcp_servers.fanvue]
command = "npx"
args = ["-y", "mcp-remote", "https://mcp.fanvue.com/mcp"]

Any MCP client can connect. Use the URL directly if the client supports remote (HTTP) servers, or bridge it with mcp-remote:

{
  "mcpServers": {
    "fanvue": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.fanvue.com/mcp"]
    }
  }
}

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 replies, and send messages.

Pull account info

Fetch your profile, followers, subscribers and notifications.

Manage posts

Create, edit, pin, repost and schedule posts. Generate an image post from a prompt and publish it.

Insights on demand

Pull earnings, top spenders and subscriber trends from the Insights API.

Media & vault

Browse the vault, organise folders, upload media and grant access.

Mass messaging & lists

Build smart and custom lists, then send mass messages to the segment you choose.

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.

Custom tools

Alongside the tools that mirror the Fanvue API, the server includes custom tools, named with a custom__ prefix. Each wraps one complete job. The first two take an image post from file to feed:

custom__start-image-upload

Returns a short-lived upload URL for one image. The image uploads directly to Fanvue, it never passes through the conversation.

custom__create-image-post

Publishes a post with the uploaded image: caption, audience, pay-to-view pricing, scheduling, expiry and collections. On a paid post, a second uploaded image serves as the free teaser shown to non-subscribers. The post goes live only once the image is ready to display.

You don’t need to name these tools. Ask for the outcome, “post this photo as a $9.99 pay-to-view with a teaser”, and the assistant selects them.

Custom tools reference

Building an agent? Every argument and result field for each custom tool, with examples.

More custom tools are coming. To request one, tell us in the community.

Just ask

Once connected, you run your account in plain language, for example:

Clear the inbox

Go through my unread chats, tell me who is waiting and what each fan wants, then draft a warm, on-brand reply to every one. Show me the drafts before anything sends.

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.

Security and access

OAuth 2.0

Connecting runs the standard Fanvue OAuth flow. There are no API keys.

Revoke any time

The assistant can only do what your own account can do. You approve access on 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?

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?

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?

Everything your authorized 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. On top of that, a growing set of custom tools covers complete jobs like publishing an image post.

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?

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.

MCP server

Coding agents

Fanvue MCP server

Quick connect

Add to Claude

Add to Cursor

Other clients

Detailed setup

One connection, your whole account

Auto-reply to fans

Pull account info

Manage posts

Insights on demand

Media & vault

Mass messaging & lists

Agencies: run every creator from one place

Custom tools

custom__start-image-upload

custom__create-image-post

Custom tools reference

Just ask

More example prompts

Security and access

OAuth 2.0

Revoke any time

Rate-limited

FAQ

​Quick connect

Add to Claude

Add to Cursor

Other clients

​Detailed setup

​One connection, your whole account

Auto-reply to fans

Pull account info

Manage posts

Insights on demand

Media & vault

Mass messaging & lists

Agencies: run every creator from one place

​Custom tools

custom__start-image-upload

custom__create-image-post

Custom tools reference

​Just ask

More example prompts

​Security and access

OAuth 2.0

Revoke any time

Rate-limited

​FAQ

Quick connect

Detailed setup

One connection, your whole account

Custom tools

Just ask

Security and access

FAQ