Expense Tracker MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EXPENSE_DB_PATH | No | Path to the SQLite database file. Defaults to 'expenses.db' in the project directory. | expenses.db |
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 an expense. |
| remove_expenseA | Remove one expense by its integer ID and return the removed expense. |
| list_expensesA | List expenses, optionally filtered by type and an inclusive date range. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| expense-types | Supported expense types and their sub-expense types. |
TDQS
Scored across 3 tools
Each tool serves a clearly distinct operation: adding, removing, or listing expenses. There is no overlap or ambiguity between them.
All tools follow a consistent verb_noun snake_case pattern: add_expense, remove_expense, list_expenses. The minor singular/plural variation is natural and does not harm consistency.
Three tools is a reasonable, focused set for a simple expense tracker. Each tool covers a necessary core action without unnecessary bloat.
The server covers create, read/delete, and list operations, but lacks an update_expense tool, which is a notable gap for expense tracking since correcting a mistaken amount or category requires delete-and-recreate.