MCP Ynab 3068f6c3

MCP设计创作

提供方 bold-minds

设计创作 未标注 Token 社区 / 第三方 Claude DesktopClaudeCursor

一个为YNAB预算API提供的模型上下文协议服务器,支持读取预算计划、账户、类别、交易和月度摘要,可选择启用写入功能。

一句话选型结论

按资料字段整理

MCP Ynab 3068f6c3 属于设计创作类 MCP 服务器,传输方式未标注,Token,可直接接入 Claude Desktop、Claude、Cursor,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类设计创作 传输方式未标注 鉴权Token 部署方式未标注
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 17 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

设计创作
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量17暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

预算管理Go本地部署财务管理API集成数据同步安全设计

安装与配置

未标注 Token
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 17 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
出图与素材

生成配图、图标与素材。

设计稿处理

读取设计稿、批量改尺寸或导出。

内容生成

按主题生成文案与视觉草稿。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 17 个工具,覆盖面较广,能满足多种调用。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在设计创作场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP Ynab 3068f6c3当前 17 未标注 未标注 无 2026-05-17
Cursor Talk To Figma MCP Da1c7911 40 未标注 未标注 无 2026-05-17
Blender MCP 17 stdio · 本地进程 本地部署 有 2026-05-18
Nova Canvas MCP Server 2 stdio · 本地进程 本地部署 有 2026-05-17
Figma Context MCP 3aaa8d28 未标注 未标注 支持远程部署 无 2026-05-17
kreuzberg 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

设计创作
字段来自项目仓库与公开索引,中文说明由本站标注
提供方bold-minds上游标注的维护方 bold-minds
分类设计创作本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

20.0 KB
来自项目仓库与上游目录的原文,未做删改

mcp-ynab

A read-only by default Model Context Protocol server for the YNAB budgeting API. Lets an LLM (Claude Desktop, Cursor, Claude Code, or any MCP-compatible client) inspect your plans, accounts, categories, transactions, and monthly summaries. Write tools (create/update/approve transactions, update category budgeted) are available only when YNAB_ALLOW_WRITES=1 is set in the environment — when unset, writes are not registered at startup and cannot be invoked.

Built in Go against the official MCP Go SDK. One binary, stdio transport, no inbound network surface, OS-keyring token storage.

Why read-only

YNAB personal access tokens are long-lived and full-scope — they grant read and write on every plan on the account, and YNAB has no bulk-undo for mutations. An LLM that can call deleteTransaction is one prompt-injected transaction memo away from scrambling a budget with no recourse. This server deliberately exposes only the read endpoints, and the design has no code path that mutates YNAB data.

Tools

Read tools (always available)

Tool Description
list_plans List all YNAB plans (called "budgets" in the YNAB UI) owned by the authenticated user.
list_accounts List accounts in a plan with current balances. Closed accounts excluded by default. Delta-synced.
list_categories List all categories in a plan with this month's assigned / activity / balance amounts and goal details.
list_transactions List transactions for a plan, most recent first. Filter by since_date, approval state (type), or scope — one of account_id, category_id, or payee_id. Unfiltered variant is delta-synced. Category / payee scoping flattens split transactions. Default limit 100, max 500.
list_months Monthly rollup summaries (income, budgeted, activity, to_be_budgeted, age_of_money) for recent months, most recent first. Use for month-over-month trends. Default limit 6, max 60.
get_month Full plan month with per-category breakdown. Accepts "current" or YYYY-MM-01. Use for the Sunday ritual / True Expenses check.
list_scheduled_transactions Recurring and future-dated scheduled transactions in date_next order (soonest first). Optional upcoming_days filter.
list_payees List payees in a plan. Optional name_contains performs a case-insensitive substring match — use to resolve payee names to IDs before calling list_transactions with payee_id or ynab_spending_check with excluded_payee_ids.

Task-shaped tools (composition over primitives)

Tool Description
ynab_status One-call Sunday ritual dashboard: Ready-to-Assign, overspent categories (with credit card payment categories excluded), debt accounts with optional APR enrichment, liquid accounts (checking/savings/cash), days-since-last-reconciled per account, unapproved count, and next-7-days scheduled cash flow with recurrence expansion.
ynab_spending_check "Did I stay under $500 on groceries this week?" Sums net outflow across one or more categories over a date range, compares to a budget, returns on_plan verdict and offending transactions when over budget. Supports excluded_payee_ids for carve-outs like "except Chipotle on date nights".
ynab_weekly_checkin Week-over-week comparison of income, outflows, and unapproved count, plus month-over-month newly-overspent categories and age-of-money delta.
ynab_debt_snapshot Current debt balances + avalanche payoff projection. Integer basis-points simulation, no floats in the compounding loop. Optional extra_per_month_milliunits runs a comparison scenario. Returns structured negative-amortization error with shortfall amount when minimums can't cover interest.
ynab_waterfall_assignment Advisory, no writes. Walks a priority waterfall given per-category need_milliunits the skill has computed, returns proposed allocations and remainder. The LLM presents the plan; if approved, issues update_category_budgeted calls separately.

