> ## 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.

# Hosted MCP

> Use the platform MCP endpoint with your API key — the default way to drive accounts from agents.

Point your agent at the platform MCP endpoint. It authenticates with your API
key and selects the connected account per call.

```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
{
  "mcpServers": {
    "onlyfanskit": {
      "url": "https://mcp.onlyfanskit.dev",
      "headers": {
        "Authorization": "Bearer <your-api-key>"
      }
    }
  }
}
```

## Why hosted

|             | Hosted MCP                                             |
| ----------- | ------------------------------------------------------ |
| Credentials | Your API key only                                      |
| Accounts    | Any account connected under your org                   |
| Sessions    | Stored and refreshed on onlyfanskit infrastructure     |
| Rate limits | Your plan's [limits](/platform/rate-limiting)          |
| Errors      | [RFC 9457 problems](/platform/errors) relayed to tools |

You do not pass `OF_COOKIE` or run `onlyfanskit-mcp` with session env vars on
your own machines for production integrations.

## Selecting an account

Tools that act on an account take the connected account `id` from
`GET /v1/accounts`. Calls relay through the same passthrough as the
[REST API](/api-reference/introduction).

<Note>
  [Connect accounts](/connect/overview) first — embedded connect, email login,
  or mobile approval. The hosted MCP only acts on accounts already linked to
  your key.
</Note>