search_fusionauth_sources — mcp docs MCP Tool Read-only
search_fusionauth_sources
(search fusionauth sources) is one of 2 tools on the
mcp docs
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call search_fusionauth_sources from your client
- Claude Code mcp docs search_fusionauth_sources run in your project directory
- Claude Desktop mcp docs search_fusionauth_sources ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor mcp docs search_fusionauth_sources ~/.cursor/mcp.json
- VS Code mcp docs search_fusionauth_sources .vscode/mcp.json
- Zed mcp docs search_fusionauth_sources ~/.config/zed/settings.json
- Windsurf mcp docs search_fusionauth_sources ~/.codeium/windsurf/mcp_config.json
- Cline mcp docs search_fusionauth_sources ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI mcp docs search_fusionauth_sources ~/.gemini/settings.json
- Grok mcp docs search_fusionauth_sources .mcp.json (in your project root)
- ChatGPT mcp docs search_fusionauth_sources Settings → Connectors → Advanced → Developer mode
- Claude.ai mcp docs search_fusionauth_sources Settings → Connectors → Add custom connector
- LangChain mcp docs search_fusionauth_sources pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp-docs https://ai.fusionauth.dev/mcp/docsOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.