ops-mcplisted

MCP server health dashboard and reconnect control. Surfaces the watchdog + keepalive + reauth subsystem as a discoverable slash command. Routes — status, servers, reconnect, reauth, logs, restart, test.
Lifecycle-Innovations-Limited/claude-ops · ★ 17 · AI & Automation · score 86

Install: claude install-skill Lifecycle-Innovations-Limited/claude-ops

# OPS ► MCP Surfaces the MCP auto-reconnect subsystem (watchdog + keepalive + reauth) as a discoverable slash command. These three scripts were previously orphaned — no plugin-level entry point. This skill is the entry point. For full architecture reference (state files, scripts, failure modes) see [`STATUS.md`](./STATUS.md). ## Runtime Context Before any route runs, resolve: 1. **State dir**: `$HOME/.claude/state/mcp-watchdog` — watchdog state, health, and logs. 2. **Keepalive state dir**: `$HOME/.claude/state/mcp-keepalive` — keepalive logs and health. 3. **Reauth state dir**: `$HOME/.claude/state/mcp-reauth` — reauth logs. 4. **Plugin root**: `${CLAUDE_PLUGIN_ROOT}` — used to invoke scripts. 5. **Claude config**: `$HOME/.claude.json` — source of truth for configured MCP servers. If the watchdog state dir does not exist, the watchdog has never run — surface a setup hint on the `status` route. ## Routing table Parse `$ARGUMENTS` and route immediately. First token decides the route. | First arg | Route | | ----------------------- | ----------------------------------------------------------------------------- | | (empty) / `status` | **Status dashboard** — watchdog health + per-server states + last tick | | `servers` | List all MCP servers from `~/.claude.json` with current state | | `reconnect [server]` | Manually trigger watchdog reconne