Budget Tracker

io.github.emnbcPublished by GitHub account emnbcv0.7.2Updated Oct 24, 2026

joinBudget MCP: Manage personal finances, budget spaces, transactions, and categories.

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Lets an assistant manage personal finances, budget spaces, transactions, and categories through a local MCP server.

What you can do
Budget Tracker is a local MCP server for personal finance management. According to its description, it covers budget spaces, transactions, and categories, letting an assistant work with budgeting records. No individual tools are listed in the manifest.
When to use it
Use it when you want an assistant to help organize personal budgeting data such as budget spaces, transactions, and categories on your own machine. It is not aimed at shared or team finance workflows.
Requirements
Runs as a local process over stdio on the user's machine; desktop only, with no web executable. No packages, authentication, environment variables, or headers are declared, so setup details are not specified.
Before you install
The description does not state whether the server can create, modify, or delete transactions and categories, so assume it may write to your budget data. No credentials, payments, or third-party data sharing are described.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.7.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.