Skip to main content
The Fanvue MCP server exposes the Fanvue API over the Model Context Protocol (MCP), as tools a client calls against the account you sign in with. Once it’s connected, the client can read and answer chats, publish posts, manage the vault and read earnings for your account, or for every creator you manage as an agency. You need a Fanvue creator or agency account and a client that supports MCP. There’s nothing to build and no code to write: connecting is a settings change in the client, and you authorise it through Fanvue OAuth in your browser.

​
Quick connect

The server URL is the same for every client:
Add the URL as a remote server in your client, then sign in with Fanvue when the client asks. Two clients offer a one-click install in Detailed setup. Once you’re connected, try the example requests. To run the server yourself instead, use the open-source fanvue-api-mcp server.

​
Detailed setup

Any client that implements MCP over a remote HTTP connection can connect directly, and any other client can connect through mcp-remote. Each client has its own page with the setup steps, requests to try and how to disconnect.

Claude

Custom connector, with one-click install.

Claude Code

One claude mcp add command.

ChatGPT

Connector in developer mode.

Codex

mcp-remote in config.toml.

Cursor

One-click install or mcp.json.

Grok Bot

Custom server added from a chat.

Grok

Custom connector on grok.com.

Grok Build

One grok plugin install command.
For any other client, use the URL directly if the client supports remote (HTTP) servers, or bridge it with mcp-remote:

​
What the server can do

The server exposes the previous-version (unversioned) Fanvue API catalogue as tools. Each tool maps to one API operation, and the client picks the tools for each request.

Read and send messages

Read unread chats and message history, then send replies.

Read account data

Read your profile, followers, subscribers and notifications.

Manage posts

Create, edit, pin, repost and schedule posts. Publish an image post from a file.

Read insights

Read earnings, top spenders and subscriber trends.

Manage media and the vault

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

Message lists

Read smart lists, create and edit custom lists, then send a mass message to a list.

Agencies: every managed creator from one connection

With agency scopes, the same connection works against the creator-scoped endpoints for every creator you manage: chats, the chatter leaderboard, per-creator earnings and insights, posts, media and messages.
The full reach is everything your granted scopes allow on the unversioned API, which also covers tracking links and the agency endpoints. The API reference has the whole surface, and What is not exposed lists the exceptions.

​
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 and never passes through the conversation.

custom__create-image-post

Publishes a post with the uploaded image: caption, audience, pay-to-view price, schedule, expiry and collections. On a paid post, a second uploaded image serves as the free teaser. The post goes live only once the image is ready to display.
Ask for the outcome, for example “post this photo as a $9.99 pay-to-view with a teaser”, and the client selects the tools. Every argument and result field is in the custom tools reference.

​
What is not exposed

Two groups of operations are outside the server.

​
Scopes and access

Connecting runs the standard Fanvue OAuth 2.0 flow, and the client requests one of two scopes. The connection also requests the OIDC scopes openid and offline_access, which identify you and keep the connection signed in. Scopes lists what each API scope unlocks. Fanvue grants the subset of API scopes your account type can use, and hides from the client any tool whose scopes it did not grant. A creator account never sees agency tools. The client can only do what your own account can do, within the scopes granted on connect. Every call counts against the API’s own rate limits: 200 requests per 60 seconds per user per app by default, with higher limits for agencies on request. See Rate limits.

​
Disconnect and revoke

Remove the server in your client’s settings, or from the terminal in a command-line client:
Then revoke the connection in Fanvue under Settings > Account > Third Party Apps Consent. You can revoke at any time. After revocation the next tool call returns a reconnect error, and the client runs the connect flow again.