Skip to main content
Glama
MuazamAbbas

expense-tracker-remote-mcp-server

by MuazamAbbas

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DB_PATHNoPath to SQLite databaseexpenses.db
DEFAULT_BUDGETNoDefault monthly budget1000.0

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

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
add_expenseC

Add a new expense to the database.

list_expensesB

List expenses with optional filters for category and date range.

get_summaryC

Get spending summary grouped by category.

delete_expenseA

Delete an expense by its ID.

update_expenseC

Update an existing expense's details.

get_budget_statusB

Check budget vs actual spending for current month.

get_monthly_trendB

Get monthly spending trends over time.

search_expensesA

Search expenses by description keyword.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
get_current_month_expensesGet current month's expenses as a resource.
get_expense_summaryGet overall expense summary as a resource.

TDQS

B3.4/5.0

Scored across 8 tools

Disambiguation4/5

Each tool targets a distinct operation (add, list, update, delete, summary, budget, trend, search). list_expenses and search_expenses both retrieve expenses, but list uses filters while search uses keyword, and descriptions clarify the difference.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_expense, list_expenses, get_summary). This makes the set predictable and easy to navigate.

Tool Count5/5

With 8 tools, the server is well-scoped for expense management. Each tool serves a clear purpose without redundancy or bloat, covering core CRUD plus useful analytics.

Completeness4/5

The surface covers add, list, update, delete, summary, budget check, trend, and search—solid coverage for expense tracking. Minor gaps like a dedicated get-by-ID or budget-setting tool, but these are not critical and can be worked around.

Maintenance

ActivityInactive
ResponsivenessNo issues