Skip to main content
Glama
Go-Business-Inc

MCP Mac Monitor

by Go-Business-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to MCP Mac Monitor

No user-submitted related servers found.

    Related Servers

    • macos-control-mcp

      vito1317
      A
      license
      B
      quality
      D
      maintenance
      MCP server that enables AI to fully control macOS — mouse, keyboard, terminal, screenshots, window management, UI element detection, and provides AI-optimized information reporting.
      36
      21 npm
      MIT

    • computer-use

      taotao135791-bit
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a JSON-RPC computer use runtime for macOS, exposing 7 MCP tools (observe/act/inspect/session/cancel/trace) as image content blocks so external agents like Claude Code, Pi, OpenCode, or Codex CLI can capture screenshots and drive the desktop with clicks, keys, and typing while enforcing session locking, stale-frame protection, and trace redaction server-side.
      12 npm
      1
      MIT

    • Actvt

      oye-collective
      A
      license
      Not graded
      quality
      C
      maintenance
      Actvt's embedded MCP server for macOS. 25 tools for live CPU, GPU, memory and network metrics, listening ports with a guarded port_kill, and Claude Code and Codex session analytics (cost, tokens, transcript search, error patterns). It ships inside the Actvt macOS app and binds to loopback on the user's machine, so it starts with the app, not as a standalone or containerised process.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools target a distinct metric or action, but get_snapshot overlaps with the individual get_* monitoring calls, and get_top_processes/get_energy both report process-level usage. The descriptions clarify their intended use, so ambiguity remains limited.

    Naming Consistency5/5

    Read operations consistently follow the get_<noun> pattern, while power actions use simple imperative verbs like shutdown, restart, sleep, and lock_screen. Everything uses lowercase snake_case, making the set highly predictable.

    Tool Count5/5

    With 14 tools, the server is well-scoped: approximately nine monitoring read tools, four power/lock controls, and one pair for checking/canceling scheduled actions. Each tool earns its place without redundancy.

    Completeness5/5

    The tool surface fully covers the stated domain: battery, memory, CPU, disk, system info, processes, energy usage, and a complete power-control lifecycle including scheduling and cancellation. No obvious dead ends or missing core operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources