Read YNAB account metadata with customer-managed OAuth. Two explicit read commands; no writes.
What you can do (2)
What you can do
Available commands: 2 (2 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
List plans — ynab.plans.list |
Read |
List plan accounts — ynab.accounts.list |
Read |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for YNAB, then enter the issued values in the connection form below.
- Create an OAuth application in YNAB Account Settings > Developer Settings > OAuth Applications, register https://api.tooluse.net/v1/oauth/callback, and copy its client ID and secret into this integration’s connection form. Save, then choose Sign in to provider and approve read-only access. YNAB restricts new apps to 25 other-user authorizations until its application review is approved; apply through the official API site before public rollout. Do not request or share personal access tokens: YNAB reserves those for your own code. Tooluse.net stores the grant encrypted, uses S256 PKCE and refreshes according to the returned expiry. Disconnect here and remove the authorization in YNAB to revoke source access. Choose List plans, then List accounts with the returned plan ID (or last-used/default where enabled). Balances are integer milliunits: 125050 means 125.050 currency units. The accounts delta parameter is last_knowledge_of_server; preserve returned server_knowledge for subsequent reads. No transactions, bank links or writes.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| OAuth access token (optional) | Optional |
| YNAB OAuth client ID | Optional |
| YNAB OAuth client secret | Optional |
| Registered OAuth redirect URI (optional) | Optional |
| Return URL after authorization | Optional |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
List plans — ynab.plans.list
Read accessible plan IDs, names and date ranges. Uses current YNAB plans API. No account expansion, transactions or writes. One response; YNAB does not page this endpoint.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
This tool has no input parameters.
Full JSON Schema
Example input
{}
At most 1 provider requests per invocation; timeout: 30 seconds.
List plan accounts — ynab.accounts.list
Read account summaries and delta knowledge for one plan. Balances are integer milliunits (125050 = 125.050 currency units). No notes, payees, bank links or transactions. Pass returned server_knowledge as last_knowledge_of_server for incremental reads.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.plan_id |
string | Required | Plan UUID, last-used, or default where enabled. | pattern: "^(?:[0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}|last-used|default)$" |
query |
object | Optional | additionalProperties: false |
|
query.last_knowledge_of_server |
integer | Optional | Previous server_knowledge; omit for all accounts. | minimum: 0; maximum: 9007199254740991 |
Full JSON Schema
Example input
{
"path": {
"plan_id": "last-used"
},
"query": {
"last_knowledge_of_server": 1
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.