Your Money Left The Chat
@Rayato159
A Rust + MCP powered financial tracker that knows exactly where your money ghosted you.
Overview
What is Your Money Left The Chat?
Your Money Left The Chat is a Rust-native, SQLite-backed financial tracking system that uses LLMs (Claude or Ollama) to log spending, analyze habits, and calculate taxes via natural conversation. It stores all data locally, with no cloud dependency.
How to use Your Money Left The Chat?
Install Rust, SQLite, and Make, clone the repository, install Diesel CLI, create a database.db file, run database migrations (make migrate-up), build the project (make build-release), add the binary and database path to your MCP agent’s config.json, then chat with the agent to log expenses.
Key features of Your Money Left The Chat
- Natural language input for logging expenses
- Smart summaries (daily, monthly, yearly breakdowns)
- Graph view for visualizing spending (Claude only)
- Tax calculation to estimate owed amounts
- Offline and local-first: no internet or accounts required
Use cases of Your Money Left The Chat
- Log daily expenses like “Spent 129 baht on KFC today” via chat
- Get category-based spending summaries over time
- Visualize monthly food costs with Claude’s graph view
- Estimate tax obligations based on recorded spending
FAQ from Your Money Left The Chat
How does it differ from cloud-based money trackers?
It is fully offline and local-first. All data is stored in a SQLite file on your machine, with no internet, accounts, or cloud surveillance.
What are the dependencies and runtime requirements?
You need Rust, SQLite, GNU Make, and Diesel CLI (with the SQLite feature). The system runs as a local binary and requires an MCP-compatible agent (Claude or Ollama with mcp-cli).
Where is my financial data stored?
Data is stored in a single database.db SQLite file whose path you provide when configuring the MCP server. Nothing is sent to any external service.
What transport protocol does it use?
It uses the Model Context Protocol (MCP) to communicate with the LLM agent. Authentication is not mentioned—access is defined by your MCP agent configuration.
