Maybe Finance MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your Maybe Finance API key | |
| API_BASE_URL | Yes | The base URL of your Maybe Finance API endpoint, e.g., https://your-maybe-instance.com/api/v1 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_accountsB | Get list of all accounts with their balances |
| get_account_balanceA | Get current balance for a specific account |
| get_transactionsC | Get transactions with various filters |
| search_transactionsC | Search transactions by text query |
| get_spending_breakdownC | Get spending breakdown by category for a time period |
| create_transactionC | Create a new transaction |
| update_transactionC | Update an existing transaction |
| categorize_transactionC | Quick categorization of a transaction |
| bulk_categorizeA | Categorize multiple transactions at once |
| get_cash_flowC | Get cash flow analysis for a period |
| get_rolling_cash_flowC | Get rolling cash flow analysis |
| forecast_cash_flowC | Forecast future cash flow based on historical data |
| get_categoriesB | Get all available categories |
| create_categoryB | Create a new category |
| import_csvB | Import transactions from CSV file |
| analyze_csvB | Analyze CSV structure before import |
| auto_categorize_allB | Auto-categorize all uncategorized transactions |
| get_categorization_rulesB | Get current categorization rules and patterns |
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 18 tools
Most tools target distinct resources and actions, but get_transactions and search_transactions overlap in purpose, potentially causing misselection. Other pairs like get_cash_flow and get_rolling_cash_flow are distinct enough in scope.
Tool names mostly follow a verb_noun snake_case pattern (e.g., get_accounts, create_transaction). Minor deviations like bulk_categorize and auto_categorize_all break the strict pattern but remain readable and predictable.
With 18 tools, the server is slightly above the ideal 3-15 range but still within a reasonable scope for a finance manager. Each tool addresses a specific need, though the count feels a bit heavy.
The server covers transaction management, categorization, cash flow, and CSV import well, but lacks account CRUD (create/update/delete) and category update/delete operations. These gaps are notable for a finance domain but not severe enough to break core workflows.