FansAPI for Grok Bot.

Grok Bot plugins may be available across your account; shared Bot setup can affect its teammates. Review the scope shown by your client before saving. In Grok on the web, the documented flow is Connectors → New Connector → Custom. Grok Business and Enterprise may need an administrator to provision the connector first.

1. Open Connect apps, or the Bot’s Plugins setup, and choose the custom MCP server option.
2. Name the connection fansapi-docs, choose Remote HTTPS and paste the server URL. Leave authentication headers empty.
3. Save the connector, then attach it to a conversation. If your team blocks custom connectors, ask an administrator to allow this endpoint.

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

Check that your client exposes custom Remote HTTPS MCP connections and that you have permission to manage plugins. A team administrator may need to allow the endpoint. Grok web uses its own Connectors screen; it is a separate setup surface.

Attach the fansapi-docs connector to the conversation and inspect its available tools. Ask it to use the connected documentation search and return a source link. A web answer alone does not verify the MCP connection.

Confirm that the URL is https://docs.fansapi.com/api/mcp. This public documentation server needs no API key or Authorization header. Account API credentials belong to a separate authenticated integration.

The server searches and reads public FansAPI documentation. It does not access your accounts or send account API requests. Connecting the docs needs no API key; calling the account API from your application requires separate authentication.