Cinderfi MCP Server

Compatible with Claude Code, Cursor, VS Code Copilot, OpenAI Codex, Gemini CLI, Goose, and any other MCP- or [Agent

Remote serverstreamable-http

What is the Cinderfi MCP MCP server?

Compatible with Claude Code, Cursor, VS Code Copilot, OpenAI Codex, Gemini CLI, Goose, and any other MCP- or Agent Skills-compatible agent. That is what the cinderfi mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

  • Retirement projections (single + couples)
  • CPP / OAS / Social Security timing
  • Tax calculations (all Canadian provinces + US states)
  • GIS eligibility and clawback analysis
  • RRSP meltdown / Roth conversion strategy
  • Monte Carlo simulation

The tools it exposes

The server publishes 5 tools. What each one is for:

  • Endpoint — ** https://mcp.cinder.fi/mcp
  • Auth — ** Authorization: Bearer YOUR_API_KEY (or the auth.md registration flow)
  • Transports — ** Streamable HTTP, SSE
  • Optimizer — —
  • Backtest — —

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

What it needs from you

Configuration is passed through the environment: AUTHORIZATION, CINDERFI_MCP_KEY, YOUR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Cinderfi MCP's toolset — Endpoint, Auth, Transports and 2 more — is a fair guide to whether it matches your workflow. It is maintained by cinderfi; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Cinderfi MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Endpoint** https://mcp.cinder.fi/mcp
Auth** Authorization: Bearer YOUR_API_KEY (or the [auth.md](https://cinder.fi/auth.md) registration flow)
Transports** Streamable HTTP, SSE
Optimizer
Backtest

How to install the Cinderfi MCP MCP server

{
  "mcpServers": {
    "cinderfi": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.cinder.fi/mcp"],
      "env": {
        "AUTHORIZATION": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
AUTHORIZATIONConfiguration value read at startup.Optional
CINDERFI_MCP_KEYCredential the server authenticates with.Yes
YOUR_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Cinderfi MCP to Endpoint.
  • Use Cinderfi MCP to Auth.
  • Use Cinderfi MCP to Transports.

Frequently asked questions

It connects Cinderfi MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (Endpoint, Auth, Transports, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Cinderfi MCP directly.