factreason_auth_playbook — FactReason MCP Tool
factreason_auth_playbook
(factreason auth playbook) is one of 11 tools on the
FactReason
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call factreason_auth_playbook from your client
- Claude Code FactReason factreason_auth_playbook run in your project directory
- Claude Desktop FactReason factreason_auth_playbook ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FactReason factreason_auth_playbook ~/.cursor/mcp.json
- VS Code FactReason factreason_auth_playbook .vscode/mcp.json
- Zed FactReason factreason_auth_playbook ~/.config/zed/settings.json
- Windsurf FactReason factreason_auth_playbook ~/.codeium/windsurf/mcp_config.json
- Cline FactReason factreason_auth_playbook ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FactReason factreason_auth_playbook ~/.gemini/settings.json
- Grok FactReason factreason_auth_playbook .mcp.json (in your project root)
- ChatGPT FactReason factreason_auth_playbook Settings → Connectors → Advanced → Developer mode
- Claude.ai FactReason factreason_auth_playbook Settings → Connectors → Add custom connector
- LangChain FactReason factreason_auth_playbook pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http factreason https://www.factreason.com/mcpOther 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.