CashChat MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port the HTTP server will listen on. | 3000 |
| SERVER_URL | No | The publicly accessible URL of the server (e.g., http://localhost:3000). | |
| CASHCHAT_API_KEY | Yes | Your CashChat API key obtained from the settings page. | |
| OAUTH_CLIENT_SECRET | No | Optional client secret for additional OAuth security in production. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_transactionsC | Get transactions from CashChat with optional filters |
| add_transactionC | Add a new transaction to CashChat |
| update_transactionC | Update an existing transaction in CashChat |
| delete_transactionC | Delete a transaction from CashChat |
| get_summaryB | Get spending summary for a time period |
| get_categoriesB | Get list of transaction categories |
| get_settingsC | Get CashChat user settings |
| update_settingsC | Update CashChat user settings |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| server-info |
TDQS
Scored across 8 tools
Every tool has a clearly distinct purpose targeting specific resources and actions. For example, add_transaction, update_transaction, and delete_transaction handle different lifecycle stages of transactions, while get_categories, get_settings, and update_settings manage separate aspects of the system. There is no ambiguity or overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case. The verbs (add, delete, get, update) are applied logically to corresponding nouns (transaction, categories, settings, summary), creating a predictable and readable naming convention throughout the tool set.
With 8 tools, this server is well-scoped for a personal finance/transaction management domain. Each tool earns its place by covering essential operations like CRUD for transactions, settings management, and summary reporting, without being overly sparse or bloated.
The tool surface provides complete coverage for the apparent domain of transaction management. It includes full CRUD for transactions (add, get, update, delete), settings management (get and update), and auxiliary functions like categories and summaries, ensuring agents can handle typical workflows without dead ends.