
Actual Budget MCP Server
io.github.agigante80Published by GitHub account agigante80v0.27.1Updated Nov 4, 2026
Manage Actual Budget accounts, transactions, budgets, rules and reports from an AI assistant.
Overview
MCP server that lets an AI assistant read and manage a self-hosted Actual Budget: accounts, transactions, budgets, rules, schedules and reports.
- What you can do
- Read and look up accounts, payees, categories, tags and server context
- Create, update, delete, import and transfer transactions
- Summarize spending, aggregates and balances
- Set budget month amounts, move money between categories and batch-update budgets
- Create and manage rules, payee rules and scheduled transactions
- Run read-only SELECT queries and handle budget switching, import/export and bank sync
- When to use it
- Use it when you keep your finances in a self-hosted Actual Budget server and want an assistant to answer spending questions or make budget and transaction changes directly. It suits both a single local client over stdio and a shared chat UI over HTTP with several users.
- Requirements
- A running Actual Budget server (25.0.0 or later) and its URL, server login password and budget Sync ID. Node.js 22 or later for the npx/stdio route, or Docker for the HTTP route. For HTTP, a Bearer token in MCP_SSE_AUTHORIZATION that clients send in the Authorization header; an optional encryption password for end-to-end encrypted budgets.
Installation
In SourceWeft
- Open Actual Budget MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Actual MCP Server
[GitHub Actions CI] [npm version] [Docker Pulls] [License: MIT] [Node.js Version] [TypeScript]
A Model Context Protocol server that lets an AI assistant (Claude, LibreChat, LobeChat, Cursor and others) read and manage your self-hosted Actual Budget.
What you can ask it: "How much did I spend on groceries last month, by payee?", "Add a $47.50 grocery transaction at Whole Foods to my checking account.", "Move $200 from Dining Out to Emergency Fund for this month."
85 tools across accounts, transactions, budgets, rules, schedules and more, over stdio or HTTP, with Bearer token or OIDC auth, per-user budget access, up to 15 concurrent sessions, and automatic retry of transient Actual errors (3 attempts, exponential backoff; deletes and merges are never retried).
Pick your path
- Claude Desktop, Claude Code, Cursor, VS Code or another local client: run it over stdio with
npx, no server to keep running. Follow your client's page in docs/guides/clients/, for example Claude Desktop or Claude Code. - A chat UI such as LibreChat or LobeChat, or several users: run it over HTTP in Docker with the quick start below, then follow LibreChat or LobeChat.
- A client that installs from the official MCP Registry: it is listed as
io.github.agigante80/actual-mcp-server, with the npm package (stdio) and the Docker image (HTTP); the client asks for the same settings as the pages above. - Unraid: install it from Community Applications; see Unraid.
Quick start (Docker, HTTP)
You need an Actual Budget server and Docker. 1. Create .env with a generated token. In an empty directory:
The last line prints the Bearer token your client sends. It never overwrites a value you set, except a token that is missing, duplicated or shorter than 32 characters, so it is safe to run again.
2. Fill in .env: ACTUAL_PASSWORD, ACTUAL_BUDGET_SYNC_ID (Actual: Settings, Show advanced settings, Sync ID) and ACTUAL_SERVER_URL. The URL is read inside the container, where localhost is the container itself: use your Actual server's LAN address or domain, or http://host.docker.internal:5006 when Actual runs on the Docker host.
3. Start the server from the same directory:
Check it with curl http://localhost:3600/health. The image is also on Docker Hub as agigante80/actual-mcp-server. Production flags, TLS, reverse proxies and the reason for the /app/data volume are in the deployment guide.
Docker Compose (Compose 2.24.0 or later), from a clone of this repository:
On a fresh .env, fill in the three Actual settings, then run the last line again.
npx (Node.js 22 or later, no container), in a directory holding a filled-in .env from step 1, where http://localhost:5006 is right for Actual on the same machine:
Privacy
Budget data the tools return goes to whichever model provider your AI client uses. The server itself contacts only the configured Actual server and, when OIDC auth is configured, your identity provider (discovery and JWKS). Logs stay on the host you run it on. Details: security and privacy.
Compatibility
Node.js 22 or later, Actual Budget server 25.0.0 or later, and the bundled @actual-app/api (its version is in package.json and reported by the actual_server_info tool). Requirements and upgrade steps: upgrading.
Tools
Every tool, with its description and caveats, is in the tools reference.
Reducing the tool surface
All 85 tools are published by default. Chat clients with a small tool budget (Gemini, LibreChat) do better with fewer. A tool that is not published is also refused if a client calls it by name.
The chat preset publishes 12 tools: actual_get_context, actual_query_run, actual_transactions_update_batch, actual_budget_updates_batch, actual_rules_create_batch, actual_transactions_create, actual_transactions_update, actual_transactions_delete, actual_rules_create, actual_budgets_transfer, actual_budgets_setAmount and actual_budgets_getMonth.
MCP_READ_ONLY=true hides and refuses 48 write-capable tools and leaves 37 published.
Example: a chat assistant with two extra tools.
A configuration that resolves to zero tools refuses to start. See Security and Privacy.
Configuration
Every variable, with its type and default: configuration reference. Several budgets: multiple budgets. Auth modes, per-client tokens and OIDC: authentication.
Documentation
- Documentation index: every page.
- Connect a client, deployment, authentication, upgrading, troubleshooting.
- Architecture, testing and reliability.
Contributing
Contributions are welcome. See CONTRIBUTING.md for setup, the checks every change must pass and the PR process. Questions and bug reports: SUPPORT.md.
Security
Report a vulnerability privately as described in SECURITY.md, not in a public issue.
Sponsor
I build and maintain this in my own time. It is free, it stays free, and it gets maintained either way. If it saved you some time, you can say thanks at github.com/sponsors/agigante80. Entirely optional.
License
MIT, see LICENSE. Built on Actual Budget and the Model Context Protocol, with thanks to s-stefanov/actual-mcp for the original adapter pattern. An independent project, not affiliated with Actual Budget, provided as-is without warranty: if you connect it to real financial data, you do so at your own risk.
Version: 0.27.1 | Tool Count: 85 (verified LibreChat-compatible)
Source: README.md at commit 2bf0987
Tools
0Version history
5- v0.27.1LatestNov 4, 2026
- v0.27.0Nov 4, 2026
- v0.26.0Nov 3, 2026
- v0.25.2Nov 3, 2026
- v0.25.1Oct 31, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts