CLI & MCP Server

Daemon Watchdog includes a command-line tool and an MCP server for AI agents. Both connect to the running app — Daemon Watchdog must be open in your menu bar.

CLI and MCP access requires an active trial or valid license.

CLI Setup

The CLI ships inside the app. Run it directly:

"/Applications/DaemonWatchdog.app/Contents/MacOS/sdw" status

Or create a symlink so you can use sdw from anywhere:

ln -s "/Applications/DaemonWatchdog.app/Contents/MacOS/sdw" /usr/local/bin/sdw

Commands

Check all daemons:

sdw status

JSON output (for scripting):

sdw status --json

View 24-hour memory history:

sdw health corespotlightd

Restart a leaking daemon:

sdw restart corespotlightd

Clear auto-restart suppression:

sdw resume corespotlightd

App version and license info:

sdw version

All restart requests go through the same safety checks as the app — cooldowns, backup detection, frequency caps, and WindowServer protection.

MCP Server Setup

The MCP server lets AI agents like Claude monitor your daemons and request restarts through natural language.

Claude Desktop

1. Open your config file:

~/Library/Application Support/Claude/claude_desktop_config.json

2. Add the Daemon Watchdog server:

{
  "mcpServers": {
    "sdw": {
      "command": "/Applications/DaemonWatchdog.app/Contents/MacOS/sdw-mcp"
    }
  }
}

3. Restart Claude Desktop.

Claude Code

Add to your MCP configuration:

{
  "mcpServers": {
    "sdw": {
      "command": "/Applications/DaemonWatchdog.app/Contents/MacOS/sdw-mcp"
    }
  }
}

Cursor

Add to your Cursor MCP settings with the same configuration block above.

What you can ask

Once configured, try:

Available tools

Tool Description
get_daemon_status Current status of all monitored daemons
get_daemon_health 24-hour memory history for a specific daemon
restart_daemon Request a daemon restart (safety checks apply)
resume_daemon Clear auto-restart suppression
get_version App version, license status, system info

Frequently Asked Questions

Do I need an API key?

No. The MCP server runs locally and connects to the app via a Unix socket on your Mac. No API keys, no network connections, no data sent externally.

Can an AI agent bypass the safety checks?

No. All restart requests from CLI and MCP go through the same safety pipeline as the app. WindowServer restarts are refused, backupd checks for active Time Machine backups, and cooldowns and frequency caps are enforced.

Why does the CLI say "Cannot connect"?

Daemon Watchdog must be running in the menu bar. The CLI and MCP server communicate with the app via a local socket that only exists while the app is open.

Why does the CLI say "Trial expired"?

CLI and MCP access requires an active trial or valid license. After the 14-day trial, open Daemon Watchdog and enter your license key. The app continues monitoring without a license, but CLI and MCP access stops.

Does the MCP server work with other AI tools?

The MCP server follows the Model Context Protocol standard and works with any MCP-compatible client. It communicates via JSON-RPC over stdio.