Actual Budget
OCI · GHCR.IO/HENFRYDLS/ACTUAL-BUDGET-MCP · 2 COMPONENTS
Actual Budget, carefully: deletes preview first, and new transactions check for duplicates.
Available components
Last scanned (7 hours ago)
Scores higher than 68% of OCI servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5621 tokens (~119/item across 47 items; 44 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management72
- Stability check failed: the tool surface changed between 0.10.5 and 0.12.0: 0 tool removals, 1 breaking changes, 3 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety94
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 6 of 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "transfer_between_categories" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 46 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 69 to 72.
- 4 Nov 26 −5
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.11.1 → 0.12.0 functional
- 2 Nov 26 0
- Package version: 0.11.0 → 0.11.1 functional
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 95 to 99.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 89 to 92.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 82 to 85.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 75 to 79.
- 22 Oct 26 0
- Tool safety: pass → unverified ▼ security
- Stability: fail → unverified ▼ security
- Schema quality: 5001 → 5556 ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Package version: 0.10.9 → 0.11.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed oci/ghcr.io/henfrydls/actual-budget-mcp@0.12.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
balance_history ~82
Track an account's balance changes over time by showing the running balance at key transaction dates.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Account name or ID |
| end_date | string | – | End date (YYYY-MM-DD or natural language). Defaults to today. |
| start_date | string | – | Start date (YYYY-MM-DD or natural language). Defaults to 3 months ago. |
No output schema declared.
No examples provided.
budget_vs_actual ~65
Compare budgeted amounts versus actual spending for each category in a given month. Highlights over-budget and under-budget categories.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | Filter to a specific category group name |
| month | string | – | Month (YYYY-MM or natural language). Defaults to current month. |
No output schema declared.
No examples provided.
category_trends ~151
Show spending trends for a category across a window of months, ending in the month you name or this month. Identifies increasing/decreasing patterns.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category name or ID. If omitted, shows trends for top spending categories. |
| month | string | – | The month the window ends in (YYYY-MM or natural language). Defaults to this month. Use it to look at a past period: month "2026-06" with months 3 reads April, May and June. |
| months | number | – | How many months the window covers. Defaults to 6, which is a default and not a limit: ask for 24 or 36 if that is what you want. |
No output schema declared.
No examples provided.
create_account ~107
Create a new budget account (on-budget or off-budget). Returns the new account ID so transactions can target it right away.
| Name | Type | Req | Description |
|---|---|---|---|
| initialBalance | number | – | Opening balance in human amounts (e.g. 1500.50, not cents). Creates the "Starting Balance" transaction. |
| name | string | yes | Account name |
| offBudget | boolean | – | Whether the account is off-budget (tracked but outside the budget, e.g. a loan or investment). Defaults to false. |
No output schema declared.
No examples provided.
create_category ~47
Create a new budget category within a category group.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | yes | Category group name or ID to add this category to |
| name | string | yes | Name for the new category |
No output schema declared.
No examples provided.
create_category_group ~32
Create a new category group for organizing budget categories.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name for the new category group |
No output schema declared.
No examples provided.
create_payee ~28
Create a new payee.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name for the new payee |
No output schema declared.
No examples provided.
create_rule ~602
Create a transaction rule. When a transaction matches the condition, the action is applied automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| action_field | string | yes | Field to set: category, payee, payee_name, notes, account, amount, date, imported_payee, cleared, reconciled. Not category_group, which does nothing, and not transfer, parent or saved, which make eve… |
| action_value | string|boolean|number | yes | Value to set (category name/ID, payee name/ID, account name/ID, note text, an amount as you would say it, or true or false for cleared and reconciled). A payee, category or account must already exist… |
| condition_field | string | yes | Field to match: payee, payee_name, category, category_group, account, amount, notes, date, imported_payee, cleared, reconciled |
| condition_op | string | yes | Operator: is, isNot, oneOf, notOneOf, contains, doesNotContain, matches, gt, lt, gte, lte. oneOf and notOneOf take a list. contains, doesNotContain and matches are refused on payee, category, categor… |
| condition_value | – | yes | Value to match against. For payee, category, category_group and account, a whole name or an ID. For amount, the figure as you would say it (45.50, or -45.50 for money going out), not in cents. Spendi… |
| stage | string|null | – | When to apply: null (default), pre, or post |
No output schema declared.
No examples provided.
create_split_transaction ~183
Add a split transaction: one bank-facing total spread across multiple categories. The split amounts must sum to the total.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Account name or ID |
| allow_duplicate | boolean | – | Create it even though a transaction with the same account, date and total already exists. The total is what a duplicate repeats; how it is divided is internal. |
| amount | number | yes | Total amount (negative for expenses, positive for income). Must equal the sum of the splits. |
| cleared | boolean | – | Whether the transaction is cleared |
| date | string | – | Transaction date (YYYY-MM-DD or "today", "yesterday"). Defaults to today. |
| notes | string | – | Notes for the parent transaction |
| payee | string | – | Payee name |
| splits | array | yes | Two or more splits whose amounts sum to the total. |
No output schema declared.
No examples provided.
create_transaction ~320
Add a new transaction to an account. Use negative amounts for expenses, positive for income. If a transaction with the same account, date and amount already exists, this creates nothing and returns the existing one instead; pass allow_duplicate to go ahead anyway.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Account name or ID |
| allow_duplicate | boolean | – | Create it even though a transaction with the same account, date and amount already exists. Without this, such a call returns the existing one and creates nothing. |
| amount | number | yes | Amount (negative for expenses, positive for income). Use human amounts like -150.50, not cents. |
| category | string | – | Category name or ID. Giving one stops a payee that names an account from becoming a transfer, but only when both accounts are on budget. An empty string counts as no category. |
| cleared | boolean | – | Whether the transaction is cleared |
| date | string | – | Transaction date (YYYY-MM-DD or "today", "yesterday"). Defaults to today. |
| notes | string | – | Transaction notes |
| payee | string | – | Payee name, or the name of one of your accounts to make a transfer. Naming an account moves money between accounts and creates the matching row there. Giving a category turns it into an ordinary purc… |
No output schema declared.
No examples provided.
create_transactions ~179
Create several transactions in one call. This is the way to record more than one: the rows are validated first and written together, so nothing is created unless every row is usable. Calling create_transaction many times in parallel is what this replaces. A row whose payee names one of your accounts becomes a transfer, the same way create_transaction treats it, so a month of records can be sent as one list.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_duplicate | boolean | – | Create the rows even though some repeat each other or match transactions already in the budget. Without this, such a batch is reported and nothing is written. The reply says which rows the checks fou… |
| transactions | array | yes | The transactions to create. All of them are written, or none. |
No output schema declared.
No examples provided.
create_transfer ~144
Create a transfer between two accounts.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_duplicate | boolean | – | Create it even though a transfer between the same two accounts, on the same date, for the same amount already exists. Two identical transfers in one day are ordinary: a cash withdrawal split across t… |
| amount | number | yes | Transfer amount (positive number, e.g., 5000.00) |
| date | string | – | Date (YYYY-MM-DD or natural language). Defaults to today. |
| from_account | string | yes | Source account name or ID |
| notes | string | – | Transfer notes |
| to_account | string | yes | Destination account name or ID |
No output schema declared.
No examples provided.
delete_account ~119
Delete an account and its entire transaction history. Destructive and irreversible: the first call only previews what would be lost, and deleting requires both confirm: true and confirm_name set to the account's exact name. Prefer closing an account when you just want to retire it.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Account name or ID to delete |
| confirm | boolean | – | Must be true to delete. Without it, the tool only previews. |
| confirm_name | string | – | The account's exact name, echoed back as a safeguard against deleting the wrong account. |
No output schema declared.
No examples provided.
delete_category ~132
Delete a budget category. Destructive and irreversible: the first call only previews, and deleting requires confirm: true plus confirm_name set to the category's exact name. Deleting a category also destroys its budget and rollover history; pass transfer_to to keep its transactions categorised.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Category name or ID to delete |
| confirm | boolean | – | Must be true to delete. Without it, the tool only previews. |
| confirm_name | string | – | The category's exact name, echoed back as a safeguard. |
| transfer_to | string | – | Category name or ID to transfer existing transactions to |
No output schema declared.
No examples provided.
delete_category_group ~150
Delete a category group and every category in it. Destructive and irreversible: the first call only previews, and deleting requires confirm: true plus confirm_name set to the group's exact name. A group with categories in it also needs transfer_to, the category their transactions move to; an empty group does not.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true to delete. Without it, the tool only previews. |
| confirm_name | string | – | The group's exact name, echoed back as a safeguard. |
| group | string | yes | Category group name or ID to delete |
| transfer_to | string | – | Category name or ID to transfer the transactions of the deleted categories to. Required unless the group is empty. |
No output schema declared.
No examples provided.
delete_payee ~98
Delete a payee. Destructive and irreversible: the first call only previews, and deleting requires confirm: true plus confirm_name set to the payee's exact name.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true to delete. Without it, the tool only previews. |
| confirm_name | string | – | The payee's exact name, echoed back as a safeguard. |
| payee | string | yes | Payee name or ID to delete |
No output schema declared.
No examples provided.
delete_rule ~68
Delete a transaction rule by its ID. Destructive and irreversible: the first call only previews the rule, and deleting requires confirm: true.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true to delete. Without it, the tool only previews. |
| rule_id | string | yes | Rule ID to delete |
No output schema declared.
No examples provided.
delete_transaction ~69
Delete a transaction by its ID. Destructive and irreversible: the first call only previews what would be lost, and deleting requires confirm: true.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Must be true to delete. Without it, the tool only previews. |
| transaction_id | string | yes | Transaction ID to delete |
No output schema declared.
No examples provided.
get_budget_month ~79
Get the budget for a specific month showing all category groups, their categories with budgeted amounts, actual spending, and remaining balance. Also shows the to-be-budgeted amount.
| Name | Type | Req | Description |
|---|---|---|---|
| month | string | – | Month in YYYY-MM format, or natural language like "this month", "last month", "January 2025". Defaults to current month. |
No output schema declared.
No examples provided.
get_budget_summary ~58
Executive summary of the budget showing totals by category group, total income, total expenses, savings rate, and to-be-budgeted for a given month.
| Name | Type | Req | Description |
|---|---|---|---|
| month | string | – | Month (YYYY-MM or natural language). Defaults to current month. |
No output schema declared.
No examples provided.
get_categories ~53
List all category groups with their categories and IDs. Useful for seeing the full budget structure.
| Name | Type | Req | Description |
|---|---|---|---|
| include_hidden | boolean | – | List hidden categories too, and the ones whose group is hidden, each marked. Off by default. |
No output schema declared.
No examples provided.
get_category_balance ~138
Get the balance and spending history for a specific category across a window of months, ending in the month you name or this month.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Category name or ID |
| month | string | – | The month the window ends in (YYYY-MM or natural language). Defaults to this month. Use it to look at a past period: month "2026-06" with months 3 reads April, May and June. |
| months | number | – | How many months the window covers. Defaults to 3, which is a default and not a limit: ask for 24 or 36 if that is what you want. |
No output schema declared.
No examples provided.
get_payees ~27
List all payees in the budget. Useful for seeing available payees and their IDs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_rules ~159
List transaction rules with their conditions and actions. Returns the first 100 rules; pass offset for the next page, flagged_only for just the ones with a warning, or field to see only the rules that mention one field.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | – | Only the rules that mention this field in a condition or an action, such as payee, amount or category. |
| flagged_only | boolean | – | Only the rules carrying a warning, wherever they are in the list. These are the ones worth acting on. |
| limit | integer | – | How many rules to list. 100 by default, which is about 16 KB of text. |
| offset | integer | – | How many rules to skip, for reading the list a page at a time. |
No output schema declared.
No examples provided.
get_schedules ~45
List the budget's schedules: what is due next, how much, from which account, and whether the last one posted. Read-only; creating and changing schedules is not here.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_transactions ~385
List transactions with optional filters. Returns date, payee, category, amount, notes, account, cleared status, and — for a part of a split — the note on the split it belongs to.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Account name or ID to filter by |
| category | string | – | Category to filter by: a name, matched on any part of it, or a full category ID. For transactions with no category at all, use uncategorized instead. |
| end_date | string | – | End date (YYYY-MM-DD or natural language). Defaults to today, or to every date when uncategorized or notes_contains is set. |
| limit | number | – | Maximum number of transactions to return (default 50) |
| max_amount | number | – | Maximum amount in human format |
| min_amount | number | – | Minimum amount in human format (e.g., -500 for expenses of at least 500) |
| notes_contains | string | – | Only transactions whose notes contain this text, case-insensitive. Also matches the note on the split a transaction belongs to, shown in the "Split of" column. Searches every date unless you give a r… |
| payee | string | – | Payee name to filter by (partial match) |
| start_date | string | – | Start date (YYYY-MM-DD or natural language like "start of month", "30 days ago"). Defaults to the start of the current month, or to every date when uncategorized or notes_contains is set. |
| uncategorized | boolean | – | Only transactions with no category. Left out: split parents (their categories live on their parts), transfers between accounts on the same side of the budget (Actual clears those), and off-budget acc… |
No output schema declared.
No examples provided.
hold_for_next_month ~141
Hold some of a month's unassigned money so it carries into the next month, instead of assigning it now. Adds to whatever is already held; pass 0 to release it all. To give money to a category, or to take it back, use transfer_between_categories; this one assigns nothing, it only keeps what is left over from being assigned this month.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | How much to hold, added to what is already held (human-readable, e.g. 150.00). Pass 0 to release the whole hold. |
| month | string | – | Month (YYYY-MM or natural language). Defaults to the current month. |
No output schema declared.
No examples provided.
list_accounts ~27
List all budget accounts with their current balances, type (on-budget/off-budget), and status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
monthly_summary ~51
Monthly financial summary showing income, expenses, savings, and savings rate across multiple months. Great for seeing trends in your overall financial health.
| Name | Type | Req | Description |
|---|---|---|---|
| months | number | – | Number of months to show (default 3) |
No output schema declared.
No examples provided.
recategorize_transaction ~40
Change the category of an existing transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | New category name or ID |
| transaction_id | string | yes | Transaction ID |
No output schema declared.
No examples provided.
reconcile_account ~186
Compare an account against the balance a bank reports, and list what might explain the difference. Reads only; books nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Account name or ID |
| as_of | string | – | Date the bank figure is from (YYYY-MM-DD or "today"). Defaults to today. Transactions after this date are not counted in the balance. |
| balance_counts | string | – | Which transactions the balance counts. "all" (default) counts uncleared rows too, which is right when uncleared means nobody ticked it off rather than the bank has not posted it. "cleared_only" count… |
| expected_balance | number | yes | Balance the bank reports for this account (human amount, e.g., 12345.67) |
| lookback_days | number | – | How far back to look for candidates, in days. Defaults to 90. |
No output schema declared.
No examples provided.
reconcile_currency_residual ~371
Book an adjustment transaction to bring a multi-currency account to the balance the bank reports, clearing accumulated FX-rate residual. It compares against every transaction up to today, and the reply says how much of that figure is not marked cleared and what the adjustment would have been against the cleared rows alone, since a statement generally shows only what has posted. The date must be today or earlier. If a transaction with the same account, date and amount already exists this books nothing and reports it instead; run it again to recompute, or pass allow_duplicate if the match is unrelated. If the account holds transactions dated after today, it reports those and books nothing until future_rows says whether the balance you gave already counts them.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Account name or ID to reconcile |
| allow_duplicate | boolean | – | Book the adjustment even though a transaction with the same account, date and amount already exists. Without this, such a call reports the existing one and books nothing. |
| category | string | yes | Category to book the adjustment under (name or ID) |
| date | string | – | Date for the adjustment (YYYY-MM-DD or "today"). Defaults to today. |
| future_rows | string | – | What the balance you gave does with transactions dated after today. "exclude" if the bank has not posted them, "include" if it has, which is usual for a card purchase the bank dates a day or two ahea… |
| notes | string | – | Note for the adjustment. Defaults to "FX residual adjustment". |
| payee | string | – | Optional payee for the adjustment |
| target_balance | number | – | Balance the bank reports for this account (human amount). Defaults to 0. |
No output schema declared.
No examples provided.
repair_sync ~48
Repair the budget's sync state when operations fail with an out-of-sync error. Rebuilds sync bookkeeping without modifying budget data. Use this when other tools report that the budget is out of sync.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_bank_sync ~58
Sync bank transactions from linked accounts (GoCardless/SimpleFIN). Syncs a specific account or all linked accounts if none specified.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Account name or ID to sync. If omitted, syncs all linked accounts. |
No output schema declared.
No examples provided.
set_category_carryover ~131
Turn a category's carryover on or off from a month onwards, so overspending rolls into that category next month instead of coming off the money to assign. Actual writes the flag into every month from the one given to the last the budget has, not only that one.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Category name or ID |
| enabled | boolean | yes | true to carry overspending forward in this category, false to stop |
| month | string | – | Month this starts from, and every month after it in the budget is set too (YYYY-MM or natural language). Defaults to this month. |
No output schema declared.
No examples provided.
spending_by_category ~107
Break down spending by category for a date range. Shows each category's total spending and percentage of total.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | End date (YYYY-MM-DD or natural language). Defaults to today. |
| include_income | boolean | – | Include income categories (default: false) |
| limit | number | – | Maximum number of categories to show (default 20) |
| start_date | string | – | Start date (YYYY-MM-DD or natural language). Defaults to start of current month. |
No output schema declared.
No examples provided.
spending_projection ~54
Project end-of-month spending for each category based on the current daily spending rate. Warns about categories likely to exceed budget.
| Name | Type | Req | Description |
|---|---|---|---|
| month | string | – | Month to project (YYYY-MM or natural language). Defaults to current month. |
No output schema declared.
No examples provided.
transfer_between_categories ~149
Move budgeted money between categories, or between a category and the money that is not budgeted yet, for a month. Creates no transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount to move (human-readable, e.g., 125.50). Must be positive. |
| from | string | yes | Category to take the money from (name or ID), or "To Budget" for money that is not budgeted yet |
| month | string | – | Month (YYYY-MM or natural language). Defaults to the current month. |
| to | string | yes | Category to give the money to (name or ID), or "To Budget" to return it to the money that is not budgeted yet |
No output schema declared.
No examples provided.
update_account ~44
Rename an account. Transactions, balance and budget status are untouched.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Account name or ID to rename |
| name | string | yes | The new name |
No output schema declared.
No examples provided.
update_budget_amount ~167
Set the budgeted amount for a category in a specific month, or add to it with mode: "delta".
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Human-readable amount, e.g., 5000.00. With mode "absolute" this is the new budgeted figure; with mode "delta" it is added to what is already there, and may be negative. |
| category | string | yes | Category name or ID |
| mode | string | – | How to apply the amount. "absolute" (default) sets the budgeted figure. "delta" adds to it, which is what an ordinary adjustment is: putting more into an envelope rather than working out what the tot… |
| month | string | – | Month (YYYY-MM or natural language). Defaults to current month. |
No output schema declared.
No examples provided.
update_category ~57
Rename or hide/unhide a budget category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Category name or ID |
| hidden | boolean | – | Set to true to hide, false to unhide |
| name | string | – | New name for the category |
No output schema declared.
No examples provided.
update_category_group ~59
Rename or hide/unhide a category group.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | yes | Category group name or ID |
| hidden | boolean | – | Set to true to hide, false to unhide |
| name | string | – | New name for the group |
No output schema declared.
No examples provided.
update_payee ~40
Rename a payee.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | New name for the payee |
| payee | string | yes | Payee name or ID |
No output schema declared.
No examples provided.
update_transaction ~122
Update fields of an existing transaction. Only the fields you provide will be changed.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | New amount (negative for expenses, positive for income). Human amounts, not cents. |
| category | string | – | New category name or ID |
| cleared | boolean | – | Whether the transaction is cleared |
| date | string | – | New date (YYYY-MM-DD or "today", "yesterday") |
| notes | string | – | New notes |
| payee | string | – | New payee name |
| transaction_id | string | yes | Transaction ID |
No output schema declared.
No examples provided.
How do I install the Actual Budget MCP server?
Actual Budget runs locally as a container image, launched with docker run --rm -i -e ACTUAL_SERVER_URL -e ACTUAL_PASSWORD -e ACTUAL_SESSION_TOKEN -e ACTUAL_BUDGET_ID -e ACTUAL_BUDGET_IDS -e ACTUAL_ENCRYPTION_PASSWORDS -e ACTUAL_BUDGET_WORKERS -e ACTUAL_WORKER_IDLE_MINUTES -e ACTUAL_WORKER_READY_SECONDS -e ACTUAL_READ_ONLY -e ACTUAL_TOOLSET -e ACTUAL_HTTP_TIMEOUT_MS -e ACTUAL_HTTP_PORT -e ACTUAL_HTTP_TOKEN -e ACTUAL_HTTP_WRITE_TOKEN -e ACTUAL_HTTP_HOST -e ACTUAL_HTTP_ALLOW_REMOTE -e ACTUAL_HTTP_ALLOWED_HOSTS ghcr.io/henfrydls/actual-budget-mcp:0.12.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/henfrydls/actual-budget-mcp
claude mcp add henfrydls-actual-budget-mcp -- docker run --rm -i -e ACTUAL_SERVER_URL -e ACTUAL_PASSWORD -e ACTUAL_SESSION_TOKEN -e ACTUAL_BUDGET_ID -e ACTUAL_BUDGET_IDS -e ACTUAL_ENCRYPTION_PASSWORDS -e ACTUAL_BUDGET_WORKERS -e ACTUAL_WORKER_IDLE_MINUTES -e ACTUAL_WORKER_READY_SECONDS -e ACTUAL_READ_ONLY -e ACTUAL_TOOLSET -e ACTUAL_HTTP_TIMEOUT_MS -e ACTUAL_HTTP_PORT -e ACTUAL_HTTP_TOKEN -e ACTUAL_HTTP_WRITE_TOKEN -e ACTUAL_HTTP_HOST -e ACTUAL_HTTP_ALLOW_REMOTE -e ACTUAL_HTTP_ALLOWED_HOSTS ghcr.io/henfrydls/actual-budget-mcp:0.12.0
This image reads ACTUAL_SERVER_URL, ACTUAL_PASSWORD, ACTUAL_SESSION_TOKEN, ACTUAL_BUDGET_ID, ACTUAL_BUDGET_IDS, ACTUAL_ENCRYPTION_PASSWORDS, ACTUAL_BUDGET_WORKERS, ACTUAL_WORKER_IDLE_MINUTES, ACTUAL_WORKER_READY_SECONDS, ACTUAL_READ_ONLY, ACTUAL_TOOLSET, ACTUAL_HTTP_TIMEOUT_MS, ACTUAL_HTTP_PORT, ACTUAL_HTTP_TOKEN, ACTUAL_HTTP_WRITE_TOKEN, ACTUAL_HTTP_HOST, ACTUAL_HTTP_ALLOW_REMOTE and ACTUAL_HTTP_ALLOWED_HOSTS. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the Actual Budget MCP server?
Actual Budget is an MCP server listed in the public MCP registry as io.github.henfrydls/actual-budget-mcp. Actual Budget, carefully: deletes preview first, and new transactions check for duplicates. This page covers its container image (ghcr.io/henfrydls/actual-budget-mcp).
Is the Actual Budget MCP server safe to use?
Actual Budget scores 47 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Actual Budget MCP server expose?
Actual Budget exposes 44 tools: list_accounts, get_budget_month, get_transactions, get_category_balance, get_budget_summary, and 39 more. Their descriptions and schemas cost roughly 5,372 tokens of context every time the server is loaded.
Is the Actual Budget MCP server still maintained?
Actual Budget is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Actual Budget MCP server under?
Actual Budget declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.