Query your MCPSpend usage: cost today, top tools, recent sessions, budget projections.
MCPSpend (Model Context Protocol) Server
This MCP server lets you query MCPSpend usage, including cost today, top tools, and recent sessions, with budget projections. It tracks MCP tool calls across Cursor, Claude Desktop, Windsurf, and VS Code, using a Model Context Protocol-compatible setup.
🛠️ Key Features
Query cost today
List top tools
View recent sessions
Provide budget projections
Track MCP tool calls across Cursor, Claude Desktop, Windsurf, and VS Code
🚀 Use Cases
Checking real-time spend for AI agents using MCP tools
Identifying which tools contribute most to usage
Reviewing recent MCP sessions for cost monitoring
Planning future budget based on projections
⚡ Developer Benefits
Enables cost tracking by tool and session
Supports MCP-based workflows in multiple clients: Cursor, Claude Desktop, Windsurf, and VS Code
⚠️ Limitations
Only described as covering MCP tool-call cost tracking for the listed clients and the queried usage categories (cost today, top tools, recent sessions, projections)
Auto-detects Claude Desktop, Cursor, Windsurf, VS Code (user + workspace), and Claude Code (user + project). Wraps every configured MCP server, leaves a .mcpspend.bak backup, and starts streaming usage to your dashboard at mcpspend.com.
Free tier: 25,000 tool calls/month, no credit card.
Add @mcpspend/mcp-server to your client config — agent gains tools like get_today_cost, list_top_tools.
From any MCP client (HTTP)
Point your client at https://api.mcpspend.com/api/mcp with Authorization: Bearer mcps_live_….
Pricing
Plan
Calls/month
Monthly
Yearly
Free
25,000
$0
$0
Pro
1,000,000
$29
$290 (2 months free)
Team
10,000,000
$99
$990
Enterprise
unlimited
$499
$4,990
Every paid plan: 30–90 day retention, CSV/Slack export, budget alerts, role-based access.
Privacy
The proxy reports: tool name, server name, model, latency, success, approximate input/output sizes (tokens, derived from JSON length). It does not send the actual tool arguments or response bodies to MCPSpend. See Privacy Policy for the full sub-processor list (Stripe + Resend + Hostinger, all EU-hosted) and your GDPR rights.
Security
For automated scanners flagging this repo: the proxy uses child_process.spawn to wrap the user's own MCP server — that's the whole point of an observability proxy. The spawn args come from the user's local MCP-client config (Claude Desktop / Cursor / Windsurf / VS Code), never from network input. No RCE path, no privilege escalation, no arbitrary command execution. Full threat model in SECURITY.md.
API keys stored as SHA-256 hashes (never plaintext on the server)
Passwords bcrypt cost 12
Secrets at rest AES-256-GCM (APP_ENCRYPTION_KEY)
Transport HTTPS only, HSTS enabled, helmet CSP headers
No tool arguments or responses ever leave the user's machine
Per-tenant isolation every query scopes by organizationId
GDPR Art. 15 / 17 / 20 self-serve at mcpspend.com/dashboard/account/privacy
If MCPSpend saves you money or you just want to keep the proxy MIT and the free
tier alive, you can sponsor any amount via Stripe — no account required:
Your MCPSpend API key. Create one at https://mcpspend.com/dashboard/keys. Starts with mcps_live_ or mcps_test_. Optional — the server boots and lists tools without it; only tool calls require auth.
MCPSPEND_ENDPOINTdefault https://api.mcpspend.com
Optional. Override the MCPSpend API endpoint. Defaults to https://api.mcpspend.com. Use only if you self-host MCPSpend.
