My Finance MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MY_FINANCE_MCP_DIR | No | The directory where financial data will be stored. If not set, defaults to ~/.my_finance_mcp/ |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| store_transactionsA | |
| query_financial_historyC | |
| list_transactionsA | |
| delete_transactionsA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct and non-overlapping purpose: list_transactions retrieves data, store_transactions adds new data, delete_transactions removes data, and query_financial_history performs semantic search. The descriptions clearly differentiate their functions, with no ambiguity in selection.
Three tools follow a consistent verb_noun pattern (list_transactions, store_transactions, delete_transactions), but query_financial_history deviates slightly with a different verb style. The naming is still readable and mostly predictable, with only minor inconsistency.
With only 4 tools, the set feels thin for a finance management server, lacking operations like update_transactions, get_transaction_by_id, or category management. While the tools cover basic CRUD and search, the scope suggests more functionality is needed for comprehensive financial handling.
There are significant gaps in the tool surface for a finance domain. The server supports create (store_transactions), read (list_transactions, query_financial_history), and delete (delete_transactions), but lacks update operations (e.g., modify_transaction) and essential features like budget tracking, reporting, or category CRUD, which will limit agent effectiveness.