Mac Health MCP
Related Servers
Alternatives to Mac Health MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables an MCP client such as Claude to inspect a Mac's battery, memory, CPU, GPU, disk, and most energy-hungry apps, and to shut down, restart, sleep, or lock the screen now or on a schedule with a cancellable 60-second grace period.14-
- AlicenseNot gradedqualityCmaintenanceA remote MCP server that lets AI assistants such as Claude, ChatGPT, and any MCP client ask about a user's Apple Health data, with answers produced live by the user's iPhone via HealthKit. Health data is forwarded through process memory only — never written to disk — and covers sleep, workouts, metric series, health overviews, and user-defined custom metrics.AGPL 3.0
- AlicenseAqualityCmaintenanceProvides Claude with read-only access to PC diagnostics including hardware specs, live performance metrics, disk usage, network checks, and more, enabling natural language queries about PC health and performance.151MIT
- AlicenseBqualityBmaintenanceEnables MCP-aware AI agents to query the local machine's health over stdio, retrieving CPU, memory, disk, and load-average metrics along with boot time and the top processes by CPU usage. It gives coding agents a structured, protocol-standard way to answer questions like whether it is safe to run a build or what is currently consuming resources.21MIT
- AlicenseNot gradedqualityDmaintenanceDiagnose MCP servers — health checks, tool testing, token cost audits, conflict detection, and security scanning with 50+ prompt injection patterns. Works as CLI or MCP server inside Claude Desktop.1MIT
- AlicenseNot gradedqualityDmaintenanceLets MCP clients (Claude Code, Claude Desktop) inspect a Linux home server's health over the network: uptime, load, memory, disk, Docker containers, systemd services, journal errors, and listening ports. Read-only, bearer-token secured.MIT
TDQS
Scored across 8 tools
Several tools overlap: diagnose_slowness and get_mac_overview both answer 'why is my Mac slow' and include uptime, memory, disk, battery and thermal checks, creating real misselection risk. The component reports (memory_report, disk_report, battery_report, thermal_status, top_processes, startup_items) are more clearly scoped, but they also duplicate data exposed by the aggregate tools.
All names use snake_case, which is good, but the patterns are mixed: diagnose_slowness and get_mac_overview are verb_noun, while memory_report, disk_report, battery_report, thermal_status and startup_items are noun_noun, and top_processes has no clear verb convention. The set remains readable, but it does not follow one predictable naming scheme.
Eight tools is a well-scoped size for a Mac health diagnostics server. Each tool has a recognizable role: one ranked diagnosis, one overview, and six focused component inspections.
The surface covers the main health areas: slowness diagnosis, CPU/memory, disk, battery, thermal throttling, startup items and an overview. Minor gaps remain around network diagnostics, SMART/storage health, crash logs or macOS update status, but most common Mac health questions are supported.