# FusionAuth Docs MCP server > Search FusionAuth documentation and ask technical questions about FusionAuth from your assistant. - Listing: https://mcp.tc/i/fusionauth-docs - Connect: use the server's own URL `https://ai.fusionauth.dev/mcp/docs` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: none - Category: [Docs & Knowledge](https://mcp.tc/c/docs-knowledge) - Vendor: FusionAuth ## About Connects your assistant to the FusionAuth documentation. You can search documentation sources and ask technical questions about FusionAuth, so answers come from the official docs rather than model memory. Runs as a hosted streamable-http endpoint at https://ai.fusionauth.dev/mcp/docs. No sign-in or API key is needed. ## What it can do - Ask technical questions about FusionAuth - Search FusionAuth documentation sources - Ground answers about FusionAuth in official docs ## Tools (2) - `ask_fusionauth_question`: Ask technical questions about FusionAuth and get an answer. - `search_fusionauth_sources`: Search FusionAuth documentation sources for a query. ## Example prompts - "How do I configure a FusionAuth application for OAuth authorization code flow?" - "Search the FusionAuth docs for webhook event types." - "Ask FusionAuth how to set up multi-factor authentication." - "Find FusionAuth documentation on custom JWT claims with lambdas." ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http fusionauth-docs https://ai.fusionauth.dev/mcp/docs ``` 2. Start Claude Code and type `/mcp`. **fusionauth-docs** should show as connected. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**. 2. Name it **FusionAuth Docs** and paste this URL: ```url https://ai.fusionauth.dev/mcp/docs ``` 3. Click **Add**. Its tools appear in the chat’s tools menu. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://ai.fusionauth.dev/mcp/docs` and click **Add**. 3. Turn it on in a chat from the tools menu. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://ai.fusionauth.dev/mcp/docs` as the server URL and choose **No authentication**. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "fusionauth-docs": { "url": "https://ai.fusionauth.dev/mcp/docs" } } } ``` ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"fusionauth-docs","type":"http","url":"https://ai.fusionauth.dev/mcp/docs"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "fusionauth-docs": { "type": "http", "url": "https://ai.fusionauth.dev/mcp/docs" } } } ``` ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "fusionauth-docs": { "serverUrl": "https://ai.fusionauth.dev/mcp/docs" } } } ``` 2. Refresh the MCP server list in Cascade. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add fusionauth-docs --url https://ai.fusionauth.dev/mcp/docs ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.fusionauth-docs] url = "https://ai.fusionauth.dev/mcp/docs" ``` ### Gemini CLI ```bash gemini mcp add --transport http fusionauth-docs https://ai.fusionauth.dev/mcp/docs ``` This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "fusionauth-docs": { "type": "http", "url": "https://ai.fusionauth.dev/mcp/docs" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://ai.fusionauth.dev/mcp/docs`. ## Recent changes - 2026-10-06 21:23 UTC: Tracking started: 2 tools read. Source: automatic check. More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/fusionauth-docs#history (Atom feed: https://mcp.tc/i/fusionauth-docs/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review. ## Details - Server version: 1.0.0 - MCP protocol version: 2025-06-18 - Last checked: 2026-10-07 (reachable) - Listed: 2026-10-06 - Updated: 2026-10-06 --- Source: https://mcp.tc/i/fusionauth-docs (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report