Spendlog MCP Server

If you already use Spendlog, the spendlog mcp server is the piece that lets your assistant work with it directly. Local-first cost & expense tracking for solo entrepreneurs — MCP server for Claude Code & Claude Desktop with budgets, invoices, recurring expenses & CSV export. No account, no cloud.

What the server does

Track what your business spends, manage budgets, write invoices — all in natural language. Your data stays 100% local in SQLite. Nothing leaves your machine.

• Zero context-switching — — log costs while you build, right where you already work
• Local-first — — all data in ~/.spendlog/spendlog.db, no account, no cloud
• Natural language — — no forms, no menus, just tell Claude what you spent
• 38 tools — — invoicing, budgets, recurring expenses, CSV export, multi-project tracking
• Multilingual — — English and German (EN/DE), with i18n ready for more

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Category — Tools
• Transactions — add_expense add_income list_transactions update_transaction delete_transaction
• Analysis — get_summary get_category_breakdown compare_periods get_tax_summary
• Invoices — create_invoice list_invoices get_invoice mark_invoice_sent mark_invoice_paid delete_invoice duplicate_invoice
• Budgets — set_budget get_budget_status list_budgets update_budget delete_budget
• Recurring — create_recurring list_recurring delete_recurring process_recurring
• Projects — create_project list_projects rename_project delete_project
• Categories — list_categories add_category delete_category
• Export — export_transactions export_invoices export_for_tax_advisor
• Settings — get_profile set_profile get_notifications

Credentials and setup notes

Configuration is passed through the environment: DATABASE_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

The server ships on npm as spendlog, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Spendlog's toolset — Category, Transactions, Analysis and 7 more — is a fair guide to whether it matches your workflow. It is maintained by makz81; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Spendlog's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Spendlog.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.