Skip to main content
These are requests you can send, word for word or adapted, through a client connected to the Fanvue MCP server. Each one is plain English. The client works out which tools to call, and every request works on any connected account except the agency ones, which need agency scopes.

Messages

Clear the inbox
Prioritise high-value fans
Follow up on unpaid offers
Reward your top fans
Message a smart list

Posts and media

Plan a week of posts
Publish an image post
Publishing an image needs a client that can read files on your machine, such as an editor or terminal client.
Find unposted content

Insights

Know your numbers
Spot your best content

Agency

These requests need agency scopes, so they work only on an agency account.
Run the morning standup
Coach the team

What each request calls

The client chooses tools by matching each request to the API operations the server exposes. This is what each example reaches.

What cannot be requested

Dynamic lists live only on the /v1/ API, which the server does not expose, so a request to build or message a dynamic list fails. Experience operations can’t be authorised through the server, so requests about fan experiences fail too. What is not exposed has the reasons.