mcp-local-telemetry
Related Servers
Alternatives to mcp-local-telemetry
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceMulti-machine system monitor with a built-in MCP server that enables AI agents to query health metrics, manage processes, schedule cron jobs, and run diagnostics across local and remote machines.133 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceA real-time system diagnostics MCP server that gives AI agents live access to CPU, RAM, disk, network, processes, and hardware health metrics, with zero cloud dependency.7Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to monitor real-time CPU, RAM, and disk usage on the local machine.-
- FlicenseNot gradedqualityBmaintenanceEnables MCP-compatible clients to inspect the local machine's CPU, memory, and disk information through tools, a structured resource, and an upgrade-assessment prompt.-
- AlicenseBqualityCmaintenanceEnables MCP-compatible AI assistants to inspect and manage local or remote servers in plain language, covering system health, Docker containers, services, ports, disks, scoped files, and read-only database queries over key-only SSH. Write actions such as container restarts, file edits, and allowlisted dev commands require client approval.14MIT
- AlicenseAqualityBmaintenanceA lightweight MCP server that enables AI assistants to execute local development tools and retrieve system status with low latency over stdio or HTTP.129 npm3MIT
TDQS
Scored across 2 tools
get_system_metrics returns aggregate machine-level stats while get_top_processes returns per-process ranking, so their purposes are clearly distinct. An agent can trivially choose between them with no overlap.
Both tools follow a consistent get_<noun> snake_case verb_noun pattern. Naming is predictable and idiomatic throughout.
Two tools is on the thin side for a telemetry server; while each earns its place, the surface feels minimal and could reasonably include a couple more monitoring dimensions without bloat.
Core CPU/RAM/Disk and top-CPU-process coverage exists, but network I/O, memory-heavy process ranking, disk I/O, and any historical/sampling data are missing. Agents can perform basic pre-flight checks but hit dead ends for richer diagnostics.