avie-moneylover-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PUBLIC_URL | No | Public HTTPS origin for cloud MCP (e.g., https://your-domain.com) | |
| MCP_AUTH_SECRET | No | Secret for MCP authentication | |
| MONEYLOVER_COOKIE | No | Browser cookie string (alternative to cf_clearance) | |
| MCP_OWNER_PASSWORD | No | Password for MCP owner authentication | |
| MONEYLOVER_TIMEOUT_MS | No | Timeout in milliseconds for HTTP requests | |
| MONEYLOVER_USER_AGENT | No | Exact browser User-Agent string | |
| MONEYLOVER_ACCESS_TOKEN | Yes | Your Money Lover access token (AuthJWT) | |
| MONEYLOVER_CF_CLEARANCE | No | Cloudflare cf_clearance cookie value (if required) | |
| MONEYLOVER_WRITE_DELAY_MS | No | Delay in milliseconds between writes | |
| MONEYLOVER_CATEGORY_LOOKBACK_DAYS | No | Number of days to look back for category mapping |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginA | Authenticate with Money Lover and return an access token. |
| get_user_infoC | Retrieve the authenticated Money Lover profile. |
| get_walletsB | List all wallets accessible to the authenticated user. |
| get_categoriesB | Retrieve categories for a specific wallet. |
| get_transactionsB | Fetch transactions for a wallet between two dates. |
| preview_transactionB | Resolve a category and check for an exact duplicate without writing anything. |
| add_transactionA | Create one transaction only after explicit confirmation. Validates category ownership and blocks exact duplicates by default. |
| diagnose_write_contextC | Read-only diagnostics for wallet ownership, browser write config, and category-v2 runtime mapping. |
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 8 tools
Each tool has a clear, distinct purpose: login, user info, wallets, categories, transactions (list, preview, add), and diagnostics. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern (e.g., get_wallets, add_transaction, diagnose_write_context). Although verbs vary, they match the action type appropriately, and the naming is uniform and predictable.
With 8 tools, the server is well-scoped for a personal finance app. It covers authentication, read operations, transaction creation, and diagnostics without bloat or redundancy.
The tool set covers authentication, reading of user/wallets/categories/transactions, and adding transactions. However, it lacks update and delete operations for any resource, which are notable gaps in a typical CRUD lifecycle. This could hinder agents from correcting mistakes or modifying data.