Skip to content
Fans API
[MODEL CONTEXT PROTOCOL]

The API reference.
Part of the conversation.

Connect your AI tools to FansAPI’s public documentation through MCP. Search for what you need and bring the source into your workflow.

One endpoint. Useful context.

Connect with Streamable HTTP.

Public docs MCP endpoint
https://docs.fansapi.com/api/mcp
Access
Public · read-only
Authentication
Not required
Server name
fansapi-docs
[THE DOCUMENTATION TOOLKIT]

Find it. Read it. Build with it.

Three focused tools give your agent a path through the documentation.

search_docs

Find the right page

Search the documentation by topic or endpoint. Start here when you know what you want to build.

EXAMPLE INPUT
{ "query": "list accounts", "limit": 2 }
get_doc_page

Read the details

Read a page as Markdown, including its parameters, examples and implementation notes.

EXAMPLE INPUT
{ "path": "/api-reference/account/list-accounts" }
get_overview

See the bigger picture

Get the documentation index to explore the available guides and API reference.

EXAMPLE INPUT
{}

Tool names and public access checked on 9 October 2026. Read the setup guide

[FROM QUESTION TO CONTEXT]

A source for your next step.

Ask about an endpoint. Let your agent locate the page and read the details before suggesting an implementation.

SEARCH“How do I list connected accounts?”
REFERENCE PAGEList AccountsGET /api/accounts

Read the source. Then write your example.

[A CLEAR CONNECTION]

The docs, in context.

Give your agent useful reference material. Keep account access an explicit, separate choice.

Learn from the public docs

Search guides, read endpoint details and explore the API reference. This connection works without an API key.

Account actions have their own access

Reading or changing account data requires a separate authenticated integration. Connecting the docs does not grant that access.

Explore the API reference
[MCP QUESTIONS]

Know what you’re connecting.

Connection, access and useful next steps.