cove-fi
MCP server for cove-fi, a deterministic retirement and financial-independence projection engine. It lets users run plans, create scenarios, and explore year-by-year net-worth projections through natural language.
README
cove-fi
Cove FI (@walensis/cove-fi) is a deterministic, annual retirement /
financial-independence projection engine — plan files in, a year-by-year
net-worth projection out, with a CLI and an MCP server so you can run it
from a terminal or just talk to it from Claude Desktop, Claude Code, or
Cursor. It's the Project module of the Cove suite (Balance → Plan →
Project), but works entirely standalone.
Cove for YNAB manages this month's money; Cove FI projects the next forty years. Each works alone; together they talk.
Quickstart
npm install -g @walensis/cove-fi # or: npx @walensis/cove-fi <command>
cove-fi init my-plan.toml # scaffold a starter plan
# edit birth_year, salary amount, and retirement_year in my-plan.toml
cove-fi run my-plan.toml # project it
cove-fi scenario my-plan.toml --retirement-year 2048 # try a scenario
Set an income's end = "retirement" (the scaffolded salary already is) and
it ends automatically the year before retirement_year — including under a
--retirement-year scenario override, which moves it too.
Full walkthrough, MCP setup, and command reference:
packages/cove-fi/README.md.
Onboarding
Wire up the MCP server (see docs/clients/ for
Claude Desktop, Claude Code, and Cursor setup), then just say "set up my
retirement plan." Clients that surface MCP prompts can run the onboard
guided flow directly; everywhere else, just asking works — the tools are
self-describing. Either path checks for existing plans, offers YNAB
seeding, walks you through the rest by hand, and finishes with a
projection, a Monte Carlo run, and a save.
Plans are discovered from ~/.cove-fi/plans (override with
COVE_FI_PLANS). YNAB seeding (via @walensis/ynab-client) needs
COVE_FI_YNAB_TOKEN or YNAB_TOKEN set to a YNAB Personal Access Token;
without one, seed_from_ynab just says so instead of erroring. Seeding is
always propose-only — it never writes to your plan on its own, it
returns numbers for you to confirm before they go into create_plan or
update_plan.
Docs
docs/ASSUMPTIONS.md— every default value and its citationdocs/SEMANTICS.md— the engine's rules: the contribution waterfall, drawdown order, sentinels, and moredocs/VALIDATION.md— how the engine is validated against published research and primary sourcesdocs/clients/— MCP setup for Claude Desktop, Claude Code, and Cursor
Validation
The engine is validated against published research and primary sources —
closed-form math, cross-plan invariants, IRS-table pins, and a Monte Carlo
benchmark against the Trinity-study withdrawal-rate literature. See
docs/VALIDATION.md for the full methodology,
citations, and an honest accounting of current limitations.
Roadmap
- 0.2 — Monte Carlo simulation (historical block-bootstrap returns)
- 0.3 — conversational onboarding (guided interview, plan discovery, propose-only YNAB seeding). Shipped.
- 0.4 — integrations (third-party import/export), bond series/portfolio mixes
License
MIT — see LICENSE.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.