Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.onlyfanskit.dev/llms.txt

Use this file to discover all available pages before exploring further.

Rather than running onlyfanskit-mcp yourself, point your agent at the platform’s hosted MCP endpoint. It authenticates with your API key and selects the connected account per call — so one agent can drive every account in your org. 
{
  "mcpServers": {
    "onlyfanskit": {
      "url": "https://mcp.onlyfanskit.dev",
      "headers": {
        "Authorization": "Bearer <your-api-key>"
      }
    }
  }
}

​
How it differs from self-hosted

Self-hostedHosted
CredentialsPer-session env varsYour API key
AccountsOne session at a timeAny connected account
Session managementYou manageManaged for you
Rate limitsNone enforcedYour plan’s limits
ErrorsThrown SDK errorsRFC 9457 problems relayed to tools

​
Selecting an account

Tools that act on an account take the connected account id (from GET /v1/accounts). The hosted MCP relays each call through the same passthrough as the platform API, so quotas, scopes, and error semantics are identical.
Connect accounts first via the connect flow. The hosted MCP can only act on accounts already linked under your key.