Skip to main content
The Fanaura MCP server exposes 20 tools. Every tool name starts with fanaura.. Twelve only read. Eight change a journey. None delete anything.

Journeys

Create, edit, check, publish, and list journeys. 12 tools.

Contacts

Totals, search, one contact, timelines, and audience activity. 6 tools.

Setup

Channel status and the Instagram connect link. 2 tools.

Every tool

Tool annotations

Each tool tells the assistant how careful to be. Assistants use these hints to decide when to ask before running a tool.

What a description contains

Each description states what the tool does, what it needs, what it returns, and what it changes. A description does not tell the assistant how to reply, which tool to call next, or to leave prices out of the answer. Server instructions, sent when a client connects, are separate from those descriptions. They explain that create_journey publishes in one call, that edits reach fans after publish_journey, and that tool results contain no prices, upgrades, or store links.

Shared response fields

Most tools return these alongside their own data.
boolean
required
true when the tool ran. A draft that could not go live still returns true from create_journey, with the reason in message.
string
One plain sentence the assistant can repeat.
string
Present when success is false. Field problems read Field name: what to fix.
string
The input that caused the error, such as keyword or contact_id.
fanaura://journeys/{id} on journey results. Opens the journey in the Fanaura iPhone app.
string
https://app.fanaura.com/automations/{id} on journey results.
string
The tool name that produced the result.