Fanvue MCP connector
The Fanvue connector brings your creators, subscribers, chats, mass messages, earnings and agency team into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person works with Fanvue under their own sign-in.
- Connects over OAuth
- Free 14-day trial
- No credit card
Summarize this week's Fanvue earnings by creator.
Working in Fanvue with Elaichi
-
List all Fanvue agencies team members
-
List all Fanvue insights chatter leaderboards
-
List all Fanvue agencies chats
How to connect Fanvue to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Fanvue MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Fanvue MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Fanvue MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Fanvue MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Fanvue MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Fanvue to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Fanvue through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Fanvue is logged.
-
Agency operations
Onboard a new creator or team member
Send a Fanvue creator invite or team member invite from the same place the rest of the agency's work happens, then update a team member's details when their role changes.
-
Chat team
Reply to fans without leaving your workflow
Open a subscriber's Fanvue chat, read the recent messages and send a reply, or start a new conversation with a fan who just subscribed.
-
Marketing
Schedule and tidy up mass messages
Draft a mass message to a creator's Fanvue subscribers, fix a typo in one that is already set up, and remove a campaign that no longer applies.
-
Finance
Pull agency earnings for the month
Ask for Fanvue earnings across the agency's creators for a period and get the figures ready to reconcile against payouts.
-
Growth
Track how subscriber counts are moving
Look at Fanvue subscriber and follower history for a creator to see whether a promotion actually moved the numbers week over week.
-
Chat management
See which chatters are performing
Check the Fanvue chatter leaderboard and the list of agency chats to see who is converting conversations and where fans are waiting on a reply.
Try asking
- “Summarize this week's Fanvue earnings by creator.”
- “Which chatters top the Fanvue leaderboard this month?”
- “How many subscribers did we gain in 14 days?”
What connecting Fanvue gets you
6 screens from Elaichi, each doing one job for your Fanvue account.
Ask Elaichi to work across your apps.
Summarize this week's Fanvue earnings by creator.
Which chatters top the Fanvue leaderboard this month?
How many subscribers did we gain in 14 days?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about subscribers, get real answers.
Plain language questions answered from live Fanvue chats, subscribers and earnings.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Fanvue.
One governed MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
225 Fanvue tools ready to call.
Chats, subscribers, earnings and team members covered without writing custom code.
Toolboxes
Every team gets its own toolbox.
Curate Fanvue tools per team so each one sees only its work.
Shared connections
Teammates work without seeing a credential.
Each Fanvue connection shows who connected it and which teams and members share it.
Audit log
Every Fanvue call is on the record.
When, who, what happened, type and resource for each request through Elaichi.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Fanvue digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch subscribers
Fanvue
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Fanvue
Queued
Automations
A schedule fires, the digest ships.
Fanvue earnings are fetched, grouped, drafted by an agent, approved, then posted back.
Fanvue health
Refreshed 4 minutes ago · every 15 minutes · from the subscribers collection
Subscribers
1,284 ↓ 12%
Chats
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Subscribers created
Last 14 days
By team
Share of activity
Chat team night shift 34%
Finance 27%
Creator management 21%
Growth 18%
Collections and dashboards
Fanvue numbers, computed on a schedule.
Four metrics, 14 days of records created and a breakdown by team, no model.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Fanvue
All three can connect Fanvue to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Fanvue tools | Allow or restrict single Fanvue tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Fanvue call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Fanvue tools for your AI agents
225 tools are ready to call through Elaichi's MCP endpoint the moment you connect Fanvue, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Fanvue to Claude?
First, connect Fanvue in Elaichi. Fanvue asks you to register an OAuth application inside your Fanvue account, so someone brings a client ID and secret once, and after that each person simply signs in to Fanvue as themselves. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Fanvue is ready to use in Claude from that point.
Does Fanvue work with ChatGPT and Cursor as well as Claude?
Yes. Once Fanvue is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Fanvue once and every client picks it up.
What can an AI agent actually do with my Fanvue data?
An agent can read and reply to Fanvue chats, start a new chat with a subscriber, create, edit or remove mass messages, and pull up subscribers, earnings, follower history and chatter leaderboards for the agency. It can also invite creators and team members and update a team member's details. Short, concrete asks like "show this creator's earnings for March" work better than long paragraphs, because Fanvue exposes a lot of actions and the agent searches for the right one.
Does connecting Fanvue give the AI access to every creator in my agency?
No. Access in Fanvue follows the person who signed in, so an agent working on someone's behalf sees only the creators, chats and earnings that person can already see in Fanvue. Elaichi can narrow that further, for example to reading only, but it can never widen it beyond what Fanvue itself allows that person.
Can I stop an agent from deleting or changing things in Fanvue?
Yes. Restrictions in Elaichi work per action, so you can allow reading Fanvue chats and earnings while restricting the sending of mass messages or the deletion of chat messages. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.
What happens to a Fanvue connection when someone leaves?
Offboarding a person in Elaichi ends their access to Fanvue through every client at once. If they were using a shared Fanvue connection, it keeps working for everyone else on the team. If you want Fanvue gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.
Does the Fanvue MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Fanvue is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Fanvue?
Yes. Both let Claude, ChatGPT or Cursor use Fanvue. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Fanvue call.
How is Elaichi different from Composio for Fanvue?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Fanvue: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Fanvue in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot