Product
Track My Spend: personal finance, emotional spending, and MCP
A bilingual expense tracker combining multi-currency records, emotional spending insights, and reviewed AI imports through MCP.
A bank statement can show where money went without explaining what the purchase meant. Track My Spend brings financial records and spending context into the same English and Spanish application.
From individual purchases to a monthly picture
The workflow starts with manually recording expenses, income, and savings. Categories and subcategories organize the records, while monthly charts compare spending patterns and the equivalent period of the previous month.
Expenses can carry an emotion and a satisfaction score. These fields make room for reflection alongside totals. They are personal observations, rather than a diagnosis or financial advice.
A web product with a reviewable assistant workflow
Next.js and TypeScript provide the application, with Prisma and PostgreSQL storing accounts and financial records. The dashboard supports multiple currencies and English and Spanish routes.
Text-based imports propose transactions for review. A separate MCP interface lets an authorized assistant retrieve categories, preview a classified batch, and save confirmed expenses. The assistant classifies the text; the MCP server validates and stores the proposed records.
What the current version does and does not establish
This is a manual tracker, with no automatic bank synchronization. Imported amounts, dates, and classifications need review. An expense preview token can be reused during its validity window, so repeating a commit can create duplicates.
The hosted application and a fresh self-hosted installation are different experiences. Payment-based registration and service-specific integrations remain in the code, and an open-source license has not yet been selected.
Where to explore the project
The repository documents the dashboard, setup, and MCP tools. Its self-hosting guide explains the database and account preparation that a fresh installation needs. The release checklist records the remaining work toward a community release.
Sources and further reading
Based on the linked project documentation, reviewed on 2 November 2026. Capabilities and limitations describe that documented version.
View repository