Planomy Planner

io.github.demorphed6-lgtmPublished by GitHub account demorphed6-lgtmv0.1.0Updated Oct 24, 2026

Retirement planning on your own machine: projections, Monte Carlo, scenarios, budgets, plan edits.

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

A local MCP server for retirement planning that lets an assistant run projections, Monte Carlo simulations, scenarios, budgets and plan edits on your ownmachine

What you can do
Run retirement projections and Monte Carlo simulations to model outcomes over time. Compare scenarios and adjust assumptions to see how results change. Work with budgets and make edits to an existing retirement plan. All computation happens locally on the user's machine.
When to use it
Useful when you want an assistant to help explore retirement scenarios, stress-test assumptions with Monte Carlo runs, or adjust a budget and plan without sending financial details to an outside service.
Requirements
Runs as a local process on the user's machine, installed from the provided MCPB package; desktop only. No authentication, environment variables or headers are declared.
Before you install
It handles personal financial and retirement data and can edit plans and budgets, so changes should be reviewed before relying on them. Projections and simulations are models, not financial advice. No credentials are requested, but confirm where any saved plan data is stored locally.

Installation

In SourceWeft

  1. Open Planomy Planner in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.