MCPSpend

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:

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.

The README describes the proxy and usage-query server as separate packages. 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.