Agent Chain Doctor MCP vs GPU MCP Server
A side-by-side look at the Agent Chain Doctor MCP and GPU MCP Server 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 GPU MCP Server for monitoring over a hosted endpoint. 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 GPU MCP Server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
list_gpus, get_gpu_metrics, get_gpu_processes.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 32/100 · Emerging | 53/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 15 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View Agent Chain Doctor MCP | View GPU MCP Server |
Tools & capabilities
Agent Chain Doctor MCP tools
No tool names declared yet. Check the project README from the listing page.
GPU MCP Server tools 4
list_gpusList all GPUs with utilization and memory infoget_gpu_metricsDetailed metrics for a GPU by index or UUIDget_gpu_processesPID-level GPU process attributiongpu_summaryAggregate stats across all devices
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.
GPU MCP Server
{
"mcpServers": {
"gpu-mcp-server": {
"url": "https://api.star-history.com/chart?repos=pmady/gpu-mcp-server&type=date&theme=dark&legend=top-left"
}
}
}
Frequently asked questions
Agent Chain Doctor MCP is categorized under Monitoring and uses an install path we have not confirmed yet. GPU MCP Server belongs to Monitoring and uses a remote HTTP/SSE transport. Pick Agent Chain Doctor MCP for monitoring work and GPU MCP Server 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. GPU MCP Server has no declared pricing — check the project's own site. 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 gpu-mcp-server 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. GPU MCP Server has 53/100 (Good) with 0 views, 0 installs and 15 GitHub stars.