dough-mcp
Query and monitor a Dough personal finance instance through MCP tools.
Get a compact financial snapshot (total balance, monthly income/spending/budgeted, Ready to Assign).
List all accounts with balances, optionally including closed accounts.
Retrieve transactions newest-first, filtered by search, month, category, account, or limit (1–500).
View monthly budget details: income, total budgeted, Ready to Assign, age of money, and per-category budgeted/activity/available.
See current net worth by kind (checking, savings, investments, debts) plus snapshot history.
List recurring bills and subscriptions with amounts and due days.
List active savings goals with targets and derived saved amounts.
Per README, can expose write tools if the Dough instance offers them and the API key has write scope; the provided schema shows read-only tools.
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., "@dough-mcp show my current balance and recent transactions"
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.
Dough MCP server
Read and write your Dough finances from Claude.ai and Claude Code. It offers every tool the Dough instance it points at has, because it takes them from that instance. It runs over stdio for Claude Code, or behind an OAuth 2.1 login so it can be added to Claude.ai as a custom connector.
Since Dough 4.4.0 every instance is an MCP server itself at /mcp, and a client that can connect to a remote MCP server with OAuth can use that directly. dough-mcp is for the rest: a local process over stdio, or a separately hosted endpoint.
Dough is a standalone self-hosted budget app with its own ledger (bank-synced or manual). It is not a YNAB frontend: Dough's data is corrected through these tools or Dough's own UI, never in YNAB.
Using this server with a paid AI service costs money. Tool definitions and results are billed as input tokens, and an agent can call tools repeatedly on its own. You are responsible for every charge, so set spending limits with your provider. The author accepts no liability for any costs. SeeDISCLAIMER.md.
How it fits together
dough (web app) ── /mcp (the instance's own tools, API-key auth)
▲ HTTPS + Bearer key
dough-mcp ── stdio (Claude Code) ──or── HTTP + OAuth 2.1 (Claude.ai connector)The server never sees your database. It passes each tool call to the instance's /mcp with an API key you supply through the environment, so the key stays on your machine and nothing about your ledger is exposed on the internet. Needs Dough 4.4.0 or later.
Related MCP server: LunchMoney MCP Server
Tools
Whatever the instance offers, which is one tool for every part of its API: accounts, transactions and splits, budget and targets, categories, bills, subscriptions, income, savings goals, debts, investments, payees, budget links, settings, Dougie and more. An instance that gains a tool gains it here without a new dough-mcp. Read tools work with any key; write tools need a key minted with --scopes write and return 403 otherwise.
Add to Claude.ai
Settings, Connectors, Add custom connector, and paste the MCP URL of your deployment, for example:
https://dough-mcp.example.com/mcpLeave client ID and secret blank. The OAuth 2.1 login in front (auth-server.cjs) handles registration and sign-in, and issues the token.
Claude Code
Over HTTP, with the fixed token the login also accepts:
claude mcp add --transport http dough https://dough-mcp.example.com/mcp \
--header "Authorization: Bearer $(cat ~/.config/dough-mcp/token)" --scope userOr over stdio, with DOUGH_API_URL and DOUGH_API_KEY set in the environment.
Install
git clone git@github.com:rollecode/dough-mcp.git
cd dough-mcp
npm install && npm run build # dist/ is committed; rebuild only when changing src/Configure via environment:
DOUGH_API_URL— base URL of the Dough instance, e.g.https://dough.example.comDOUGH_API_KEY— an API key minted in the Dough repo (see below)
Get an API key
In the Dough repo, on the host that owns the database:
npx tsx scripts/create-api-key.ts --name "dough-mcp" --scopes writeThe key is printed once. Use --scopes read for a query-only key. See Dough's docs/public-api.md for details.
Available Tools
8 toolsdough_accountsB
All accounts with balances. Set include_closed to also return closed accounts.
Inputs: include_closed.
dough_billsB
Recurring bills with amount and due day of month.
Inputs: no named parameters.
dough_budgetB
The month's budget: income, total budgeted, Ready to Assign, age of money and every active category's budgeted / activity / available.
Inputs: month.
dough_net_worthA
Current net worth by kind (checking, savings, investments, debts) plus the snapshot history.
Inputs: no named parameters.
dough_savings_goalsD
Active savings goals with target and derived saved amount.
Inputs: month.
dough_subscriptionsC
Subscriptions with amount and due day of month.
Inputs: no named parameters.
dough_summaryA
Compact financial snapshot: total balance and this month's income, spending, budgeted and Ready to Assign.
Inputs: month.
dough_transactionsC
Transactions newest first, with optional filters.
Inputs: q, limit, month, category, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Each tool targets a distinct financial data domain (accounts, bills, budget, net worth, savings goals, subscriptions, transactions) with no overlapping purposes. Descriptions clearly differentiate them.
All tools follow a consistent 'dough_' prefix with a plural noun representing the resource (e.g., dough_accounts, dough_bills). This pattern makes it predictable for an agent.
With 8 tools covering core personal finance areas, the count feels well-scoped for a finance data provider. Each tool serves a distinct purpose without redundancy.
The tool set covers major financial categories: accounts, bills, budget, net worth, savings, subscriptions, and transactions. For a read-only data access server, it offers a comprehensive snapshot without obvious gaps.
Maintenance
Related MCP Connectors
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
Read-only finance MCP server. Connects your banks, cards, payment apps, books and payroll into one ledger for your AI. Can't move money. Open source (AGPL-3.0), free during beta.
Query your real net worth, spending, transactions, budgets and portfolio from any MCP client.
Ask your AI about your own accounts, debts, budgets and goals. OAuth sign-in, read-only by default.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides access to personal financial data from Monarch Money, allowing users to retrieve account information, transactions, budgets, goals, and net worth through natural language queries.16-
- AlicenseAqualityBmaintenanceAn MCP server implementation that provides programmatic access to personal finance data through LunchMoney's API, enabling AI assistants to manage transactions, budgets, categories, and assets.59934 npm115MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for accessing and managing Banktivity personal finance data, enabling account, transaction, and budget operations through natural language.3MIT

RiseUp MCP Serverofficial
AlicenseAqualityBmaintenanceMCP server for programmatic read-only access to RiseUp cashflow data, allowing AI assistants to retrieve budget information via natural language.71,180 npm40MIT