
Model Context Protocol for YNAB (you need a budget)
Model Context Protocol for YNAB (you need a budget)
·
A Model Context Protocol (MCP) server for interacting with your YNAB plans at https://ynab.com
In order to have an AI interact with this tool, you will need to get your Personal Access Token from YNAB: https://api.ynab.com/#personal-access-tokens. When adding this MCP server to any client, you will need to provide your personal access token as YNAB_API_TOKEN. This token is never directly sent to the LLM. It is stored privately in an environment variable for use with the YNAB api.
A Model Context Protocol server that lets an AI assistant read and modify a YNAB plan.
The server talks to the YNAB API through the official
ynab SDK. Your Personal Access Token
lives in an environment variable and is never sent to the model.
It runs two ways from one codebase:
Both entry points register the shared tools from src/registry.ts. The Worker
can also run an optional scheduled auto-budget service that records what it
would categorize, approve and assign without changing your plan and delivers
spending alerts; see
Auto-budget service.
Other providers:
Get a Personal Access Token from https://api.ynab.com/#personal-access-tokens, then:
npm install
npm run buildEnvironment variables:
| Variable | Required | Purpose |
|---|---|---|
YNAB_API_TOKEN | yes | Personal Access Token used for every API call |
YNAB_PLAN_ID | no | Default plan, so tools can omit planId. Find it with ynab_list_plans. |
TYPESAFE_API_KEY | no | Operator-owned TypeSafe credential. Required, but not sufficient, to enable category suggestions. |
YNAB_AI_CATEGORIZATION | no | Set to "true" together with TYPESAFE_API_KEY to expose the opt-in suggestion tool. |
YNAB_AI_TYPICAL_PAYEES | no | Set to "true" to send each category's most frequent payee names from the last 12 months with each model request. Off by default because it discloses aggregated payee history to TypeSafe. |
YNAB_READ_ONLY | no | Set to "true" (case-insensitive; surrounding whitespace is ignored) to remove tools that write to YNAB, in the stdio server, the HTTP server and the Worker. |
YNAB_MCP_HOST, PORT | no | HTTP server only. Address and port to listen on; default 127.0.0.1 and 3000. |
YNAB_MCP_ALLOWED_ORIGINS | no | HTTP server only. Comma-separated browser origins allowed to call /mcp (e.g. https://app.example.com). Each entry is reduced to scheme, host and port, so a trailing slash is ignored. Empty by default, which refuses every request that carries an Origin header. |
YNAB_MCP_ALLOWED_HOSTS | no | HTTP server only. Comma-separated extra Host hostnames accepted while listening on a loopback address, for a reverse proxy on the same machine that forwards the client's Host (e.g. mcp.example.com). |
ALLOWED_GITHUB_LOGIN | no | Worker only. The single GitHub login allowed through GitHub sign-in. Required for GitHub sign-in. |
GITHUB_CLIENT_ID, GITHUB_CLIENT_SECRET | no | Worker only. The GitHub OAuth app's credentials. Required for GitHub sign-in. |
ALLOWED_REDIRECT_URIS | no | Worker only. Exact OAuth callback URIs that GitHub sign-in may deliver grants to. See Restricting redirects. Must be unset with Cloudflare Access. |
CF_ACCESS_TEAM_DOMAIN | no | Worker only. Your Cloudflare Access team domain (<team>.cloudflareaccess.com). Setting any CF_ACCESS_* value replaces GitHub sign-in with Cloudflare Access, which needs all three. |
CF_ACCESS_AUD | no | Worker only. The Access application's Audience (AUD) tag. |
CF_ACCESS_ALLOWED_EMAIL | no | Worker only. The single email allowed through Access. Any other identity, including a service token, is refused. |
{
"mcpServers": {
"ynab": {
"command": "node",
"args": ["/absolute/path/to/ynab-mcp-server/dist/index.js"],
"env": {
"YNAB_API_TOKEN": "your-token",
"YNAB_PLAN_ID": "your-plan-id"
}
}
}
}To run the server in a container or behind your own reverse proxy or MCP gateway, start the HTTP entry point instead of the stdio one.
It does no authentication of its own. Anyone who can reach
/mcpuses your YNAB token with every tool you expose, including the write tools unlessYNAB_READ_ONLYis set. It listens on127.0.0.1unless you setYNAB_MCP_HOST; only widen that on a private network or behind a proxy that authenticates callers. For a hosted endpoint with sign-in built in, use the Worker below.
On this machine only:
npm run build
YNAB_API_TOKEN=your-token npm run start:httpOutside a checkout, name the package as well as the command, so npm never
looks up a package called ynab-mcp-server-http:
YNAB_API_TOKEN=your-token npx --package ynab-mcp-server ynab-mcp-server-httpIn a container, where it must listen on every interface, start read-only unless whatever sits in front of it authenticates callers:
YNAB_API_TOKEN=your-token YNAB_READ_ONLY=true YNAB_MCP_HOST=0.0.0.0 PORT=3000 node dist/http.jsIt serves stateless streamable HTTP
at POST /mcp and a health check at GET /healthz, with the same tools and
environment variables as the stdio server. It holds one YNAB client for the
life of the process, so the plan-settings cache is shared across requests.
Bound to a non-loopback address with the write tools on, it prints a warning
at startup.
To stop a web page reaching it through DNS rebinding, /mcp refuses with a
403 any request that carries an Origin header not listed in
YNAB_MCP_ALLOWED_ORIGINS. Browsers always send Origin on a POST;
gateways and server-side MCP clients do not, so they are unaffected. While it
listens on a loopback address it also refuses any request whose Host is not
localhost, 127.0.0.1 or [::1].
A reverse proxy on the same machine usually forwards the client's Host
(Caddy and Traefik by default, nginx with proxy_set_header Host $host), which
that check refuses with 403 Host not allowed. Either have the proxy send the
upstream address as Host (Caddy: header_up Host {upstream_hostport};
nginx's default $proxy_host already does), or list the public hostname in
YNAB_MCP_ALLOWED_HOSTS.
The stdio server above cannot be reached from a phone. To use these tools from
claude.ai, the Claude mobile app, or another MCP client that supports remote
servers, deploy src/worker/ to Cloudflare Workers and add its /mcp URL to
the client. The Worker is not tied to Claude. DEPLOY.md has the
full walk through; the shape of it:
wrangler.example.jsonc to the git-ignored wrangler.jsonc, remove
the optional placeholder AUTOBUDGET_DB block unless you are configuring
the auto-budget service, and
run npx wrangler loginnpx wrangler secret put for YNAB_API_TOKEN, and optionally
YNAB_PLAN_ID. TYPESAFE_API_KEY is optional too, needed only for
category suggestionsnpm run deployhttps://<host>/mcp to your MCP client, for example as a custom
connector in claude.ai, and complete the sign-in it opensFor a Cloudflare account that uses Access. Access signs the client in at
Cloudflare's edge, so no GitHub OAuth app or OAUTH_KV namespace is needed.
Full steps: Cloudflare Access.
kv_namespaces block from wrangler.jsonc, and deploy once
so the Worker existsnpm run cf-access (setup script) or in the
dashboardnpx wrangler secret put for CF_ACCESS_TEAM_DOMAIN, CF_ACCESS_AUD,
and CF_ACCESS_ALLOWED_EMAIL, and leave ALLOWED_REDIRECT_URIS unsetThe Worker runs its own OAuth flow with GitHub as the identity provider. Full steps: GitHub sign-in.
OAUTH_KV namespace and put its ID in wrangler.jsoncnpm run deploy once to learn your *.workers.dev hostnamehttps://<host>/callbacknpx wrangler secret put for ALLOWED_GITHUB_LOGIN,
GITHUB_CLIENT_ID, and GITHUB_CLIENT_SECRETThe YNAB token stays a Worker secret and never reaches the client. The sign-in
controls who may connect to the remote Worker; the YNAB Personal Access
Token controls which YNAB account it reaches. They answer different
questions, and neither substitutes for the other. The Worker uses one
server-wide YNAB token, so anyone admitted through the sign-in reaches the
deployer's YNAB account, money, and every plan available to that token—not
their own YNAB account.
ynab_list_plans lists all of those plans, and a caller-supplied planId
overrides the optional YNAB_PLAN_ID default. This matters because the tool
set can create and delete transactions—an unauthenticated endpoint would grant
access to those plans to anyone who found the URL. Each sign-in admits one
account:
CF_ACCESS_ALLOWED_EMAIL; the Access
application's allowed redirect URIs decide which clients can connect. See
Cloudflare Access for its configuration and
client compatibility notes.ALLOWED_GITHUB_LOGIN. Each sign-in shows an approval
page naming the client and callback address, and ALLOWED_REDIRECT_URIS can
restrict clients to exact callbacks. See
Approving MCP clients.Any MCP client that supports remote servers with OAuth can connect, for example Claude, ChatGPT connectors, Claude Code, or the MCP Inspector.
YNAB OAuth is deliberately not supported. Its token exchange requires a client secret even with PKCE; an open-source package cannot ship a secret, so a local package cannot honestly implement the authorization-code flow (OAuth application requirements). The only secretless flow YNAB documents is the implicit grant, which expires in two hours with no refresh (OAuth application requirements). YNAB recommends a Personal Access Token for an individual accessing their own account (Personal Access Tokens).
Setting YNAB_READ_ONLY to "true" drops every YNAB write tool from the tool
list, which is worth considering for a connector you will mostly use on a phone.
Plan-scoped tools take an optional planId that falls back to
YNAB_PLAN_ID. Optional tool inputs may be null; the server treats null
the same as omitting that input. All monetary values — in both directions — are
plain currency amounts, never YNAB's milliunits. Reported amounts use the
plan currency's precision (three decimals for currencies such as the Kuwaiti
dinar) and fall back to two decimals if its settings cannot be read; conversion
happens in src/tools/money.ts.
| Tool | What it does |
|---|---|
ynab_list_plans | Every plan on the account. Run this first to find a plan ID. |
ynab_plan_summary | A month at a glance: income, budgeted, activity, Ready to Assign, plus categories split into overspent, underfunded (goal not yet met) and positive_balance. Hidden and deleted categories are excluded. budgetVsActuals: true adds a budget_vs_actuals block: budgeted, activity, balance, variance (budgeted plus activity) and percent_used (null when nothing was assigned) per category, subtotalled per category group and in totals. Credit Card Payments is listed as its own group but left out of totals, since its activity is card spending moving in minus payments going out. YNAB's internal Inflow: Ready to Assign category (whose activity is the month's income) is skipped; other internal categories, such as Uncategorized, are listed and counted when they have activity. |
ynab_list_accounts | Accounts with balances. includeClosedAccounts to see closed ones. |
ynab_list_categories | Categories grouped by category group, with goal info. |
ynab_list_payees | Payees, for resolving payee IDs. |
ynab_list_months | Every plan month since the plan began, with raw income, budgeted, activity, Ready to Assign, age-of-money and note fields. For recent income versus spending, use ynab_cash_flow. |
ynab_list_scheduled_transactions | The scheduled transactions set up in YNAB. For recurring charges found in transaction history, see ynab_detect_recurring; for a projected balance, ynab_balance_forecast. |
ynab_get_transactions | Transactions optionally filtered to sinceDate–untilDate, by type (all/uncategorized/unapproved), and by at most one of accountId, categoryId or payeeId (the first in that order wins). To search, add payeeContains, memoContains (case-insensitive), minAmount/maxAmount (ignoring sign) or direction (outflow/inflow/any); any search option or untilDate adds a totals block (count, inflow, outflow, net) over every match, including transfers between accounts, and totalsOnly: true returns only that. Without categoryId or payeeId, splits are matched leg by leg and the totals count only the matching legs; with them, rows are matched as YNAB returns them, so a split's parent row in the payee listing counts at its full amount. Rows come back newest first; limit defaults to 100, keeps the most recent rows, and does not affect the totals. |
ynab_suggest_categories | Opt-in, read-only category previews for unapproved, uncategorized ordinary outflows. Deleted and categorized rows are dropped in default mode; approved, reconciled, balance-adjustment, transfer, split, and inflow rows are skipped as applicable. |
ynab_apply_category_suggestions is a separate write tool that is available
without enabling the TypeSafe preview. Provide up to 25 explicit
transaction_id, category_id, and expected_content_fingerprint rows. The
tool refetches each transaction and rejects stale or ineligible changes; a retry
whose category is already applied is a no-op. It supports validation-only dry
runs and returns a pre-write undo manifest, but does not perform the undo. It
never auto-applies suggestions, calls TypeSafe, or approves transactions.
ynab_suggest_categories is off by default. To expose it, set both an
operator-owned TYPESAFE_API_KEY and YNAB_AI_CATEGORIZATION=true, then restart
the server. The API key is read from the environment (or a Worker secret), never
from a tool argument. Omit transactionIds, pass null, or pass an empty
array to fetch unapproved transactions and retain only uncategorized rows;
provide IDs to inspect only those transactions. In default mode, the tool
checks every retained row for deterministic eligibility and then applies
limit to the first eligible outflows in YNAB's returned order. Skipped rows
do not consume the limit.
The tool is a dry-run preview: it never writes to YNAB, approves a transaction,
or changes the behavior of ynab_update_transaction. It first handles exact
facts in code—dropping deleted rows and handling approved or reconciled rows,
YNAB balance adjustments, transfers, splits, inflows, existing categories, and
hidden/internal categories. In default mode, transactions contains only the
eligible rows inspected, transaction_count is that row count, and
eligible_transaction_count reports all eligible rows available before the
limit. The top-level skipped object reports total_count and a count plus
transaction_ids for each reason: skipped_approved, skipped_reconciled,
skipped_balance_adjustment, skipped_transfer, skipped_split,
skipped_inflow, and skipped_already_categorized. With explicit
transactionIds, every non-deleted fetched row remains an individual result,
including rows carrying a skipped_* status; deleted rows are omitted.
Payee history uses the latest 12 months, capped at 50 qualifying rows. When the
payee has no qualifying rows with the same payee ID, history falls back to rows
from payees with a similar name: after Unicode NFC normalization, lowercasing,
and removing everything except letters and numbers, one name begins the other
and the shorter is at least six characters, so a truncated bank payee such as
"Better Bl" draws on "Better Blend" history. Each history summary reports
match (payee, similar_payee_name, or null) and
matched_payee_names.
Each eligible row is then routed in this order, and source names the step
that answered:
history_rule). When at least one qualifying row
has the same payee ID and every such row uses the same still-eligible
category, that category is suggested. When those rows disagree, the row is
needs_review and proposes the most recently used category, with the
others as top_alternatives carrying their history_count. No model call is
made for either case.personal_prior). A naive-Bayes classifier is trained
for each request on the plan's own categorized ordinary outflows from the
same 12-month history, using payee and bank-import name tokens, the account,
and a coarse amount bucket. It is used when history contains categorized
rows across at least two categories; a single-category prior cannot rank
alternatives. Name tokens never seen in training are ignored rather than
scored. When its top category reaches probability 0.9, the row is
suggested without a model call. The probability is reported under
personal_prior.ranking, never as model_confidence. Below 0.9 the prior
only ranks: its top three appear on the model's row for comparison.jev). Every remaining row goes to TypeSafe's pinned
jev-1.13.0 System One model in batches of ten. A model answer is a ranked
shortlist, never a suggestion: every answer that names a category is
needs_review, while an explicit model abstention is left_uncategorized.
The pinned model's stored review threshold is therefore 0; thresholds stay
model-specific because confidence scales differ between models.Similar-name history is never a rule; when a row reaches the model, it is
included as suggestive evidence. The history summary's reference_category_id is the category a
proposal is compared with: the most recently used one for exact-payee history,
and the plurality for similar-name history. A similar-name disagreement is
reported as conflict but does not change the status, because a prefix match
does not establish merchant identity. Every inspected eligible row includes a
status, source, content fingerprint, proposed category, model confidence and
winning probability (model rows only), up to three alternatives, the history
summary, and the personal-prior ranking where one was computed. The response's
thresholds object reports the values in force, and personal_prior reports
how many rows trained the prior and whether it was available for routing.
Applying a suggestion remains a separate, explicit human decision using
ynab_apply_category_suggestions (or the general ynab_update_transaction
tool).
Why this order: households file payees their own way, such as restaurants under a groceries category or clinics under a savings category. A general-purpose model cannot know that, but the plan's own history encodes it. On real household history, history rules and the personal prior were much more accurate than a model on the same rows. The model's high-confidence answers were wrong far more often than on synthetic fixtures, which is why they are review-only. To evaluate your own plan, or a local model, see Evaluating categorization and local decision models.
Enabling this feature sends the transaction's display payee, imported/original
payee, memo, amount, date, and account name/type/on-budget status, plus visible
category group and category names, to TypeSafe as a third-party processor.
For model-bound rows with similar-name matches, it also sends the matched payee
names and per-category key, group, name, and count. When
YNAB_AI_TYPICAL_PAYEES=true, each model request also lists up to eight of each
category's most frequent payee names from the last 12 months
(typical_payees), and the response sets
typical_payees_sent: true. This makes the model noticeably more accurate on a
household's own filing habits, but it discloses aggregated payee history, so it
is off by default. It does not send YNAB UUIDs, balances, goals,
approval/cleared state, or raw transaction history. Rows answered by history or
the personal prior are never sent. TypeSafe's published
Jev 1.13 price at the time of this release is $0.042 per million input tokens;
output tokens are free. The tool returns preflight estimates, actual token
usage, and projected cost on each run
and refuses requests over its per-call token/cost ceilings. Pricing and
provider limits can change; check https://docs.typesafe.ai/models.
The prototype is intentionally narrow and not default-on. Its original 98.3% exact-label, 98.9% top-three, and 60/60 expected-abstention results came from 40 synthetic, single-evaluator fixtures, not a production accuracy claim. Real household history is much harder, as described above.
In the spending reports, splits are counted through their subtransactions and transfers between your own accounts are excluded, so they report spending rather than money movement.
| Tool | What it does |
|---|---|
ynab_spending_by_category | Total spend per category over a date range, biggest first, with share of total. Defaults to the last 30 days. With monthly: true, each category also gets spend per calendar month, its mean over the full months, and its last full month's change against the earlier full months, over the last months months (default 6, at most 24) or from sinceDate, which overrides months; untilDate then defaults to today. Totals are gross outflows, so refunds aren't netted. |
ynab_spending_by_payee | The same, grouped by merchant, including monthly. |
ynab_cash_flow | Income vs spending per month with the running net, from YNAB's own monthly totals. Defaults to the last 6 months. |
ynab_balance_forecast | The combined balance of your accounts over the next days (default 30, max 365, from today in UTC), projected from scheduled transactions only: starting balance, the scheduled events, the end-of-day running balance, the lowest point and the ending balance. accountIds picks the accounts; the default is every open on-budget account. limit caps the events (default 100, 0 leaves them out); event_count, the running balance, low point and ending balance always cover every event. Transfers between two included accounts (credit card payments too) net to zero; a transfer to an account outside the forecast counts as money leaving, and one from such an account as money arriving. Splits are counted leg by leg. Occurrences whose date has passed but that YNAB hasn't entered yet count on the first day, marked overdue with their scheduled_date and summarised in overdue_schedules. A twice-a-month schedule's second date is approximated as 15 days after the first when YNAB doesn't give it, and marked approximate. |
ynab_detect_recurring | Recurring outflows such as subscriptions and bills: a payee's charges of a similar amount at a regular interval (weekly to yearly), with typical amount, yearly cost at the latest amount, next expected date, whether it seems to have stopped, and whether a scheduled transaction has the same payee name. Loan and mortgage payments are transfers, so they are not included, and refunds are not netted. A heuristic; defaults to the last 365 days. |
| Tool | What it does |
|---|---|
ynab_create_transaction | Creates a transaction. Needs date, amount, an account (accountId or accountName) and a payee (payeeId or payeeName); category optional as categoryId or categoryName, or subtransactions to split it. |
ynab_update_transaction | Updates any subset of an existing transaction's fields, or splits an unsplit one with subtransactions. |
ynab_delete_transaction | Deletes a transaction. Not undoable. |
ynab_bulk_approve_transactions | Approves an array of transaction IDs in one API call, or un-approves them with approved: false. |
ynab_apply_category_suggestions | Applies up to 25 explicit category suggestions with refetch and stale-data checks, dry-run support, and a pre-write undo manifest. Never auto-applies or approves transactions. |
ynab_update_category_budget | Sets the total budgeted amount for one category in a month. Not an increment; use ynab_move_money to move money between categories. |
ynab_import_transactions | Triggers an import from linked institutions, the same as hitting Import in the YNAB app. |
ynab_move_money | Moves budgeted money between two categories in a month, for covering overspending. |
ynab_auto_assign | Spreads Ready to Assign over categories with unmet monthly goals, largest shortfall first. dryRun to preview, maxTotal to cap it. |
ynab_create_transaction accepts accountName and categoryName and matches
them loosely against the plan, so "ally checking" finds Ally Checking.
Closed accounts and hidden categories are never matched. If a name is ambiguous
or unrecognised the call fails and names the near misses rather than guessing,
and successful calls echo back matchedAccount / matchedCategory so a wrong
guess is visible.
ynab_create_transaction and ynab_update_transaction split a transaction
across categories when given subtransactions: two or more entries of
{ amount, category_name, payee_name, memo }, the same shape
ynab_get_transactions returns for a split. Amounts are in dollars and must add
up to the transaction amount exactly (on update, the new amount if given,
otherwise the current one); categories go on the splits, not on the parent.
Split category names are matched like categoryName and echoed back as
matchedSplitCategories.
YNAB cannot change the splits of a transaction that is already split, so
ynab_update_transaction refuses rather than silently dropping the change.
Delete and recreate the transaction to re-split it.
YNAB has no endpoint for moving money between categories, so ynab_move_money
rewrites both categories' budgeted amounts in two calls. It takes from the
source first, so a failure in between leaves the money in Ready to Assign rather
than double-counted. When that happens the response sets partial: true and
carries a recovery line with the original amount to restore. ynab_auto_assign
behaves the same way: on failure it reports which categories were already funded
and which were left alone.
Tools never throw at the protocol level. Failures come back as an MCP error
result (isError: true) with { "success": false, "error": "..." } in the
text content, so a failed write is never mistaken for a successful one.
Every tool advertises MCP annotations (readOnlyHint, destructiveHint,
idempotentHint, openWorldHint) alongside its schema. Tools that change
neither YNAB nor the Worker's service state are readOnlyHint: true; among the
YNAB writing tools, only ynab_delete_transaction sets destructiveHint: true.
A client may use these hints to decide which calls need a confirmation prompt.
cleared and flagColorynab_create_transaction and ynab_update_transaction accept cleared as
one of cleared, uncleared, or reconciled, and flagColor as one of
red, orange, yellow, green, blue, purple, or "" to clear an
existing flag.
npm run watch # rebuild on change
npm test # vitest (watch mode)
npm run test:run # vitest, single run
npm run test:coverage # coverage report
npm run typecheck # typecheck both the node and Worker targets
npm run debug # build, then open the MCP inspector
npm run dev:worker # run the Worker locally with wrangler
npm run deploy # deploy the Worker to Cloudflaredist/ is a build artifact and is not tracked in git; npm run build regenerates it.
Bump the version in package.json and update CHANGELOG.md, then merge to main and create a GitHub release tagged in the existing 0.2.0 style (without a v prefix). The workflow stages that release with npm; it does not make the package public. The maintainer must run npm stage list, review it, and run npm stage approve with 2FA to promote it live. Configure a Trusted Publisher on npmjs.com for ynab-mcp-server, pointing at GitHub repository calebl/ynab-mcp-server and the exact workflow filename .github/workflows/publish.yml (the filename must match exactly); under Allowed actions select only npm stage publish.
Each tool is a self-contained module in src/tools/ exporting name,
description, inputSchema (a Zod shape) and execute(input, api). See
CLAUDE.md for the full template, then add the module to the tools array in
src/registry.ts and write a test in src/tests/. Registering it there serves
it from both the stdio server and the Worker; mark writes: true if the tool
changes data, which is what YNAB_READ_ONLY filters on.
Useful references:
node_modules/ynab/dist/index.d.tsPull requests are welcome. For a new tool or a larger change, please open an issue first so we can agree on the scope.
main.src/tests/. New tools follow
the pattern in Adding a tool.npm run test:run and npm run typecheck.main.Every pull request runs the test suite on Node.js 22, 24 and 26 and receives an automated code review. Both checks must pass and review conversations must be resolved before the pull request can be merged.
budgetId and YNAB_BUDGET_ID are deprecated but still
accepted; there is no removal date. Use planId and YNAB_PLAN_ID for new
integrations.
See LICENSE.
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add ynab -- node /absolute/path/to/ynab-mcp-server/dist/index.js{
"mcpServers": {
"ynab": {
"env": {
"YNAB_PLAN_ID": "",
"YNAB_API_TOKEN": ""
},
"args": [
"/absolute/path/to/ynab-mcp-server/dist/index.js"
],
"command": "node"
}
}
}code --add-mcp '{"name":"ynab","env":{"YNAB_PLAN_ID":"","YNAB_API_TOKEN":""},"args":["/absolute/path/to/ynab-mcp-server/dist/index.js"],"command":"node"}'[mcp_servers.ynab]
command = "node"
args = ["/absolute/path/to/ynab-mcp-server/dist/index.js"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/ynab-mcp-server-2 to learn what the "Ynab Mcp Server" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
This server runs locally, so we can't read its tool list over the web yet.
We could not run this server: it ships no npx package for our sandbox and no public endpoint. The four checks that need a live server are left out, and the grade tops out at B until one exists.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/ynab-mcp-server-2)Nothing comparable is listed yet.
0.9.0Release notes0.8.0Release notes0.7.2Release notes0.7.1Release notes0.7.0Release notes0.6.0Release notes0.5.0Release notes0.4.2Release notes0.4.1Release notes0.4.0Release notes0.3.0Release notes0.2.1Release notes0.2.0Release notes0.1.2Release notes0.1.1v0.1.1Release notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "ynab-mcp-server-2" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.