Skip to main content
The Model Context Protocol (MCP) is an open standard that lets an AI assistant call tools on another service. Fanaura runs one MCP server. Your assistant connects to it, signs in as you, and calls Fanaura tools to build journeys and read contacts.

​
The pieces

Your assistant

Claude, ChatGPT, Cursor, or another MCP client. It reads your request, picks a tool, and writes the answer.

The Fanaura MCP server

https://app.fanaura.com/mcp. It checks your sign-in token and runs the tool against your account.

Your Fanaura account

Journeys, contacts, visits, and answers. This is the only place your data is stored.

​
A request, step by step

1

The assistant chooses a tool

Each tool description states what the tool does, what it needs, what it returns, and what it changes. The assistant matches your request to that description. A request with a link and a keyword fits fanaura.create_journey. A question about one person fits fanaura.get_contact.
2

Fanaura checks who you are

The assistant sends the access token it received when you signed in. Fanaura looks up that token, finds the account you approved, and runs the tool only inside that account.
3

The tool runs on your live data

Nothing is copied or synced ahead of time. Each request reads and writes your Fanaura account at that moment.
4

The assistant answers from the result

Fanaura returns structured data. Journey tools include a recap of the settings. Contact tools include a summary. The description states what came back. It does not tell the assistant how to phrase the answer.

​
Where your data lives

Your assistant’s own chat history follows that assistant’s privacy settings. Fanaura does not read your chats. It only sees the tool calls the assistant makes.

​
Why a new chat sometimes matters

Assistants save the list of Fanaura tools when you connect. When Fanaura adds a tool or improves a description, an existing chat can keep using the older list.
If the assistant says a Fanaura tool does not exist, or behaves the old way, start a new chat. If that does not help, disconnect and reconnect Fanaura in your assistant’s settings.

​
One server for every assistant

Fanaura does not run a separate backend per assistant. Claude, ChatGPT, Cursor, VS Code, Claude Code, and Gemini CLI all call https://app.fanaura.com/mcp, sign in through the same Fanaura page, and get the same 20 tools. A fix on Fanaura’s side reaches every assistant at once.

​
Read and write

Read tools (12)

List journeys, get one journey, check a link, validate publish, setup status, Instagram connect link, audience overview, search contacts, describe contact fields, get contact, contact timeline, and audience activity.

Write tools (8)

Create journey, start journey, set destination, set keyword, set public replies, set capture, set followers only, and publish journey.
Seven of those write tools are marked destructive: create journey, publish journey, set destination, set keyword, set public replies, set capture, and set followers only. Start journey creates a new draft only and is not destructive. The 12 read tools are read only. No tool deletes a journey or a contact. The full list, with every parameter, is in the tool reference.