Write tools (opt-in, require YNAB_ALLOW_WRITES=1)

Write tools are not registered at startup unless YNAB_ALLOW_WRITES=1 is set in the MCP server's environment. When disabled, they do not appear in tools/list and cannot be called at all.

Tool Description
create_transaction Create a new transaction. Asks the MCP client to confirm via elicitation. Amounts > $10K require an amount_override_milliunits echo-back acknowledgment. Provide an import_id to dedupe idempotently on retry.
update_category_budgeted Change the assigned amount on a single category for a single plan month. The primitive for Rule 3 money moves during the Sunday ritual. Returns before/after snapshots of budgeted and balance.
update_transaction Partial update of a transaction: category, payee, memo, approved state, cleared state, flag color. Amount changes are structurally not supported — the input struct has no amount field, enforced by a reflection regression test.
approve_transaction Convenience wrapper setting approved=true on a transaction. Skips per-call elicitation to support batch daily pending-cleanup workflows. The YNAB_ALLOW_WRITES=1 env-var gate remains the primary defense.

All read and task-shaped tools advertise readOnlyHint: true in their MCP annotations. Write tools advertise readOnlyHint: false.

Tool counts:
- Without YNAB_ALLOW_WRITES: 13 tools (8 reads + 5 task-shaped)
- With YNAB_ALLOW_WRITES=1: 17 tools (add 4 writes)

What each tool enables

Use case Tool(s)
"What's my grocery spend this week?" list_categories → find grocery id → list_transactions with category_id
Debt snapshot (all debt accounts + balances) list_accounts (filter to creditCard / loan / debt types)
True Expenses check / overspending detection list_categories or get_month
Month-over-month trend ("am I spending more than last month?") list_months
"What's coming up this month?" (rent, subscriptions) list_scheduled_transactions with upcoming_days: 30
Ready-to-Assign for waterfall conversation get_month → to_be_budgeted field
Pattern detection across a payee list_transactions with payee_id
Eating plan audit list_categories → grocery/restaurant ids → list_transactions with category_id and since_date

Money representation

Every monetary value in a tool response is a Money object with two fields:```json
"balance": { "milliunits": 123456, "decimal": "123.456" }


- `milliunits` is the authoritative int64 value — YNAB's native format, exact across every currency.
- `decimal` is a pre-formatted string with 3 fractional digits (milliunit precision).

**No code path in this server uses `float64` for currency.** Formatting is performed via integer arithmetic only. See `money.go`.

## Install

### Homebrew / prebuilt binaries

Download a release from GitHub Releases — static binaries for Linux, macOS, and Windows (amd64 and arm64).

### Docker```bash
docker pull ghcr.io/bold-minds/mcp-ynab:latest

Distroless-based image (no shell, no package manager), runs as non-root, static binary, stdio-only — no exposed ports.

From source```bash

go install github.com/bold-minds/mcp-ynab@latest


Requires Go 1.25 or newer.

## Configure

### Get a YNAB personal access token

Log in to YNAB, go to **Account Settings → Developer Settings**, and create a **Personal Access Token**. Copy it once — you cannot retrieve it later.

### Provide the token to the server

Three options, in order of preference. The server checks them in the order below and uses the first source that provides a non-empty value.

#### 1. OS keyring (recommended)

Store the token once in your operating system's native credential store (macOS Keychain, Linux Secret Service, Windows Credential Manager):```bash
printf '%s' "your-ynab-personal-access-token" | mcp-ynab store-token

The token is read from stdin — it never appears on the command line, so it never lands in shell history or /proc/PID/cmdline. Subsequent runs of mcp-ynab pick it up automatically with no environment variables needed.

To rotate, re-run store-token with the new value.

2. File-based secret

Useful for Docker secrets, systemd LoadCredential, or Kubernetes secret volumes:```bash
export YNAB_API_TOKEN_FILE=/run/secrets/ynab_token


Keep the file at `chmod 600`.

#### 3. Environment variable (plaintext)

The simplest option, but the token lives in plaintext in process environment:```bash
export YNAB_API_TOKEN=your_personal_access_token

