OnlyFans API

Develop with AI Agents

Use AI agents with OnlyFans API documentation resources and the official onlyfansapi-skill.

Not sure where to start?

AI-ready docs resources

When building with AI agents, point them to these resources first:

Per-page .mdx URLs

For individual guides or API endpoints, just append .mdx to the page URL and feed that directly to the AI agent.

Examples:

  • https://docs.onlyfansapi.com/introduction/guides/develop-with-ai-agents.mdx
  • https://docs.onlyfansapi.com/api-reference/account/list-accounts.mdx
  • https://docs.onlyfansapi.com/api-reference/chats/list-chats.mdx

Two MCP servers, different jobs

We run two MCP servers. They are easy to confuse and do completely different things — pick by whether you want your agent to read the docs or run the API.

Docs MCPAPI MCP
URLdocs.onlyfansapi.com/api/mcpapp.onlyfansapi.com/mcp/onlyfans-mcp
Use it toSearch and read this documentationActually call the API
Tools3 (search_docs, get_doc_page, get_overview)350+ — one per endpoint, OnlyFans and Fansly
AuthNone — public, read-onlyAPI key or OAuth
Touches your accountsNoYes

Most developer setups want both: the Docs MCP so the agent writes correct calls, and the API MCP so it can execute them.

Connect our docs via MCP

We host a remote Model Context Protocol server at:

https://docs.onlyfansapi.com/api/mcp

Hook it into Claude, Cursor, VS Code, ChatGPT, or any other MCP-compatible client and your agent gets three tools that query these docs directly — no copy/paste, always up to date:

  • search_docs(query, limit?) — full-text search across the docs (Algolia).
  • get_doc_page(path) — raw Markdown for a single page (path or full URL).
  • get_overview() — the entire docs as one Markdown document (llms.txt).

The MCP server is public, read-only, and requires no API key. It only exposes content already published at docs.onlyfansapi.com.

Cursor

→ Add to Cursor (one click)

Or manually: SettingsMCPAdd new server, type HTTP, URL https://docs.onlyfansapi.com/api/mcp.

VS Code (GitHub Copilot)

→ Add to VS Code (one click)

Or manually: open the Command Palette → MCP: Add ServerHTTP → URL https://docs.onlyfansapi.com/api/mcp.

Claude Desktop

Open SettingsConnectorsAdd custom connector and paste the URL:

https://docs.onlyfansapi.com/api/mcp

Alternatively, add this entry to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows) and restart the app:

{
  "mcpServers": {
    "onlyfansapi-docs": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://docs.onlyfansapi.com/api/mcp"]
    }
  }
}

Claude.ai (web)

In Claude.ai: SettingsConnectorsAdd custom connector → URL https://docs.onlyfansapi.com/api/mcp. Requires a paid plan that supports custom connectors.

ChatGPT

In ChatGPT: SettingsConnectorsCreate → paste https://docs.onlyfansapi.com/api/mcp. Custom connectors are available on plans that include MCP support (Pro / Business / Enterprise at the time of writing).

Other MCP clients

Any client that speaks Streamable HTTP MCP works — point it at https://docs.onlyfansapi.com/api/mcp. For stdio-only clients, bridge with mcp-remote:

npx -y mcp-remote https://docs.onlyfansapi.com/api/mcp

Call the API via MCP

The docs MCP above only reads documentation. To let an agent run the API — send messages, pull earnings, publish posts — connect the API MCP server:

https://app.onlyfansapi.com/mcp/onlyfans-mcp

It exposes 350+ tools, one per documented endpoint, across both creator platforms: 290+ OnlyFans (unprefixed) and 80+ Fansly (prefixed fansly_).

For stdio-only clients, bridge with mcp-remote. The server supports OAuth, so this opens a browser to authorize — no key handling in your config:

npx -y mcp-remote https://app.onlyfansapi.com/mcp/onlyfans-mcp

Backend integrations authenticate instead with an API key from app.onlyfansapi.com/api-keys, passed as Authorization: Bearer …. See Embed in your app for that pattern.

Working with one platform only? Append ?platforms=onlyfans or ?platforms=fansly to cut the tool list down before it reaches your model.

Unlike the docs MCP, this server acts on your real accounts. Use a scoped API key, keep write access on Needs approval in your client, and review the audit log.

Full setup guides: Claude · ChatGPT · Manus · Embed in your own app. Platform specifics: OnlyFans · Fansly.

Install onlyfansapi-skill from skills.sh

Skill page: skills.sh/onlyfansapi/skill/onlyfansapi-skill

Install command shown on the skill page:

npx skills add https://github.com/onlyfansapi/skill --skill onlyfansapi-skill

Restart your agent/CLI session after installation so the new skill is loaded.

Configure your API key

The skill expects ONLYFANSAPI_API_KEY in your environment:

export ONLYFANSAPI_API_KEY="your_api_key_here"

Get your key from: app.onlyfansapi.com/api-keys

Quick auth check:

curl -s -H "Authorization: Bearer $ONLYFANSAPI_API_KEY" \
  "https://app.onlyfansapi.com/api/accounts" | jq .

Prompting tips for better agent output

  • Ask the agent to read llms.txt or llms-full.txt before generating calls.
  • Include exact date ranges and timezone when requesting analytics.
  • Ask for tables with totals when comparing multiple accounts.
  • Ask the agent to show endpoint path + params before execution if you want to review requests first.

On this page