Harvey Budget

io.github.meltingpixelsaiPublished by GitHub account meltingpixelsaiv1.0.0Updated Oct 24, 2026

Agent spending management with budget tracking, ROI analysis, and spend approval.

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Lets an assistant manage agent spending with budget tracking, ROI analysis, and spend approval.

What you can do
Harvey Budget is a local MCP server for agent spending management. According to its description, it covers budget tracking, ROI analysis, and spend approval. It connects to a Supabase budget database and is configured with a Solana wallet address for receiving USDC payments. No individual tools are listed in the manifest.
When to use it
Consider it when an assistant needs to track budgets, analyze return on investment, or route spending decisions through an approval step. It suits setups where agent spending is recorded in a Supabase database and payments are received in USDC on Solana. It is less relevant if you only need general accounting or reporting without agent spend controls.
Requirements
Runs locally as a stdio process, installed from the npm package @meltingpixels/harvey-budget, so Node.js is needed. Requires SUPABASE_URL and the secret SUPABASE_SERVICE_ROLE_KEY, plus a PAYMENT_WALLET Solana address for receiving USDC payments. Desktop only; no web executable. No authentication is declared.
Before you install
Requires a Supabase service role key (SUPABASE_SERVICE_ROLE_KEY), which is a high-privilege credential granting broad access to the budget database; store it carefully and prefer a scoped key if possible. The server is tied to a Solana wallet address (PAYMENT_WALLET) for receiving USDC payments, so review how payments and approvals are handled before use. No tool list is published, so the exact write, approval, or payment actions cannot be verified in advance.

Installation

In SourceWeft

  1. Open Harvey Budget 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.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

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

Version history

1
  1. v1.0.0LatestSep 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.