Wire it into your MCP client

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on your OS. If you have stored the token in the OS keyring, you don't need an env block at all:```json
{
"mcpServers": {
"ynab": {
"command": "/path/to/mcp-ynab"
}
}
}


If you prefer file-based:```json
{
  "mcpServers": {
    "ynab": {
      "command": "/path/to/mcp-ynab",
      "env": {
        "YNAB_API_TOKEN_FILE": "/Users/you/.config/ynab/token"
      }
    }
  }
}

Do not paste the raw token into claude_desktop_config.json — that file is typically world-readable and may be backed up by iCloud / Time Machine. Use the keyring instead.

Cursor

Edit ~/.cursor/mcp.json:```json
{
"mcpServers": {
"ynab": {
"command": "mcp-ynab"
}
}
}


(Token comes from the keyring.)

#### Other MCP clients

Any client that speaks the MCP stdio transport can launch `mcp-ynab` as a subprocess. Configure the command to run the binary and provide the token via `YNAB_API_TOKEN`, `YNAB_API_TOKEN_FILE`, or the OS keyring (recommended).

## Security model

### What this server protects against

| Threat                                                                      | Mitigation                                                                                                                                                |
| --------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Prompt-injected instructions telling the LLM to delete/modify financial data | Write tools are gated behind `YNAB_ALLOW_WRITES=1` (opt-in at startup) and every write elicits a per-call confirmation plus a $10K safety cap with echo-back override. When the env var is unset, no write tool is registered and no `POST`/`PATCH`/`PUT` code path can be reached. |
| Token leakage via log statements / `%+v` on a config struct                 | Token is wrapped in a redacting `Token` type. `String`, `GoString`, `Format`, `MarshalJSON`, `MarshalText` all return `[REDACTED]`. Raw value only accessible via a package-private `reveal()` called in exactly ONE place. |
| Token leakage via HTTP-client errors (axios-style config-in-error pattern)  | Adversarial regression test: pathological RoundTripper returns errors containing the literal token; every tool's error path is asserted not to echo it.  |
| Exfiltration of the YNAB token via a rogue URL (SSRF / spec injection)       | Custom `http.RoundTripper` refuses any request whose hostname is not `api.ynab.com` (case-insensitive, port-tolerant). Strips `Authorization` defensively. Refuses all redirects. |
| Token leakage via YNAB error responses surfaced to the LLM                  | All YNAB errors go through `sanitize()`, which strips `Bearer ` and `Authorization:` patterns. No code path formats the raw token into an error.  |
| Runaway LLM exhausting YNAB's per-token rate limit (200 req/hour)            | Token-bucket rate limiter: refill of 1 request per 20 seconds with a burst of 10. Peak: 10 burst + 3600/20 refill = 190 calls in the first hour. Steady-state after the burst drains: 180 calls/hour (3600/20). Enforced in the RoundTripper. |
| Unbounded write access by an LLM with credentials                            | **Write tools are opt-in.** Unless `YNAB_ALLOW_WRITES=1` is set at MCP server startup, write tools are not registered at all and cannot be invoked. When writes are enabled, every write goes through an MCP elicitation confirmation, an amount safety cap with echo-back override for >$10K transactions, and returns before/after state in the response so the calling skill can persist an audit record. |
| Wrong-amount updates on existing transactions                                | `update_transaction` has no amount field on its input struct — amount changes are structurally impossible via this tool. Regression test enforces the field's absence via reflection.                                                    |
| Hung upstream                                                                | 30-second per-request timeout, 8 MB response body cap.                                                                                                    |
| Plaintext token storage                                                      | OS keyring is the recommended storage path; file-based and env-var are fallbacks documented with tradeoffs.                                                |
| Inbound network attack on the server                                         | stdio transport only — no listening socket, no HTTP endpoints.                                                                                             |
| Floating-point drift in money arithmetic                                     | All currency stored as int64 milliunits. Formatting is integer arithmetic only. No `float64` anywhere in the money path.                                   |

### Defense-in-depth

- **Token type**: `Token` struct blocks every standard format/serialize path. `UnmarshalJSON` and `UnmarshalText` refuse, so an attacker-controlled payload cannot inject a valid Token.
- **Schema validation**: tool arguments are validated against SDK-derived JSON Schemas before any handler runs. Missing required fields produce JSON-RPC `-32602 invalid params` protocol errors at the SDK layer — our handlers are never reached.
- **Error sanitization at the tool boundary**: every handler wraps its error through `sanitizedErr` before returning, as a final defense even if an inner error escapes without going through the client's own sanitization.
- **No shell execution**: no `os/exec` call anywhere in the credential or runtime path.
- **No hardcoded credentials**: tests use fake sentinel values.

