Expense MCP server

Expense

Expense is a seamless receipt tracking solution: receipts are automatically

sent via email, mileage uses the tax rate provided by the IRS, and a smart AI

assistant does your data entry so that you can forget about the process

altogether.

Screenshots

What it does:

category, merchant, amount) and mileage expenses (map a route on the map, powered by Leaflet + OSRM, using the per year mileage rate)

• Log receipt expenses (upload/scan the image, specify the date, report,

the receipt will be parsed and automatically added (see below)

• Forward your receipt to the email associated with your Expense account, and

saved and automatically renamed to YYYY-MM-DDReportName.jpg

• Reports and categories to organize your expenses into; every receipt image is

archive

• Export: as a PDF (one PDF per report with receipt images attached) and a ZIP

Stack:

settings, mileage, image blobs

• React Router v8 (framework mode) + Tailwind v4, TypeScript
• Postgres via Prisma: accounts, users, expenses, reports, categories,

storage

• Images: Postgres BYTEA (production and development/test), with no external

deploys)

• Deployed on Vercel + Supabase Postgres (git push to main automatically

Auth and accounts:

account is separate from other ones

• Email/password login (hashed with scrypt), sessions with signed cookies
• Multi-user accounts: everything in one account is shared between users, each

Settings) and can sign up to a new account from scratch; image keys are namespaced by an account so that two accounts won't interfere

• A user can join an account by entering an 8-character invite code (visible in

Accounts and sharing

Email/password login: email is the login name, stored in lowercase and validated, and unique at signup/join. All expenses, reports, categories, and settings belong to an account; everything in an account is shared between users, and accounts are fully isolated from each other.

existing account and share its data.

• Sign up -> creates an entirely new account (empty).
• Join -> enters an account invite code (Settings -> Account) to join an

the database is empty; pre-existing accounts get their login restored from APP_EMAIL on the first launch (initStore).

• The first account/user is bootstrapped from APPEMAIL/APPPASSWORD when

SEO and AI discovery

Marketing pages that are available publicly double as the AI search surface: if an assistant is asked for an expense tracker, the GPTBot / OAI-SearchBot / ClaudeBot / PerplexityBot crawler quotes them. The copy is written in such a way that it's easily quotable and includes the app name and the URL and lives only in one place, the content files under app/data/ (one markdown or YAML file per page, parsed by app/lib/content.server.ts), which render all the surfaces:

Plumbing to support it: public/robots.txt explicitly permits the AI crawlers while app routes are blocked, and public/sitemap.xml lists the public pages.

Shortened. The full README is on GitHub.