A side-by-side look at the MCPSpend and AI Dev Analytics MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCPSpend for monitoring work as a local process; choose AI Dev Analytics for monitoring as a local process. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 56/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Freemium | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 75 | 8 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MCPSpend | View AI Dev Analytics |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"andreisirbu91-lab-mcpspend": {
"command": "npx",
"args": [
"--yes",
"@mcpspend/proxy@latest"
]
}
}
}
{
"mcpServers": {
"lwtlong-ai-dev-analytics": {
"command": "npx",
"args": [
"-y",
"aida"
]
}
}
}