### What it does NOT protect against

- A fully compromised upstream `api.ynab.com` (TLS verification is on, but no certificate pinning).
- A fully compromised MCP client (the client sees every tool response in plaintext).
- An adversarial user on your own machine with read access to your keyring / token file.
- The bare token value appearing in a YNAB error response body as a non-`Bearer`-prefixed substring (unlikely in practice).

## Enabling writes

By default, `mcp-ynab` is read-only. To enable write tools, set `YNAB_ALLOW_WRITES=1` in the MCP server's environment:```json
{
  "mcpServers": {
    "ynab": {
      "command": "mcp-ynab",
      "env": {
        "YNAB_ALLOW_WRITES": "1"
      }
    }
  }
}

When writes are enabled:
- The 4 write tools appear in tools/list alongside the 13 read and task-shaped tools.
- Every write goes through an MCP elicitation confirmation prompt (on clients that support it — Claude Code does, Claude Desktop does not; the env-var gate is the sole defense on clients without elicitation).
- Amounts > $10,000 milliunits require an amount_override_milliunits parameter equal to the main amount, forcing the LLM to explicitly re-assert the value.
- Every write returns before/after state in its response; the calling skill is responsible for persisting an audit trail from those responses (the MCP itself writes no logs to disk).

Known limitations

  • Delta sync is unfiltered-only. list_accounts and unfiltered list_transactions use last_knowledge_of_server for bandwidth savings. Filtered list_transactions (with since_date, type, or scope) always does a full fetch — YNAB's delta semantics on filtered endpoints are under-documented.
  • Delta cache has no TTL or size cap in v0.2.0. For single-session MCP processes (minutes to hours) this is fine; for long-running daemons it grows unbounded. See delta.go for the memory profile discussion.
  • English-only assumptions — see docs/ASSUMPTIONS.md for the full list, notably the "Credit Card Payments" group name match in ynab_status.
  • twiceAMonth schedules are approximated as 15-day advances in the recurrence iterator because YNAB's API doesn't expose the user's two anchor days. For 7-day dashboard windows this under-counts by at most one occurrence. See docs/ASSUMPTIONS.md.
  • Amount cap is currency-agnostic at 10 million milliunits. Correct for USD ($10K); tighter than intended for currencies with different subunit scales (e.g., JPY ~$70 USD equivalent).

Roadmap

Deferred from v0.2:

  • Currency-aware amount caps — fetch the plan's currency_format.iso_code and use a per-currency threshold table.
  • Bounded delta cache — LRU eviction or time-based TTL once long-running session patterns reveal whether it matters.
  • twiceAMonth accurate expansion — use date_first and date_next to derive the two anchor days per month.
  • Delta sync for filtered reads — once YNAB's documentation clarifies the semantics with query filters.
  • Write tool: delete_transaction — highest-risk write, not shipping until there is a strong user case.

Development```bash

go test -race ./... # run tests with race detector
go vet ./...
go build ./...
staticcheck ./...
govulncheck ./...


Docker build:```bash
docker build -t mcp-ynab:dev --build-arg VERSION=dev .

Running locally against the real YNAB API```bash

echo -n "your-token" | mcp-ynab store-token # one-time, uses OS keyring
./mcp-ynab # run the server
```

The server reads JSON-RPC messages from stdin and writes responses to stdout. All logs go to stderr — the binary never touches stdout from its own code, or it would corrupt the transport framing.

Adding a tool

  1. Define input/output structs in tools.go with json and jsonschema tags.
  2. Add a handler method on *Client.
  3. Register it in registerTools with an appropriate ToolAnnotations hint.
  4. Add a test in tools_test.go using the testClient helper.
  5. Add a subprocess test in subprocess_test.go if the tool has required arguments, to confirm the SDK validation layer rejects missing fields.

The MCP SDK automatically derives JSON Schemas from struct types and validates incoming arguments before the handler runs.

License

MIT — see LICENSE.

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
MCP Ynab 3068f6c3 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

MCP Ynab 3068f6c3 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

MCP Ynab 3068f6c3 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

MCP Ynab 3068f6c3 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

MCP Ynab 3068f6c3 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

MCP Ynab 3068f6c3 能提供哪些能力?

资料显示约 17 个工具;能力标签包括 Go、Claude、财务管理。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。