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