Skip to main content
Glama
xinrong-meng

My Finance MCP Server

by xinrong-meng

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MY_FINANCE_MCP_DIRNoThe 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

NameDescription
store_transactionsA
Parse and store transaction data from uploaded financial documents.

If you receive unstructured financial data (statements, receipts, CSV files, etc.),
extract transactions into the format: [{"date": "YYYY-MM-DD", "amount": number, "description": "string", "category": "string"}]

Args:
    transactions: List of transaction dictionaries, each containing:
        - date: Transaction date (string, format: YYYY-MM-DD)
        - amount: Transaction amount (number, can be negative for expenses)
        - description: Transaction description (string)
        - category: Transaction category (string, optional, e.g. "Food", "Transport", "Bills")

Returns:
    Success message with count of stored transactions
query_financial_historyC
Search through all stored financial data using semantic search.

Args:
    query: Search query string to find relevant transactions

Returns:
    Formatted summary of matching transactions with totals
list_transactionsA
List stored transactions from the JSON ledger with optional pagination and filtering.

Args:
    limit: Maximum number of transactions to return (default 20)
    offset: Number of transactions to skip from the beginning (default 0)
    category: Optional category filter (case-insensitive)

Returns:
    Dictionary containing total count, pagination info, and transactions with index field
delete_transactionsA
Delete transactions from both the JSON ledger and ChromaDB.

Args:
    indices: List of transaction indices (from list_transactions) to delete
    delete_all: Set to true to delete all transactions
    confirm: Must be true to actually perform deletion (safety guard)

Returns:
    Status message describing the deletion result

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 4 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count3/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues