Driggsby

Driggsby is an MCP server for personal finance. You link accounts through Plaid, and your AI client gets read-only MCP tools for transactions, balances, investments, and debts.

Setup

npx driggsby@latest mcp setup

This prompts you to choose a setup path. For Claude Code and Codex, it runs the native MCP setup command. Or specify one:

npx driggsby@latest mcp setup claude-code
npx driggsby@latest mcp setup codex
npx driggsby@latest mcp setup other

After setup, authenticate Driggsby through your client — run /mcp in Claude Code, or sign in through the browser window Codex opens.

So your Driggsby MCP page can tell your CLI sign-ins apart, login sends Driggsby this computer's name and operating system version (for example mbp-studio and macOS 15.6) with its sign-in.

For another MCP client, choose Other. Driggsby currently supports only OAuth-based remote MCP at:

https://app.driggsby.com/mcp

Some driggsby commands work with your Driggsby account directly and need an app token saved on your machine: run npx driggsby@latest login and approve the page it opens (approving in a browser on another computer shows a code to paste, or to finish with npx driggsby@latest login --code <CODE>). The token is stored in your platform keychain when one is available, otherwise in ~/.driggsby/credentials.json, and is never printed. npx driggsby@latest logout removes it.

Building an app

Driggsby hosts small static apps — dashboards, visualizations — each at its own driggsby.dev address. Start one with:

npx driggsby@latest init your-app-name

This creates a working app — index.html, app.js, styles.css, and the driggsby.json that names it. The app reads live data with one call, driggsby.watch(tool, params, callback), and shows sample data when opened on its own.

Preview it with your real Driggsby data:

npx driggsby@latest dev

This runs the app locally, embedded exactly the way Driggsby embeds it after a deploy, and reloads the page when you save a file. While dev runs, the preview serves your financial data to this machine — other websites can't reach it, but anything running locally can, so stop it when you're done: press Ctrl+C, or run npx driggsby@latest dev --stop in the app's folder. It also stops on its own after 30 minutes with no page open. Previews for several apps can run at once; each prints its own addresses. Each data call the page makes prints one line in the terminal, after any retries: a check and how long it took, or a cross and the reason.

Deploying an app

From a folder holding a driggsby.json ({ "slug": "your-app-name", "serve": "." }) and an index.html:

npx driggsby@latest deploy

The first deploy creates the app: Driggsby assigns its address — the name you picked plus a unique ending, like your-app-name-x7k2qf.driggsby.dev — and saves the assigned name back into driggsby.json, so any readable name works and names never collide. deploy prints the Driggsby page for the app first; that is where it runs with your data. The driggsby.dev address is the app on its own, which shows no Driggsby data when opened directly. If the project lives in git, commit the updated driggsby.json — it is the only record of your app's address, and a fresh checkout without it would create a second app. Every deploy after that uploads only the files that changed. Deploy with --preview to upload a version without changing what visitors see, npx driggsby@latest versions to list every kept version, and npx driggsby@latest rollback to switch which one is live — switching re-uploads nothing. npx driggsby@latest delete removes a deployed app forever, after asking you to type its address name back (--yes for scripts). npx driggsby@latest query <tool> runs one read-only data tool and prints its result as JSON, the same shape a driggsby.watch callback receives, so you can see the data before writing any render code.

The CLI is pure TypeScript and installs from the npm registry alone — no binary downloads, no install scripts — and runs on macOS, Linux, and Windows with Node.js 18 or newer.

See the GitHub repo for tools, examples, and full documentation.

Transaction rules

npx driggsby@latest rules reads and changes your transaction rules — your standing corrections to how Driggsby reads your transactions: a category, a counterparty's name, or tags on a set of transactions. rules describe prints the rule format and the process. rules preview shows exactly what a new or changed rule would do and returns the confirm token rules save needs to apply it; renaming, pausing, or resuming a rule needs its rule_ref and no preview. rules delete needs --yes. Every action prints JSON.

Items

npx driggsby@latest items saves and removes the items behind your charges: what an order or a receipt actually bought, each in a category, so Driggsby counts a charge by what was in it. items describe prints the item format and the process. items save --params-file order.json saves the items of up to 25 charges (saving a charge again replaces its items); each charge is saved or refused on its own, and the JSON result says which and why. items delete needs --yes. Read items back with npx driggsby@latest query query_item_sql --sql "...".

License

Apache-2.0. The bundled Inter font (assets/Inter.woff2), which driggsby dev serves to the app it previews, is under the SIL Open Font License 1.1; see assets/Inter-LICENSE.txt.