Agent Chain Doctor MCP vs MCPSpend
A side-by-side look at the Agent Chain Doctor MCP and MCPSpend MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agent Chain Doctor MCP for monitoring work; choose MCPSpend for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Agent Chain Doctor MCP when
- You need dedicated capabilities in the Monitoring domain.
- Its auth model fits you: No auth required.
Choose MCPSpend when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 32/100 · Emerging | 56/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Freemium |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 75 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Agent Chain Doctor MCP | View MCPSpend |
Tools & capabilities
Agent Chain Doctor MCP tools
No tool names declared yet. Check the project README from the listing page.
MCPSpend tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
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.
Agent Chain Doctor MCP
No confirmed install command for Agent Chain Doctor MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
MCPSpend
{
"mcpServers": {
"andreisirbu91-lab-mcpspend": {
"command": "npx",
"args": [
"--yes",
"@mcpspend/proxy@latest"
]
}
}
}
Frequently asked questions
Agent Chain Doctor MCP is categorized under Monitoring and uses an install path we have not confirmed yet. MCPSpend belongs to Monitoring and uses a local stdio subprocess. Pick Agent Chain Doctor MCP for monitoring work and MCPSpend for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Agent Chain Doctor MCP has no confirmed install command yet — follow its own setup instructions.
Agent Chain Doctor MCP is listed as free. Auth: no auth required. MCPSpend is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add agent-chain-doctor-mcp and andreisirbu91-lab-mcpspend as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Chain Doctor MCP has a quality signal of 32/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. MCPSpend has 56/100 (Good) with 3 views, 0 installs and 75 GitHub stars.