Expense Tracker MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXPENSE_TRACKER_DB_PATH | No | Database location | |
| EXPENSE_TRACKER_CONFIG_PATH | No | Config location |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_expenseC | Add a new expense to the tracker. |
| get_expenseA | Get a single expense by ID. |
| update_expenseC | Update an existing expense. |
| delete_expenseB | Delete an expense. |
| list_expensesA | List all expenses or filter by category. |
| summarize_expensesB | Summarize expenses by category with optional date range and category filter. |
| set_budgetA | Set or update a budget for a category. |
| check_budget_statusC | Check spending against budget for a category/month. |
| add_recurring_expenseC | Add a recurring monthly expense. |
| list_recurring_expensesC | List all recurring expenses. |
| generate_due_recurring_expensesB | Generate expenses for recurring items that are due. |
| export_expenses_csvB | Export expenses to a CSV file. |
| monthly_reportC | Generate a monthly expense report. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| weekly_expense_report | Get a summary of expenses from the past 7 days |
| categorize_expense | Categorize a raw expense description and add it to the tracker |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| resource_categories | Resource: List of all available expense categories and subcategories. |
| resource_recent_expenses | Resource: Recent expenses (last 10). |
| resource_summary | Resource: Current month expense summary by category. |
TDQS
Scored across 13 tools
Most tools target a clear, distinct action: CRUD operations on expenses, recurring expenses, budgets, and reporting. Some overlap exists between monthly_report and summarize_expenses, as both provide aggregated views, but their descriptions sufficiently clarify the monthly vs. customizable category/date scope.
The majority of tools follow a consistent verb_noun snake_case pattern (add_expense, get_expense, list_expenses, set_budget). The main deviation is monthly_report, which is a noun phrase rather than a verb-led name, making the set slightly less uniform but still predictable.
Thirteen tools is appropriate for an expense tracker covering core CRUD, recurring expenses, budgets, reporting, and export. Each tool addresses a meaningful aspect of the domain without excessive duplication or unnecessary surface area.
Expense CRUD is complete, with solid support for recurring expense generation, budgets, summaries, and export. Minor gaps exist: recurring expenses can be added and listed but not updated or deleted, and there is no explicit budget deletion, though these are workable limitations.