All servers / Finance / ProjectionLab MCP server
ProjectionLab MCP server
MCP server for ProjectionLab: read and safely edit your retirement plan from any MCP-compatible AI assistant
Tested by ConnectATDScore 86 out of 100. Tested 2026-11-19 on package version 1.3.0. Package: projectionlab-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (2.6 seconds including download)
- Tools offered: 23
- Last published: 2026-11-16
- Weekly downloads (npm): 710
- License: MIT · Direct dependencies: 4
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
projectionlab_get_bootstrapno parametersReturns a JavaScript snippet the user pastes into the ProjectionLab tab's devtools console to connect that tab to this server - a zero-install alternative to the browser extension. Use when check_connection reports no executor connected and the user has not installed the extension. The snippet lasts until the tab reloads.
projectionlab_check_connectionno parametersVerify connectivity to ProjectionLab. Checks that the browser is running, the ProjectionLab page is loaded, the Plugin API is accessible, and the API key is valid. Also reports writesEnabled, which is true only while the connected browser extension's "Enable agent plan edits" switch is on; while it is false every write tool, dry runs included, is refused. Call this first in every session, before any other ProjectionLab tool. If any check fails, read the projectionlab://guide resource and walk the user through the fix. The result also carries versions (server, executor, latest npm release) and notices: plain sentences to relay to the user when a release is out of date. apiContract is the Plugin API contract the page offers: 1 on ProjectionLab 4, 2 on ProjectionLab 5, which has no progress write.
projectionlab_describe_plugin_apino parametersLists the methods and properties exposed by window.projectionlabPluginAPI in the running app build. Use this to discover undocumented capabilities (e.g. reading computed projection results) before assuming a method does not exist.
projectionlab_export_datano parametersExport the complete current state from ProjectionLab as a JSON object: plans, current finances, settings, and progress (ProjectionLab 4) or account history (ProjectionLab 5). The layout differs by version. This is the primary source of truth. WARNING: the full export is very large; results over the inline limit are saved to a file and a pointer is returned. Prefer projectionlab_get_plan or projectionlab_get_plan_section for targeted access. Write tools snapshot automatically, so a manual pre-write export is NOT required.
projectionlab_describe_schemano parametersReturns a lightweight summary of the ProjectionLab data structure without the full payload. Includes top-level keys, account list (IDs, names, types, balances; asset rows report marketValue and loanBalance in place of balance, with type "real-estate" for real estate), plans (IDs, names, and each plan's income, expense, and milestone event counts), and the progress entry count. On ProjectionLab 5 the account rows carry the stored kind (account, debt, real-asset) and type, a real asset reports value, a debt reports balance and securedByAssetId, archived accounts are listed apart under archivedAccounts, the keys name each documents.* section, and accountHistory counts the per-account history in documents.accountHistory (ProjectionLab 5 exports no progress section). Use this to understand the data model before crafting queries or mutations.
projectionlab_get_summaryno parametersReturns a compact inventory of CURRENT finances: net worth as of today (account balances plus asset market values, minus debts and asset loans; not a projected outcome), account breakdown by type (assets totaled at market value), and each plan's name with its income, expense and milestone event counts. On ProjectionLab 5 the account breakdown is keyed by the stored kind and type (for example "account:taxable", "real-asset:land", "debt:secured-loan"), real assets carry their equity after the debts that name them in securedByAssetId, and archived accounts are listed apart and left out of every total. It does not return ending net worth or Chance of Success and must not be used to judge a plan change's impact.
projectionlab_get_plan1 of 1 parameter describedReturns a single plan by name or ID. Much smaller than export_data. Use this for deep analysis of a specific plan; prefer projectionlab_get_plan_section when only one aspect is needed. Accepts a plan name (case-insensitive; a partial match must identify exactly one plan) or exact plan ID.
projectionlab_get_plan_section5 of 5 parameters describedReturns a specific section of a plan (e.g., just milestones, income, expenses, accounts, variables, etc.). Much smaller than a full plan export. Narrow further with eventIdentifier (single event by name/ID) or path (dot-path within the section, e.g. 'events[2].rothConversions'). Set listPaths=true to flatten the selected object into discrete, typed dot paths that can be used with projectionlab_update_plan_event pathChanges. Use this for targeted analysis of a specific aspect of a plan.
projectionlab_get_plan_settings2 of 2 parameters describedLists discrete, path-addressable configuration values for one plan. Covers general assumptions and tax controls (variables), Chance of Success configuration (the montecarlo section; trials over historical market periods, with randomized sampling as an option), and withdrawal strategy settings (a compare mode that replaces most other plan events while it is enabled). Nested objects are flattened to dot paths while ordered arrays remain intact. Advanced rate schedules also expose indexed control-point fields so one year or rate can be patched without replacing the schedule. Use the returned paths and JSON types with projectionlab_update_plan_settings. On ProjectionLab 5 the result also carries planSelection, the workspace's plan settings (active and baseline plan ids, alignment, tabs); a value the export leaves null reads 'not reported', and mutableWith is null while writes are unsupported there.
projectionlab_get_current_finances3 of 3 parameters describedReturns just the Current Finances section (account balances, debts, real estate) without plan data. Narrow to one existing account by exact ID, and set listPaths=true to discover typed dot paths for projectionlab_update_account pathChanges. Real-estate assets (assets entries with type "real-estate") carry a realEstate block that labels the fields ProjectionLab stores confusingly: marketValue is the stored amount, loanBalance is the remaining loan balance (never the property's value; an absent balance reads as 0), and netEquity is marketValue minus loanBalance, an arithmetic on stored fields and not ProjectionLab's own net-worth figure, which can depend on excludeLoanFromLNW. The block also carries paymentMethod, classification and excludeLoanFromLNW where present, loan terms (apr, interestType, monthlyPayment, compounding) when paymentMethod is "financed", and carrying costs (propertyTax, insurance, maintenance, monthlyHOA, appreciation) where present. Values come from the Current Finances record only, never from plan-modeled asset events. Only the amount and balance labels are verified; the other labels name stored fields whose UI meaning is not yet confirmed. Raw fields are kept unchanged alongside the block. On ProjectionLab 5, accounts are records in `accounts` keyed by id and narrowed by kind (account, debt, real-asset), with their v5 type strings kept as stored. Each real-asset record carries a realAsset block: value, purchasePrice, loanBalance (the balances of the unarchived debts whose securedByAssetId names it), equity (value minus loanBalance) and securedDebts; a debt without securedByAssetId is tied to no asset. Archived accounts (archivedOn) are left out of `accounts` and listed under archivedAccounts unless includeArchived is true.
projectionlab_diff7 of 7 parameters describedReports field-level differences, read-only: it never writes and never snapshots, so it works while plan edits are turned off. Two modes, told apart by the arguments you supply. Points in time: from is required and names a saved snapshot with exactly one of snapshotId, nBack or beforeTime, resolved the way projectionlab_rollback resolves them. to is optional: another snapshot selector, or omitted to compare against the data in ProjectionLab right now. Only the data sections the from snapshot holds are compared, and when to is a snapshot, only the sections both hold; comparedSections says which. For plans it reports plans added, removed and changed, and within a changed plan the events added, removed and modified per section, each modification as "path": "before → after" dot paths you can read back with projectionlab_get_plan_section or patch with projectionlab_update_plan_event. Computed plan fields (lastUpdated, simKey, meta) are left out, so a plan ProjectionLab merely re-saved reads as unchanged. For Current Finances it reports rows added, removed and modified by id within each collection. Use it to confirm a write landed as intended, to explain to the user what changed, or to see what projectionlab_rollback would undo before rolling back. Narrow the output with planIdentifier (plan name or ID) and section. Two plans: planA and planB name two different plans and compare one against the other, so a plan rebuilt by hand in the ProjectionLab UI can be checked against the original. Both plans are read from the live app, or from one snapshot when from is also given; planA and planB cannot be combined with to or planIdentifier. Events match by name plus occurrence. The fields that say which plan an object is (the plan's id and name, each event's own id) and the computed fields are left out, as is each event's random key, which ProjectionLab assigns when the event is created, so re-entering the same event does not read as a difference. A reference from one event to another event of the same plan, such as a milestone id in a start or end condition, is compared by the event it names, so the same milestone still compares equal under the unrelated ids two plans store. Each section reports onlyInA, onlyInB, different (each with "path": "planA value → planB value") and sameCount; planSettings reports the plan's own fields outside the sections. Use it to answer "does the plan I rebuilt match the original?" In either mode pathsOnly: true reports the paths that differ with no values, for a comparison whose values are private. Any value whose path names a credential (apiKey, token, password, ...) is reported as [REDACTED] rather than shown, and a value longer than 200 characters is truncated with its original length. Output is capped at 200 field changes, with omittedFieldChanges and per-entry omittedChanges counting the rest; a difference past the cap is still counted as changed.
projectionlab_update_account5 of 5 parameters describedSafely patches one existing account, debt, or real asset in Current Finances. Use pathChanges for nested fields so siblings are preserved; discover valid paths with projectionlab_get_current_finances using accountId and listPaths=true, and see projectionlab://data-model for field units and allowed values. The legacy data input shallowly patches top-level fields. Supply exactly one patch mode. Dry runs validate the account and return before/after values as a field-level safety diff, not a plan-impact measure. Confirmed changes snapshot Current Finances, send only changed top-level fields, and verify every requested path.
projectionlab_update_plan_section5 of 5 parameters describedSafely updates ONE section of ONE plan. Replaces the specified section (e.g., income, expenses, accounts) while leaving all other sections and plans untouched. When confirm is false (default), returns a dry-run diff (added/removed/modified events with field-level changes) showing what would change. When confirm is true, auto-snapshots all plans, rebuilds with the updated section, and calls restorePlans. Prefer projectionlab_update_plan_event when changing a single event - it is smaller and safer. IMPORTANT: Always fetch fresh section data via projectionlab_get_plan_section before constructing sectionData - never mutate from stale data. Pass the dry-run's planVersion as expectedPlanVersion when confirming so a plan saved in the meantime is not overwritten.
projectionlab_update_plan_event6 of 6 parameters describedPatches ONE event (income source, expense, account, asset, milestone, or priority) within ONE plan. Use pathChanges for nested fields so nested siblings are preserved; get valid paths from projectionlab_get_plan_section with eventIdentifier and listPaths=true. See projectionlab://data-model for field units and allowed values. The legacy patch input shallowly merges top-level fields and replaces any nested object supplied there; existing fields keep their JSON type and new fields must be plain, non-secret names. Supply exactly one of patch or pathChanges. All sibling events are preserved. This is the PREFERRED write tool for single-event changes: much smaller and safer than regenerating a whole section. When confirm is false (default), returns a dry-run field-level diff. When confirm is true, auto-snapshots all plans, applies the patch, and verifies.
projectionlab_update_plan_settings4 of 4 parameters describedSafely patches discrete existing settings in ONE configuration section of ONE plan. Paths come from projectionlab_get_plan_settings and may address nested fields, such as "estate.enabled". Sibling values are preserved server-side. Unknown paths and JSON type changes are rejected, and values outside an observed field's allowed values are refused; see projectionlab://data-model for units and allowed values. When confirm is false (default), returns a dry-run diff. When confirm is true, auto-snapshots all plans, restores the patched plan, and verifies each value.
projectionlab_clone_plan3 of 3 parameters describedCopies one plan to a new plan with a new name, for what-if scenarios. Every existing plan is left as it is; the copy is appended. Event ids are kept, as ProjectionLab's own plan duplication does, so references between events, milestones and accounts stay intact. When confirm is false (default), returns a dry-run preview. When confirm is true, auto-snapshots all plans, appends the copy, and verifies the other plans are unchanged and that no Current Finances balance moved. Edit the copy afterwards with projectionlab_update_plan_event or projectionlab_update_plan_settings. projectionlab_rollback on the snapshot removes the copy.
projectionlab_delete_plan2 of 2 parameters describedPermanently removes one plan by exact plan ID; names are never matched, so get the ID from projectionlab_describe_schema first. Refuses the last remaining plan. When confirm is false (default), returns a dry-run preview. When confirm is true, auto-snapshots all plans, writes the remaining plans, and verifies the deleted plan is gone while every other plan is unchanged. projectionlab_rollback on the snapshot restores the deleted plan.
projectionlab_restore_current_finances2 of 2 parameters describedREPLACES the Current Finances state with the provided data. On ProjectionLab 4 this is a FULL REPLACEMENT, not a patch - the entire current finances object is overwritten. On ProjectionLab 5 every non-account field and each submitted account is replaced whole, but an account missing from the submission is kept, not deleted; the preview lists those as keptAccounts. When confirm is false (default), returns a dry-run preview WITHOUT modifying anything. When confirm is true, auto-snapshots current state then applies the replacement. Use projectionlab_rollback with that snapshot to undo it; a manual export first is not needed.
projectionlab_restore_plans2 of 2 parameters describedREPLACES ALL plans with the provided array. This is a FULL REPLACEMENT - every existing plan is overwritten. An empty array is refused. When confirm is false (default), returns a detailed dry-run diff showing plans added/removed/modified with per-section event count changes. When confirm is true, auto-snapshots current plans then applies the replacement. Use projectionlab_rollback with that snapshot to undo it; a manual export first is not needed.
projectionlab_restore_progress2 of 2 parameters describedREPLACES the Progress state with the provided data. This is a FULL REPLACEMENT, not a patch. When confirm is false (default), returns a dry-run preview. When confirm is true, auto-snapshots then applies the replacement. Use projectionlab_rollback with that snapshot to undo it; a manual export first is not needed. Not available on ProjectionLab 5, which records Progress history by itself.
projectionlab_restore_settings2 of 2 parameters describedREPLACES the Settings state with the provided data. This is a FULL REPLACEMENT, not a patch. A secret field that a read returned as [REDACTED], such as the Plugin API key, keeps its stored value; leave it as [REDACTED]. A payload that leaves out a stored secret is refused, since the replacement would erase it. When confirm is false (default), returns a dry-run preview. When confirm is true, auto-snapshots then applies the replacement. Use projectionlab_rollback with that snapshot to undo it; a manual export first is not needed.
projectionlab_list_snapshotsno parametersReturns a list of available data snapshots with timestamps, the operation that triggered them, and which data sections were saved. Snapshots are created automatically before any write operation.
projectionlab_rollback4 of 4 parameters describedRestores ProjectionLab data from a previously saved snapshot. Choose the snapshot with exactly one of snapshotId (an exact ID), nBack (how many snapshots back, 1 being the most recent) or beforeTime (the latest snapshot strictly before an ISO 8601 time carrying an explicit Z or ±HH:MM offset). nBack and beforeTime rank snapshots newest first, the order projectionlab_list_snapshots shows, and count every saved snapshot including the pre-rollback snapshot a confirmed rollback writes, so nBack 1 is the top of that list. When confirm is false (default), shows the resolved snapshot and what the rollback would restore. When confirm is true, applies the rollback by calling the appropriate restore methods. Use projectionlab_list_snapshots to find available snapshot IDs.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.