Log inSubmit server
MCPSpend logo

MCPSpend

by andreisirbu91-lab

Tracks MCP tool-call costs through a local proxy, dashboard, and MCP usage-query server.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCPSpend

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "andreisirbu91-lab-mcpspend": {
      "command": "npx",
      "args": [
        "--yes",
        "@mcpspend/proxy@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx --yes @mcpspend/proxy@latest

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

andreisirbu91-lab/MCPSpend MCP server tracks MCP tool-call usage and cost through a stdio proxy that wraps configured MCP servers. It can detect configurations for Claude Desktop, Cursor, Windsurf, VS Code, and Claude Code, then stream usage metadata to the MCPSpend dashboard. A separate MCP server exposes usage queries such as daily cost and top tools through stdio or HTTP. Reach for it when you need per-tool or per-project spend visibility without sending tool arguments or response bodies off the machine.

Use cases

  • Track MCP tool-call costs by tool and project
  • Inspect daily usage from an MCP client
  • Review top MCP tools and sessions in a dashboard
  • Monitor usage across Claude Desktop, Cursor, Windsurf, or VS Code

Key features

  • Local stdio observability proxy
  • Per-tool and per-server usage attribution
  • MCP-based usage queries
  • Dashboard with sessions and CSV export
  • Metadata-only telemetry for tool calls
  • HTTP and stdio MCP access

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

18/18 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · @mcpspend/proxy@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars66Stargazers on the source repository.
npm downloads16Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How MCPSpend works

What andreisirbu91-lab/MCPSpend MCP server does

andreisirbu91-lab/MCPSpend MCP server provides cost observability for MCP tool calls. Its proxy sits between an MCP client and the MCP servers configured for that client, records usage information, and sends the resulting telemetry to MCPSpend for dashboard reporting. The repository also includes a separate MCP server package for querying collected usage from an MCP client.

The reported data includes the tool name, MCP server name, model, latency, success status, and approximate input and output sizes. The proxy does not send actual tool arguments or response bodies to MCPSpend. Usage can be reviewed through the web dashboard, queried through MCP, or exported as CSV from the dashboard.

How it works

The proxy is distributed as @mcpspend/proxy on npm. Its initialization process can detect configurations for Claude Desktop, Cursor, Windsurf, VS Code user and workspace settings, and Claude Code user and project settings. It wraps each configured MCP server and creates a .mcpspend.bak backup of the relevant configuration.

Usage queries are available in two forms. A client can run @mcpspend/mcp-server over stdio, or connect to the HTTP MCP endpoint at https://api.mcpspend.com/api/mcp with a bearer token. The README gives get_today_cost and list_top_tools as examples of the available query tools. The dashboard provides an overview, top-tool reporting, session information, and CSV export.

Setup and configuration

The documented initialization command is:

Terminal
npx --yes @mcpspend/proxy@latest init --key mcps_live_xxx

The mcps_live_xxx value is an example key and must be replaced with a real MCPSpend key. Initialization starts streaming usage to mcpspend.com after wrapping the detected configurations. For direct HTTP MCP access, configure the client to use the documented endpoint and send the MCPSpend key as a bearer token.

The repository contains several published components: the proxy package, @mcpspend/mcp-server, and the mcpspend-vscode extension for Cursor, Windsurf, and VS Code. The proxy itself is MIT-licensed. The service has a free allowance of 25,000 tool calls per month without a credit card; paid plans add higher limits and features such as retention, exports, budget alerts, and role-based access.

Tools and capabilities

  • Wrap configured MCP servers through a local stdio observability proxy.
  • Attribute usage by tool and server, with project and end-customer attribution described by the listing.
  • Query usage from an MCP client using tools such as get_today_cost and list_top_tools.
  • Connect to the usage-query MCP server through stdio or the documented HTTP endpoint.
  • View costs, top tools, sessions, and CSV exports in the web dashboard.
  • Report metadata without transmitting tool arguments or response bodies.

Limitations and notes

andreisirbu91-lab/MCPSpend MCP server requires an MCPSpend key for initialization or authenticated HTTP access. The free plan is limited to 25,000 tool calls per month. The proxy reports approximate input and output sizes derived from JSON length rather than the complete payload contents.

Installing or configuring one does not, by itself, establish that every MCP client is supported; the documented detection list covers Claude Desktop, Cursor, Windsurf, VS Code, and Claude Code. Enterprise-specific items include a data processing agreement, while SOC 2 Type I is described as in progress rather than completed.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCPSpend

Run the documented npm initialization command, replacing its example key with a real MCPSpend key: `npx --yes @mcpspend/proxy@latest init --key mcps_live_xxx`.

Yes. The proxy can detect Claude Desktop configuration and wrap its configured MCP servers.

Its proxy records tool name, server name, model, latency, success, and approximate input and output sizes, then streams usage to the MCPSpend dashboard.

No.

It has a free tier covering 25,000 tool calls per month without a credit card, plus paid plans with higher limits.

Related MCP servers

All in Monitoring All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCPSpend AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/andreisirbu91-lab-mcpspend?style=directory)](https://allmcps.com/mcp/andreisirbu91-lab-mcpspend)
HTML Embed
<a href="https://allmcps.com/mcp/andreisirbu91-lab-mcpspend"><img src="https://allmcps.com/api/badge/andreisirbu91-lab-mcpspend?style=directory" alt="MCPSpend on AllMCPs" /></a>