Budgetsco MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUDGETSCO_ACCESS_TOKEN | Yes | Your Budgetsco personal access token |
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 |
|---|---|
| getTransactionsC | Retrieve a list of transactions |
| createTransactionC | Create new transaction. |
| editTransactionC | Edit an existing transaction. |
| deleteTransactionB | Delete transaction permanently. |
| getCategoriesByTypeA | Retrieve all categories of a specific type. Always use this tool to get categories before creating a transaction. If no categories match, create a new category. |
| getCustomCategoriesB | Retrieve all custom categories created by the user |
| createCustomCategoriesB | Create new custom categories for transactions. |
| deleteCustomCategoriesC | Delete custom categories |
| getRecurringTransactionsB | Retrieve recurring transactions |
| createRecurringTransactionC | Create a recurring transaction |
| editRecurringTransactionD | Edit a recurring transaction |
| markRecurringTransactionDoneB | Mark a recurring transaction as done for the current period |
| skipRecurringTransactionB | Skip a recurring transaction for the current period |
| deleteRecurringTransactionA | Delete a recurring transaction permanently |
| getBudgetB | Retrieve budget for a specific period |
| setBudgetB | Set budget for categories |
| getCurrencyA | Get the current currency preference |
| setCurrencyC | Set currency preference |
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
Each tool targets a distinct resource-action combination: transactions, recurring transactions, budget, currency, and categories have separate create/read/update/delete operations. The only potential overlap between getCategoriesByType and getCustomCategories is resolved by their specific scopes (general vs. user-created). No two tools appear to serve the same purpose.
All tools follow a consistent verb_noun pattern (create, delete, get, edit, mark, skip, set) with clear resource nouns. However, there is minor inconsistency in plural/singular usage: getters like getTransactions and getRecurringTransactions use plural, while createTransaction and createRecurringTransaction use singular, and getCustomCategories uses plural while createCustomCategories also uses plural. This is a small deviation from a fully uniform convention.
With 18 tools, the server is slightly above the typical 3-15 range, but the breadth of domain resources (transactions, recurring transactions, categories, budget, currency) justifies the count. Each tool has a clear purpose, and no redundant tools are present, so the count feels reasonable for a budgeting application.
The tool surface covers full CRUD for transactions and recurring transactions, plus essential get/set operations for budget and currency. Categories support creation, deletion, and retrieval, but there is no edit operation for custom categories, which is a minor gap. Overall, the core workflows are covered with only a few missing lifecycle operations.