The Budgetsco MCP Server is a personal finance management tool that lets you manage transactions, categories, recurring transactions, budgets, and currency preferences.
Transactions
Create, edit, delete, and retrieve transactions with filters for date range, type, category, and payment mode
Supported payment modes: Cash, Cheque, Credit Card, Debit Card, Mobile Wallet, Netbanking, Sodexo, UPI
Categories
Retrieve all categories (predefined and custom) by type: income, expense, or investment
Create and delete custom categories
Recurring Transactions
Create, edit, and delete recurring transactions with daily, monthly, or yearly intervals
Retrieve recurring transactions with optional date range filters
Mark recurring transactions as done or skip them for the current period
Budgeting
Set budgets with per-category spending limits
Retrieve budget information for a specific month or date range, with optional category-level breakdown
Currency
Get and set your preferred currency from a wide range of international options (e.g., USD, EUR, INR, GBP, JPY)
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Budgetsco MCP Server show me my spending on groceries this month"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Server for Budgetsco, enabling personal finance management through transactions, budgeting, and financial tracking capabilities.
Related MCP server: Expense Tracker MCP
Node.js (version 22.x recommended)
Check your Node.js version with: node --version
A Budgetsco personal access token
Clone the repository
Create a .env file in the root directory with your Budgetsco access token:
BUDGETSCO_ACCESS_TOKEN='your_access_token_here'Install dependencies:
npm installThe server provides several tools for managing personal finances:
Create, edit, and delete transactions
View transaction history with flexible filters
Support for various payment modes (Cash, Credit Card, UPI, etc.)
Get predefined and custom categories
Create and manage custom categories
Categorize transactions for better financial tracking
Set up automated recurring transactions
Manage daily, monthly, or yearly recurring entries
Skip or mark recurring transactions as complete
Set and manage budgets for different categories
Track budget utilization
Get detailed budget breakdowns
Set and manage currency preferences
Support for multiple international currencies
Available commands:
npm run dev: Launch MCP Inspector against the server (tsx src/server.ts)
npm run start: Run the production server
npm run build: Build the project
npm run lint: Run linting checks
npm run format: Format code
npm run test: Run tests
BUDGETSCO_ACCESS_TOKEN (required): Your Budgetsco personal access token
To use this MCP server with clients like Claude, add the following configuration:
{
"mcpServers": {
"budgetsco": {
"command": "npx",
"args": ["@budgetsco/mcp"],
"env": {
"BUDGETSCO_ACCESS_TOKEN": "<YOUR_TOKEN>"
}
}
}
}This project is licensed under the MIT License. See the LICENSE file for details.
Built with the official MCP TypeScript SDK (@modelcontextprotocol/sdk). The server uses stdio transport; log diagnostics to stderr only so stdout stays reserved for JSON-RPC.
Create new custom categories for transactions.
Inputs: type (required), categories (required).
Create a recurring transaction
Inputs: type (required), amount (required), category (required), interval (required), +5 more.
Create new transaction.
Inputs: type (required), amount (required), category (required), paymentMode (required), +3 more.
Delete custom categories
Inputs: type (required), categories (required).
Delete a recurring transaction permanently
Inputs: transactionId (required).
Delete transaction permanently.
Inputs: transactionId (required).
Edit a recurring transaction
Inputs: type (required), amount (required), category (required), interval (required), +5 more.
Edit an existing transaction.
Inputs: type (required), amount (required), category (required), paymentMode (required), +3 more.
Retrieve budget for a specific period
Inputs: startMonth (required), endMonth, breakDownByCategory.
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.
Inputs: type (required).
Get the current currency preference
Inputs: no named parameters.
Retrieve all custom categories created by the user
Inputs: type (required).
Retrieve recurring transactions
Inputs: endDate, startDate.
Retrieve a list of transactions
Inputs: startDate (required), types, endDate, categories, +1 more.
Mark a recurring transaction as done for the current period
Inputs: transactionId (required).
Set budget for categories
Inputs: no named parameters.
Set currency preference
Inputs: currency.
Skip a recurring transaction for the current period
Inputs: transactionId (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Personal finance: accounts, transactions, categories, budgets, goals, debts and spending stats.
Personal finance assistant: track accounts, expenses, cash flow forecasts, and subscriptions.
Track expenses, budgets, balances, transfers, and multi-currency reports with OAuth-secured tools.
Personal finance for AI agents — onboard, import statements, categorize & budget over MCP.
