Expense Tracker MCP
by naveen6768
README.md
# expense_tracker_mcp
This project uses `FastMCP 3.2.0`.
## Why your commands failed
- `fastmcp: command not found`
The CLI is only installed inside this project's virtual environment, so it is not available from your base shell unless you activate `.venv` or run it through `uv`.
- `uv run fastmcp dev main.py`
In FastMCP `3.x`, `dev` is a command group. You must use a subcommand such as `inspector`.
- `uv run fastmcp dev inspector`
That form needs a server spec or a `fastmcp.json`. This repo now includes `fastmcp.json`, so auto-detection works.
## Working commands
Run the server directly:
```bash
uv run fastmcp run
```
Inspect the server:
```bash
uv run fastmcp inspect
```
Open MCP Inspector in dev mode:
```bash
uv run fastmcp dev inspector
```
If the Inspector UI shows `Error Connecting to MCP Inspector Proxy - Check Console logs`,
open the exact URL printed in the terminal. FastMCP 3.x starts the proxy with a per-run
session token, and the Inspector page must include that token or the proxy config request
will be rejected.
For local-only debugging, you can disable proxy auth:
```bash
DANGEROUSLY_OMIT_AUTH=true uv run fastmcp dev inspector
```
You can still pass the file explicitly if you want:
```bash
uv run fastmcp run main.py
uv run fastmcp inspect main.py
uv run fastmcp dev inspector main.py
```
# MCP
TDQS
B3.4/5.0
Scored across 4 tools
Disambiguation5/5
Each tool has a distinct purpose: add, delete, list, and summarize expenses. No overlap exists.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern (add_expense, delete_expense, get_expense_summary, list_expenses).
Tool Count5/5
With 4 tools, the server covers the core operations of an expense tracker without being too sparse or bloated.
Completeness4/5
CRUD operations are mostly covered (create, read, delete, list), but an update/edit expense tool is missing, which is a minor gap.
Maintenance
ActivityInactive
ResponsivenessNo issues