ExpenseTracker MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_HOST | No | The database host | localhost |
| DB_NAME | No | The database name | expense_tracker |
| DB_PORT | No | The database port | 5432 |
| DB_USER | No | The database user | expense_user |
| DB_PASSWORD | Yes | The database password |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_expenseD | – |
| read_expenseD | – |
| update_expenseD | – |
| delete_expenseD | – |
| list_expensesD | – |
| summarizeD | – |
| monthly_reportD | – |
| top_spending_categoriesD | – |
| daily_averageD | – |
| budget_alertD | – |
| export_csvD | – |
| health_checkD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| categories |
TDQS
Scored across 12 tools
Most tools have distinct purposes targeting specific expense tracking operations like adding, listing, deleting, updating, and reporting. However, 'summarize' and 'monthly_report' could potentially overlap in function if not clearly differentiated by their descriptions, creating minor ambiguity.
All tool names follow a consistent snake_case pattern with clear verb_noun structures (e.g., add_expense, list_expenses, monthly_report). There are no deviations in naming conventions, making the set predictable and easy to parse.
With 12 tools, this server is well-scoped for an expense tracking domain. The count is appropriate, covering core operations without being excessive, and each tool appears to serve a specific, justified role in the workflow.
The tool set provides good coverage for expense management, including CRUD operations (add, read, update, delete), reporting (monthly_report, daily_average), and utilities (export_csv, health_check). A minor gap might be the absence of a tool for setting or managing budgets, which could limit full lifecycle coverage.