YABA family budget

day.yabav1.4.0Updated Oct 10, 2026

Family budget for couples: spending, budget, pace, bills and Monobank-synced entries. OAuth.

VerifiedStreamable HTTPWeb executableFinanceProductivity & Workflow

Overview

AI-generated overview

A remote MCP server that gives an assistant access to a shared family budget: spending, budgets, pace, bills and Monobank-synced entries.

What it does
YABA is a family budget service for couples, exposed as a remote MCP endpoint. According to the registry description, it covers spending, budget, pace, bills and entries synced from Monobank. The manifest lists no tools, so the exact operations an assistant can call are not documented here.
When to use it
Worth considering if you and a partner keep a shared household budget in YABA and want an assistant to look at spending, budget pace or bills without opening the app. It is not useful if you do not already use this service.
Requirements
A remote MCP endpoint at over streamable HTTP; nothing to install locally. The description mentions OAuth, so an account and an authorization step are likely, though the manifest declares no authentication, environment variables or headers.
Before you install
The description mentions Monobank-synced entries, so the server may expose real bank transaction data to the assistant and to the model provider behind it. It is a budget service, so treat any capability that records or changes spending or bills as a write action. The manifest declares no authentication details, so confirm how access is actually granted before connecting.

Installation

In SourceWeft

  1. Open YABA family budget in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "yaba": {
      "type": "http",
      "url": "https://app.yaba.day/mcp"
    }
  }
}

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.4.0LatestOct 10, 2026