The Fanduit MCP server hands your AI agent 350+ tools across every connected creator. Live fans, chats, revenue, campaigns, and AI reports, all routed through the same signing, proxying, and metering as the REST API.
# point your agent at one API key — 350+ tools appear $ FANDUIT_API_KEY=sk_live_… php artisan mcp:serve → initialize ● ready proto 2024-11-05 → tools/list ● 363 tools list_active_fans send_message get_financial_analysis mass_message list_top_spenders get_fan_summary …
Live, metered tool calls against the accounts you connected, never a stale screenshot.
Every REST endpoint is auto-exposed as an MCP tool — read fans, send DMs, run campaigns, pull earnings and AI reports, all first-class.
Any MCP-compatible client works. Drive Custom GPTs, Claude Projects, or Manus agents against real creator data.
Every tool call runs the same credit + rate-limit metering, tagged surface=mcp — no separate billing, no surprises.
Calls flow through per-account proxies, self-healing signing, and the encrypted session vault — the agent never touches raw credentials.
A read-only agency assistant runs on top of the tool layer — ask for a fan summary or a financial read in plain language.
Set one API key, point your client at the server, and the whole catalog appears. No per-tool wiring.
One key, one server, the full catalog.
Create a Fanduit key in the dashboard. It scopes to your account and every connected creator.
Add the Fanduit MCP server to Claude, ChatGPT, or Manus with your key. Remote HTTP and local stdio both work.
"Which fans went quiet this week?" — the agent calls the right tools and answers from live data.
Chat-ops for a whole roster.
Ask your agent for yesterday's revenue, top spenders, and churn across every account in one prompt.
Have the agent read a chat and draft an on-brand reply, then send it through the same tool.
Surface expired fans worth re-engaging and launch a campaign without leaving the chat.
Generate a financial + fan summary per creator on demand for weekly agency reports.
Run a whole roster from one API — connect every creator you operate and automate messaging, growth, and reporting at scale.
Neutral infrastructure on accounts you own, with encrypted credentials, per-account proxies, and no screen sharing.
Clean REST + MCP, signed webhooks, idempotency, and transparent credit metering. Build tools that don\'t break by morning.
The Model Context Protocol is an open standard that lets AI agents call external tools. Fanduit ships an MCP server so any compatible agent can operate your connected accounts.
Anything MCP-compatible — Claude (desktop and Projects), ChatGPT Custom GPTs and Agent Mode, and Manus. Remote HTTP and local stdio transports are both supported.
No. MCP tool calls run through the identical credit and rate-limit metering as REST, tagged as the MCP surface. One balance, one set of limits.
Never. Tools run server-side through the signing engine and per-account proxies; connected-account credentials stay encrypted in the vault.
Install the Fanduit MCP server and run your whole roster from the AI tool you already use.