firenum Retirement Planner MCP

An official Model Context Protocol server operated by firenum that allows AI assistants to generate personalized FIRE (Financial Independence, Retire Early) retirement plans. It accepts user financial inputs like age, income, savings, and expenses, then returns a detailed projection including Monte Carlo simulations, backtesting against historical market data since 1872, and a direct link to the interactive plan.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-18Operated by firenum

MCP endpoint (Streamable HTTP)

https://firenum.com/mcp

Vendor documentation

What you can do with it

Calculate retirement readiness based on current age and savings
Generate Monte Carlo simulations for investment longevity
Backtest retirement plans against historical market returns
Provide a direct link to an interactive FIRE plan

Tools advertised by the last live check:

build_retirement_plan

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http firenum-retirement-planner-mcp https://firenum.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add firenum-retirement-planner-mcp --url https://firenum.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable firenum-retirement-planner-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "firenum-retirement-planner-mcp": {
      "url": "https://firenum.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "firenum-retirement-planner-mcp": {
      "type": "streamableHttp",
      "url": "https://firenum.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start firenum-retirement-planner-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "firenum-retirement-planner-mcp": {
      "type": "http",
      "url": "https://firenum.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http firenum-retirement-planner-mcp https://firenum.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "firenum-retirement-planner-mcp": {
      "url": "https://firenum.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "firenum-retirement-planner-mcp": {
      "serverUrl": "https://firenum.com/mcp"
    }
  }
}

See all 2,050

Do you run firenum Retirement Planner MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing