ProjectionLab MCP Server

MCP server for ProjectionLab — export, snapshot, and restore your financial plans. Includes a built-in FIRE advisor knowledge base for analyzing Financial Independence scenarios.

Why this approach

Most MCP servers that connect to third-party services ask you to paste API keys into config files, environment variables, or .env files. That key then lives on disk, gets passed through the MCP protocol, and travels through the AI conversation — where it can end up in logs, history, or training data.

This server works differently:

• Your API key never leaves the browser. The key is extracted from the ProjectionLab settings page, stored in the browser's sessionStorage, and used there. The MCP server never sees it. The AI never sees it. It doesn't exist in any config file, environment variable, or conversation log. Other ProjectionLab MCPs store the key in plaintext files on disk or pass it through environment variables.

• Everything runs in a browser you can see. This server doesn't make hidden API calls on your behalf. It generates JavaScript that executes in a browser tab where ProjectionLab is open. You can watch every operation happen in real time — open DevTools, inspect network requests, see exactly what's being read or written. Nothing is opaque. Other approaches run headless browsers in the background where you can't observe what's happening.

• Zero infrastructure. No bundled Chromium, no background daemons, no Firefox + GeckoDriver, no Rust toolchain. The only dependencies are the MCP SDK and zod. It works with whatever browser MCP you already have running.

• Snapshots are redacted automatically. When you save financial data locally, any field named key, apiKey, or pluginKey is replaced with [REDACTED] before writing to disk.

• Published with provenance. Every release is built and published from GitHub Actions via npm trusted publishing. No long-lived tokens, no manual publishes. You can verify that the package on npm was built from this repo — npm audit signatures confirms the cryptographic link between the published tarball and the exact commit that produced it.

The trade-off is that you need a browser automation MCP running alongside this one. But for something as sensitive as your financial data, that transparency is worth it.

Features

• Guided API key setup — securely extracts and validates the key entirely in the browser

• Full data export — returns a script that exports all plans, accounts, income, expenses, and settings

• Local snapshots — save exports as timestamped JSON files with automatic API key redaction

• Snapshot restore — generate scripts to restore plans and current finances from any snapshot

• FIRE knowledge base — curated resource with links to FIRE concepts, withdrawal strategies, and ProjectionLab help docs

Prerequisites

This server generates JavaScript that must be executed in a browser where ProjectionLab is open. You need a browser automation MCP alongside this one:

• Chrome DevTools MCP or Playwright MCP

• A ProjectionLab Premium account with Plugins enabled

API

Tools

• pl_setup

  • Guided two-step API key configuration

  • Step 1 (no args): returns the settings URL, a browser extraction script, and setup instructions

  • Step 2 (validationResult): confirms the key is valid and ready

  • The extraction script reads the key from the DOM, stores it in sessionStorage, and validates it — all client-side

• pl_export

  • Returns a JavaScript string that exports all ProjectionLab data

  • Execute the script in the browser; pass the result to pl_snapshot to save it

  • Annotations: readOnlyHint: true

• pl_snapshot

  • Saves export data as a local JSON file

  • Input: data (required) — the export result from running the pl_export script in the browser

  • Input: label (optional) — appended to the snapshot filename

  • API keys are automatically redacted before writing

• pl_list_snapshots

  • Lists all saved snapshots, sorted newest first

  • Returns filename, path, creation time, and size

  • Annotations: readOnlyHint: true

• pl_restore

  • Reads a snapshot file and returns JavaScript strings to restore the data

  • Input: snapshotPath (required) — absolute path to the snapshot file

  • Returns one script per data section (plans, current finances); execute each in order

  • Always take a snapshot of the current state before restoring

Resources

• projectionlab://knowledge

  • Curated index of ProjectionLab documentation URLs organized by topic

  • Covers FIRE concepts, withdrawal strategies, and ProjectionLab features

Usage with Claude Desktop

Add this to your claude_desktop_config.json:

NPX

{
  "mcpServers": {
    "projectionlab": {
      "command": "npx",
      "args": ["-y", "@mormubis/projectionlab-mcp"]
    }
  }
}

Local (from source)

{
  "mcpServers": {
    "projectionlab": {
      "command": "node",
      "args": ["/path/to/projectionlab-mcp/dist/index.js"]
    }
  }
}

Usage with VS Code

Add this to your .vscode/mcp.json:

{
  "servers": {
    "projectionlab": {
      "command": "npx",
      "args": ["-y", "@mormubis/projectionlab-mcp"]
    }
  }
}

Configuration

Security

The API key never leaves the browser. During setup, a script runs inside the browser tab to read the key from the DOM, store it in sessionStorage, and validate it against the Plugin API. The only value that returns to the conversation is a boolean.

All other scripts (export, restore) read the key from sessionStorage at runtime. Snapshots are redacted before writing — any field named key, apiKey, or pluginKey is replaced with [REDACTED].

Build

npm install
npm run build

License

This project is licensed under the MIT License. See LICENSE for details.