Grok x OnlyFans & Fansly
Connect our MCP server to Grok as a custom connector and run your agency from any chat — grok.com, Grok Business, or the xAI API.
What this does
Grok can call Fans API endpoints directly — send messages, pull stats, manage posts — through the OnlyFans MCP server. Add it once as a custom connector in Grok, then ask Grok to run OnlyFans tasks in plain English from any chat.
Works with grok.com, Grok Business / Enterprise, and the xAI API.
Custom connectors are available to all Grok users. On Business and Enterprise, a team admin adds the connector once, then every member connects their own account.
Prerequisites
- A Grok account
- An Fans API account
- At least one connected OnlyFans account
Step-by-step
Grok uses remote MCP over HTTP. The setup lives behind Connectors.
1. Open Grok Connectors
Go to grok.com/connectors, click New Connector, then select Custom.
2. Add a custom connector
Enter these details:
- Name —
OnlyFans MCP(or any label you prefer) - MCP server URL:
https://app.onlyfansapi.com/mcp/onlyfans-mcp3. Authorize Grok on Fans API
Grok redirects you to app.onlyfansapi.com. Click Authorize.
You'll land back in Grok with the connector marked as connected. Done — Grok now has 350+ tools across chats, fans, and earnings.
Sign in to app.onlyfansapi.com in a separate tab first. If you're signed out when Grok redirects you, you land on the dashboard after signing in instead of the authorize screen, and the flow stalls.
4. Prompt Grok
Open a new chat and ask Grok to do something. It discovers the OnlyFans MCP tools automatically.
Use the xAI API
Building your own agent on Grok? Pass the OnlyFans MCP server as a remote MCP tool to the xAI Responses API. Grok connects, lists the tools, and calls them on its own — no tool-call handling on your side.
Put your Fans API key in authorization. Grok sends it as a Bearer token, so paste the bare key:
curl https://api.x.ai/v1/responses \
-H "Authorization: Bearer $XAI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "grok-4.3",
"input": [
{ "role": "user", "content": "Summarize today'\''s earnings per creator." }
],
"tools": [
{
"type": "mcp",
"server_url": "https://app.onlyfansapi.com/mcp/onlyfans-mcp",
"server_label": "onlyfans",
"authorization": "YOUR_FANS_API_KEY",
"allowed_tools": ["listAccounts", "fansly_listAccounts"]
}
]
}'Without allowed_tools, Grok loads all 350+ tool definitions into every request — well over 100k input tokens. List only the tools your agent needs, or append ?platforms=onlyfans / ?platforms=fansly to the server URL.
Example use cases
6 prompts that replace daily ops grunt work. Drop them into any Grok chat with the connector enabled:
- "Summarize today's PPV revenue per creator." — replaces the morning dashboard check
- "List my top 20 spenders this week with their last message timestamp." — no more switching dashboards per creator
- "Find every chat with no reply in 24h and surface them." — dropped chats never make it to morning standup
- "Draft a renewal DM for fans churning in the next 7 days. Don't auto-send." — Grok drafts, your team approves and ships
- "Identify whales who haven't messaged in 14 days — draft a re-engagement DM." — reactivate dormant high-spenders before they unsub
- "Compare this month's revenue on OnlyFans and Fansly per creator." — both platforms in one answer
Most tools are account-scoped and need the account id in the form acct_XXXXXXXXXXXXXXX. If you omit it, Grok will ask — or it will call listAccounts first to find one.
Troubleshooting
See also
- OnlyFans MCP overview — what MCP is, how it works, and supported clients
- Claude MCP install guide
- ChatGPT MCP install guide
- Manus MCP install guide
- Develop with AI Agents —
llms.txt, OpenAPI schema,onlyfansapi-skill - API Reference — every endpoint exposed as an MCP tool