Skip to main content
Integrations connect Fanvue to tools you already use. Two of them need nothing built: connect the MCP server to a chat client and run your account from there, or send conversion events to your ad platform. The others help you build, by giving your editor the docs and the SDK so the code it writes calls the real API.

Which one is for you

Operate your account from a chat client

The MCP server needs no app of your own. You connect a client to one URL, sign in with Fanvue, and the client calls the API on your account’s behalf.

Fanvue MCP server

Connect any MCP client to https://mcp.fanvue.com/mcp, authorise with Fanvue, and read and send messages, manage posts and media, and read insights. Agencies work across every managed creator from one connection.

Use the docs from your editor

Building your own integration means building an app, because that’s how Fanvue issues API credentials. If you haven’t registered one yet, Build your first app does it and makes a first call. Then give your editor the docs and the SDK, so the code it generates uses the real endpoints and helpers.

Scaffold an app from your editor

Give your editor the docs, the OpenAPI specs and the SDK, then generate a working app from the App Starter with one request.

Docs as plain text

llms.txt is the index, llms-full.txt is every page in one file, and both OpenAPI documents are served alongside. Any tool that reads URLs can use them.

Automation and tracking

n8n node

Call Fanvue resources from an n8n workflow with OAuth 2.0 credentials.

Conversion tracking

Send conversion events to Meta Pixel, Google Tag Manager or a server postback URL.