> ## Documentation Index
> Fetch the complete documentation index at: https://api.fanvue.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations overview

> Connect Fanvue to tools you already run: the MCP server for chat clients, plain-text docs for your editor, an n8n node and conversion tracking.

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

| Goal | Start with | You need |
| - | - | - |
| Run a creator or agency account in plain language, with nothing to build | [Fanvue MCP server](/docs/mcp-server) | A Fanvue account and an MCP client |
| Build your own app or integration on the API | [Scaffold an app from your editor](/docs/integrations/scaffold-an-app) | An app in the Developer Area for OAuth credentials |
| Call Fanvue from an automation workflow | [n8n node](/docs/integrations/n8n) | An n8n instance and an app in the Developer Area for OAuth credentials |
| Measure ad campaigns against revenue | [Conversion tracking](/docs/integrations/conversion-tracking) | A Meta Pixel, a Google Tag Manager server container or a tracker that accepts postbacks |

## 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.

<Card title="Fanvue MCP server" icon="plug" href="/docs/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.
</Card>

## Use the docs from your editor

Building your own integration means [building an app](/docs/app-store/introduction), because that's how Fanvue issues API credentials. If you haven't registered one yet, [Build your first app](/docs/get-started/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.

<CardGroup cols={2}>
  <Card title="Scaffold an app from your editor" icon="code" href="/docs/integrations/scaffold-an-app">
    Give your editor the docs, the OpenAPI specs and the SDK, then generate a working app from the App Starter with one request.
  </Card>

  <Card title="Docs as plain text" icon="file-lines" href="/docs/integrations/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.
  </Card>
</CardGroup>

## Automation and tracking

<CardGroup cols={2}>
  <Card title="n8n node" icon="diagram-project" href="/docs/integrations/n8n">
    Call Fanvue resources from an n8n workflow with OAuth 2.0 credentials.
  </Card>

  <Card title="Conversion tracking" icon="bullseye" href="/docs/integrations/conversion-tracking">
    Send conversion events to Meta Pixel, Google Tag Manager or a server postback URL.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.