Skip to main content
Glama
deenesjakoruzh
yash-201

Expense Tracker MCP Server

by yash-201
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Expense Tracker MCP Server

一个使用 FastMCP（v3.x）和 Python 构建的模型上下文协议（MCP）服务器，旨在为 MCP 兼容客户端（如 Claude Desktop 和 MCP Inspector）提供用于支出跟踪的工具和资源。

📋 前提条件

  • Python：3.10+（已在 Python 3.14 上测试）

  • uv：快速的 Python 包安装与解析器（astral.sh/uv）

  • Node.js：v22.x 或 v24.x（LTS）— MCP Inspector UI 所需

  • Claude Desktop （可选）：用于在 Claude Desktop 中直接测试工具

Related MCP server: Demo MCP Server

🚀 设置与安装

1. 初始化项目与环境

# Initialize uv project (if starting fresh)
uv init .

# Install FastMCP
uv add fastmcp

2. 为 MCP Inspector UI 准备 Node.js

MCP Inspector（@modelcontextprotocol/inspector）需要 Node.js v22.19.0+ 或 v24+。如果使用 nvm-windows：

nvm install lts
nvm use 24

全局安装 inspector，或者允许 npx 自动获取它：

npm install -g @modelcontextprotocol/inspector

🛠️ 运行与开发

选项 A：交互式 Web UI（MCP Inspector）

要启动带 热重载 的 MCP Inspector Web UI：

uv run fastmcp dev inspector main.py

  • 请保持此终端窗口打开。

  • 控制台会输出一个包含身份验证令牌的本地 URL：

    MCP Inspector Web is up and running at:
   http://127.0.0.1:6274?MCP_INSPECTOR_API_TOKEN=<token>

  • 在浏览器中打开该链接，即可测试工具、查看 schemas，并实时查看请求/响应日志。

选项 B：直接运行服务器（STDIO）

要在标准 I/O 模式下运行 MCP 服务器：

uv run fastmcp run main.py

（或 uv run python main.py）

🤖 连接到 Claude Desktop

1. 配置文件位置

在 Windows 上，Claude Desktop 的配置存储在以下位置：

%APPDATA%\Claude\claude_desktop_config.json

（完整路径：C:\Users\<你的用户名>\AppData\Roaming\Claude\claude_desktop_config.json）

2. 配置设置

在 mcpServers 下添加 expense-server 定义。

注意：在 Windows 上，Claude Desktop 等 GUI 应用通常不会继承 shell 的 PATH。请始终指定 uv.exe 的绝对路径。

{
  "mcpServers": {
    "expense-server": {
      "command": "C:\\Users\\hp\\AppData\\Local\\Python\\pythoncore-3.14-64\\Scripts\\uv.exe",
      "args": [
        "run",
        "--directory",
        "g:\\Projects\\expense-tracker-mcp-server",
        "fastmcp",
        "run",
        "main.py"
      ]
    }
  }
}

3. 重启 Claude Desktop

  1. 完全关闭 Claude Desktop（确保从时钟附近 Windows 系统托盘退出）。

  2. 重新打开 Claude Desktop。

  3. 查看 Settings > Developer，确认 expense-server 已连接。

🧰 可用工具（当前 main.py）

工具

参数

描述

roll_dice

n_dice: int = 1

掷 n_dice 个六面骰子并返回结果列表。

add_numbers

a: float, b: float

将两个数字相加并返回总和。

🔧 故障排查

1. Unknown command "main.py". Available commands: inspector, apps.

在 FastMCP 3.x 中，fastmcp dev 是一个命令组。请使用 fastmcp dev inspector main.py，而不是fastmcp dev main.py。

2. node:util does not provide an export named 'styleText'

Node.js 版本低于 v20.10 或未能正确升级。请通过 nvm install lts && nvm use 24 更新到 Node v22+ 或 v24+。

3. Cannot find native binding (npm optional dependencies bug)

切换到其他 Node 版本时 npx 缓存损坏。请运行：

npm cache clean --force
Remove-Item -Recurse -Force "$env:LOCALAPPDATA\npm-cache\_npx" -ErrorAction SilentlyContinue
npm install -g @modelcontextprotocol/inspector

Available Tools

2 tools
add_numbersA

Add two numbers together.

ParametersJSON Schema
NameRequiredDescriptionDefault
aYes
bYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It states the operation but does not explicitly mention that it is pure, has no side effects, or what the return value is. While obvious for addition, it falls short of full transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, direct sentence with zero filler. It is front-loaded and every word earns its place, exemplifying appropriate conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a trivial addition tool with a clear input schema and an output schema (as indicated by the signal), the description is largely sufficient. It lacks explicit mention of edge cases or preconditions, but none are expected for this operation, making it nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%—the description does not mention parameters by name or add any nuance. The schema already declares a and b as required numbers, but the description adds no value beyond that, failing to compensate for the low coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Add two numbers together' uses a specific verb and resource, clearly stating exactly what the tool does. It is distinct from siblings like roll_dice and add_expense, so agents can easily differentiate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus alternatives, nor any exclusions. There is no context about when addition is appropriate or not, leaving the agent to infer usage from the name and schema alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

roll_diceA

Roll n_dice 6-sided dice and return the results.

ParametersJSON Schema
NameRequiredDescriptionDefault
n_diceNo

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. It correctly implies a random stochastic process and states the output ('return the results'), but does not explicitly mention randomness, the range of outcomes (1–6 per die), or that subsequent calls produce independent results. This is adequate for a simple tool but lacks any deeper context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, front-loaded with the core action, and contains no filler words. Every term contributes to understanding the tool's behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the low complexity (one parameter, simple output) and the presence of an output schema, the description is complete enough. It explains the parameter's role and the action's purpose. It could mention the non-deterministic nature more explicitly, but that is implicit for a dice-rolling tool, and the output schema likely covers return formatting.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero description coverage for the parameter n_dice, so the description must compensate. It does so by framing n_dice as the number of dice to roll, adding semantic meaning to an otherwise bare integer field. However, it does not specify constraints like minimum value or positivity, which would have improved clarity further.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear, specific action: 'Roll n_dice 6-sided dice and return the results.' The verb 'Roll' and resource 'dice' are unambiguous, and the tool is easily distinguished from siblings like add_numbers or list_expenses, which handle arithmetic or expense management.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to use this tool versus alternatives, nor any exclusions or prerequisites. Sibling tools are unrelated, but the description provides no context for selection, leaving the agent to infer its suitability from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv0.1.0
    • First observedadd_numbers
    • First observedroll_dice
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

B3.4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have completely disjoint purposes—one rolls dice and the other adds numbers. There is no ambiguity between them and no chance of an agent misselecting one for the other.

Naming Consistency5/5

Both tool names follow the same verb_noun snake_case pattern: roll_dice and add_numbers. The naming is predictable and straightforward.

Tool Count1/5

A server named 'Expense Tracker' offers only two tools that perform unrelated operations (dice rolling and arithmetic). This is a severe mismatch between scope and purpose, making the count completely inappropriate.

Completeness1/5

The tools do not cover any expense tracking functionality whatsoever—no add expense, list expenses, delete expense, or summaries. The surface is entirely incomplete for the stated domain.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Demo MCP Server

    SannketNikam
    F
    license
    B
    quality
    D
    maintenance
    A simple demonstration MCP server that provides basic utility tools including dice rolling and number addition functionality. This server serves as a tutorial example for setting up both local and remote MCP servers using FastMCP.
    3
    -

  • dice-mcp

    yus04
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables rolling dice with customizable sides and counts, returning results and totals via MCP Streamable HTTP transport.
    -