Your ideas. Your agent.
The right API context.
Bring FansAPI documentation into the tools you already build with. Find an endpoint, understand the details, and keep your momentum.
Public docs. No API key needed.
Same docs. Your way of working.
Choose your coding agent and connect the FansAPI documentation.
Connect to Claude Code
With Claude Code installed, run this in your project’s terminal.
claude mcp add --transport http fansapi-docs https://docs.fansapi.com/api/mcpCheck the connection
Start a new Claude Code session in that project. Run /mcp and check that fansapi-docs is connected.
Public documentation. No API key needed.
Start with a question.
Build on the answer.
Give your agent a specific task and ask it to read the source before writing code.
Use the fansapi-docs MCP server to find and read the documentation for listing connected accounts. Show a minimal Node.js example using an environment variable for the API key, and link to the source documentation.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.
Your setup, step by step.
A little context before you connect.
The essentials for your first setup.