open-monitor
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@open-monitorcheck health of all machines"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
open-monitor
System monitor for AI agents and humans — watch multiple machines, detect problems, take action.
Features
🖥️ Multi-machine — monitor local, SSH, and EC2 machines from one place
📊 Metrics — CPU, memory, disk, GPU, load average, uptime, processes
🤖 MCP server — AI agents can query health, kill processes, manage cron jobs, and run doctor checks
🔍 Doctor — built-in health checks with actionable diagnostics and auto-remediation
💀 Process manager — detect zombies and orphans, smart kill policy with signal selection and safe list
📦 Container monitoring — inspect Docker/Podman/Nerdctl containers, resource usage, and logs
🚪 Port scanner — see which TCP/UDP ports are listening on one machine or across the fleet
🔄 Cron jobs — schedule actions per machine with full cron syntax
📨 Fleet reports — generate daily/weekly health summaries and deliver them via open-conversations or open-emails
🌐 Web dashboard — dark-themed real-time gauges served at
http://localhost:3848(like NVIDIA DGX Dashboard)🔎 Full-text search — search across machines, alerts, and processes
🔗 Integrations — open-todos, open-conversations, open-mementos, open-emails
💾 SQLite by default — zero-config persistence; optional PostgreSQL for production
🐚 Shell completions — zsh and bash completions included
Related MCP server: allcanuse-mcp
Install
bun install -g @hasna/monitorOr with npm:
npm install -g @hasna/monitorPublished entrypoints
After a global install, @hasna/monitor exposes four npm binaries:
Binary | Description |
| Main CLI for machines, metrics, doctor, cron, and integrations |
| MCP server for AI agents (stdio or HTTP) |
| Standalone REST API server (default port |
| Standalone Vite web dashboard dev server (default port |
Start the API and dashboard separately:
monitor-server
# REST API: http://localhost:3847
monitor-web
# Dashboard: http://localhost:3848Or start the API through the main CLI:
monitor serve --port 3847Override standalone bin ports with PORT, for example PORT=9000 monitor-web.
Quick Start
# Check local machine
monitor status
# Add a remote SSH machine
monitor add linux-node-a --type ssh --host linux-node-a.example.com --user ubuntu --key ~/.ssh/id_ed25519
# Show all machines
monitor machines
# Run health checks
monitor doctor
# List processes, filter for zombies
monitor ps --filter zombies
# Search across everything
monitor search "high cpu"
# Start the web dashboard
monitor-webMCP Setup
# Claude Code (recommended)
claude mcp add --scope user monitor -- monitor-mcp
# Or manually add to ~/.claude.json mcpServers:
# "monitor": { "type": "stdio", "command": "monitor-mcp", "args": [] }
# Codex — add to ~/.codex/config.toml:
# [mcp_servers.monitor]
# command = "monitor-mcp"HTTP mode
Run a shared Streamable HTTP MCP server (stateless, 127.0.0.1 only):
monitor-mcp --http
# or: MCP_HTTP=1 monitor-mcp
# default port: 8826 (override with --port or MCP_HTTP_PORT)Endpoints: GET /health, POST /mcp (Streamable HTTP).
Available MCP Tools
Tool | Description |
| Get current metrics snapshot (CPU, memory, disk, GPU) |
| Run health checks and return pass/warn/fail status |
| List running processes with optional filters |
| List installed apps/packages or compare inventories across machines |
| List or control system services and detected dev servers |
| List containers and resource usage on one or all machines |
| Fetch recent logs for one container |
| List listening TCP/UDP ports on one or all machines |
| Show Tailscale peer status, IPs, health, and latency |
| Show CPU/GPU temperatures, fan speeds, and thermal alerts |
| Check Claude MCP registration health and dead tmux panes |
| Show MCP server health with best-effort matched process details |
| Restart a matched MCP process and re-check health |
| Kill a process by PID with configurable signal |
| List all configured machines |
| Add a new machine to monitor |
| List recent alerts for a machine |
| List scheduled cron jobs |
| Run the doctor and get remediation suggestions |
| Full-text search across machines, alerts, processes |
| Register an AI agent for heartbeat tracking |
| Send a heartbeat to indicate agent is alive |
| Set current focus/task for an agent |
| List all registered agents and their status |
| Update integration settings |
| Submit feedback |
CLI Reference
monitor <command> [options]Command | Description |
| Show current system snapshot (CPU, memory, disk, GPU) |
| List all configured machines |
| Add a machine to monitor |
| Run health checks with diagnostics |
| List processes, with optional filter |
| Kill a process by PID |
| Show recent alerts |
| List installed apps/packages or compare them across machines |
| Compare installed apps across all configured machines |
| List or control system services and detected dev servers |
| Show containers and resource usage |
| Show listening TCP/UDP ports |
| Show Tailscale peer status, IPs, health, and latency |
| Show CPU/GPU temperatures, fan speeds, and thermal alerts |
| Check Claude MCP registration health and dead tmux panes |
| Show MCP health plus best-effort matched process PIDs, memory, and uptime |
| Restart a matched MCP process if one is running, then re-check health |
| Build a daily fleet health report |
| Deliver the current report via configured integrations |
`report --schedule daily | weekly` |
| List scheduled cron jobs |
| Add a cron job |
| Run a cron job immediately |
| Full-text search |
| Run database migrations |
| List integration status |
| Test an integration |
| Start the API server |
| Start the MCP server (stdio) |
| Push metrics to remote store |
| Pull metrics from remote store |
| Show sync status |
| Print zsh completions |
| Print bash completions |
| Auto-install shell completions |
mcp-status and monitor_mcp_status use live process snapshots, so stdio servers can report connected with processCount: 0 when no long-lived child is present at the instant of collection.
monitor add
# Local machine (default)
monitor add mybox
# SSH machine
monitor add linux-node-a \
--type ssh \
--host linux-node-a.example.com \
--user ubuntu \
--key ~/.ssh/id_ed25519 \
--port 22
# EC2 machine (uses AWS SSM)
monitor add prod-api \
--type ec2 \
--instance-id i-0abc123def456789 \
--region us-east-1 \
--profile my-aws-profilemonitor ps
monitor ps # all processes
monitor ps --filter zombies # zombie processes only
monitor ps --filter orphans # orphan processes
monitor ps --limit 20 # top 20 by CPU
monitor ps --json # raw JSON outputmonitor kill
monitor kill 1234 # SIGTERM (default)
monitor kill 1234 --signal SIGKILL
monitor kill 1234 --signal 9monitor apps
monitor apps # local package/app inventory
monitor apps macos-node-b # one remote machine
monitor apps --all # inventories for all configured machines
monitor apps --compare # highlight missing/version-skewed/root-owned installs
monitor compare-apps # dedicated cross-machine consistency report
monitor apps --jsonmonitor service
monitor service list # show system services plus detected dev servers
monitor service list --machine macos-node-b # inspect one remote machine
monitor service start postgresql # systemd / brew / launchctl start
monitor service restart nginx # systemd / brew / launchctl restart
monitor service stop vite:12345 # stop a detected dev server by PID-backed name
monitor service list --jsonmonitor temperature
monitor temperature # local thermal snapshot
monitor temperature linux-node-a # one remote machine
monitor temperature --all # inspect all configured machines
monitor temperature --jsonmonitor containers
monitor containers # local container list
monitor containers linux-node-a # remote machine containers
monitor containers --all # all configured machines
monitor containers --logs api # recent logs for one container
monitor containers --logs api --tail 200
monitor containers --jsonmonitor ports
monitor ports # local listeners
monitor ports linux-node-a # one remote machine
monitor ports --all # scan all configured machines
monitor ports --protocol tcp # filter by protocol
monitor ports --json # raw JSON outputmonitor loop-check
Loop-ready deterministic checks emit compact heartbeats, bounded evidence, and
deduped task seeds without dispatching tmux prompts. Add --upsert-tasks with
an explicit --todos-project when a loop should create missing remediation
tasks directly.
monitor loop-check listening-ports local
monitor loop-check workspace-ports --workspace /home/hasna/workspace
monitor loop-check process-hygiene local
monitor loop-check quarantine-retention --apply --max-gb 100 --target-gb 80
monitor loop-check workspace-ports \
--upsert-tasks \
--todos-project /home/hasna/.hasna/loops \
--max-task-actions 20monitor tailscale
monitor tailscale # local Tailscale graph
monitor tailscale linux-node-a # one remote machine
monitor tailscale --all # inspect all configured machines
monitor tailscale --json # raw JSON outputmonitor report
monitor report # preview daily fleet report
monitor report --period weekly # preview weekly fleet report
monitor report --send # send via configured conversations/emails integrations
monitor report --schedule daily # create/update a 9:00 daily cron report
monitor report --schedule weekly # create/update a Monday 9:00 weekly cron report
monitor report --allow-live-cloud-polling # include EC2/cloud machines only after explicit approvalCloud runtime diagnostics
monitor health, monitor doctor, and monitor report include metadata-only
cloud runtime diagnostics. These checks make the runtime boundary explicit:
Local SQLite and local config files are always the default runtime store.
MONITOR_DATABASE_URLswitches package storage/sync diagnostics to remote Postgres/RDS metadata, but status output never prints the URL, host, user, or password.S3/object-store diagnostics are enabled by configuration environment names such as
MONITOR_S3_BUCKET,MONITOR_S3_PREFIX, orMONITOR_OBJECT_STORE_BUCKET; reports show aggregate readiness only.EC2 machine configs remain on-demand/read-only through CloudWatch/SSM collectors when a machine is explicitly inspected.
ECS and RDS health are modeled through provider-injected read-only observations. The default CLI path does not poll live AWS accounts, mutate AWS resources, create secrets, deploy services, run Terraform, or increase spend.
Cloud diagnostics are safe for task loops and reports because they expose only configured/observed counts, statuses, and threshold percentages. Cloud identifiers such as bucket names, ARNs, hostnames, private paths, and credential values are intentionally excluded.
Web Dashboard
monitor-web
# Opens: http://localhost:3848The dashboard shows:
Real-time CPU, memory, and disk gauges per machine
Recent alerts with severity indicators
Process table with sort and filter
Doctor check results
Cron job schedule
Default port is 3848. Override it with PORT=9000 monitor-web.
Configuration
Config is stored at ~/.hasna/monitor/config.json. Set MONITOR_CONFIG_DIR
to use a different config/database directory for CI, tests, or isolated agent
runs.
{
"machines": [
{
"id": "local",
"label": "Local Machine",
"type": "local",
"pollIntervalSecs": 30,
"tags": ["dev"]
},
{
"id": "linux-node-a",
"label": "Spark Node 01",
"type": "ssh",
"ssh": {
"host": "linux-node-a.example.com",
"port": 22,
"username": "ubuntu",
"privateKeyPath": "~/.ssh/id_ed25519"
},
"pollIntervalSecs": 60,
"tags": ["production", "spark"]
},
{
"id": "prod-api",
"label": "Prod API Server",
"type": "ec2",
"ec2": {
"instanceId": "i-0abc123def456789",
"region": "us-east-1",
"profile": "my-aws-profile"
}
}
],
"thresholds": {
"cpuPercent": 90,
"memPercent": 90,
"diskPercent": 85,
"loadAvg": 10
},
"dbPath": "~/.hasna/monitor/monitor.db",
"apiPort": 3847,
"webPort": 3848,
"integrations": {
"todos": {
"enabled": true,
"project_id": "my-project-id"
},
"conversations": {
"enabled": true,
"space_id": "my-space-id"
},
"emails": {
"enabled": true,
"to": "alerts@example.com"
}
}
}Alert Thresholds
Field | Default | Description |
| 90 | Alert when CPU exceeds this % |
| 90 | Alert when memory exceeds this % |
| 85 | Alert when any disk exceeds this % |
| 10 | Alert when 1-min load average exceeds this |
Integrations
open-monitor integrates with the open-* ecosystem to surface alerts where you're already working.
open-todos
Creates tasks when critical alerts fire.
"todos": {
"enabled": true,
"project_id": "your-project-id",
"base_url": "http://localhost:3000"
}open-conversations
Posts alerts to a team space.
"conversations": {
"enabled": true,
"space_id": "your-space-id",
"base_url": "http://localhost:3001"
}open-mementos
Stores alert history as memories for AI agent context.
"mementos": {
"enabled": true,
"base_url": "http://localhost:3002"
}open-emails
Sends email notifications for critical alerts.
"emails": {
"enabled": true,
"to": "alerts@example.com",
"from": "monitor@yourdomain.com",
"base_url": "http://localhost:3003"
}Test any integration:
monitor integrations test todos
monitor integrations test conversations
monitor integrations test emailsShell Completions
# Install automatically (detects your shell)
monitor completions install
# Or manually:
monitor completions zsh >> ~/.zshrc
monitor completions bash >> ~/.bashrcDatabase
By default uses SQLite at ~/.hasna/monitor/monitor.db. For production or multi-agent setups, use PostgreSQL:
Set MONITOR_DATABASE_URL environment variable:
export MONITOR_DATABASE_URL="postgres://monitor-db.example.internal:5432/monitor"
monitor migrateSecurity
The REST API binds to
127.0.0.1by default. Usemonitor serve --host 0.0.0.0orHASNA_MONITOR_API_HOST=0.0.0.0only behind a trusted network or reverse proxy.Mutating and diagnostic command REST routes require
Authorization: Bearer <token>orX-API-Key: <token>. SetHASNA_MONITOR_API_TOKENorMONITOR_API_TOKENbefore using API routes that create/delete machines, run doctor diagnostics, kill processes, create cron jobs, or run cron jobs. The dashboard sendsVITE_MONITOR_API_TOKENor a browserlocalStoragevalue namedmonitor.apiTokenwhen present.CORS is restricted to exact trusted origins. Local dashboard origins are allowed by default; add comma-separated origins with
HASNA_MONITOR_API_CORS_ORIGINSorMONITOR_API_CORS_ORIGINS.Process command lines are automatically redacted before being returned to AI agents — passwords, tokens, API keys, and secrets are replaced with
***See SECURITY.md for the security policy and responsible disclosure process
License
Apache-2.0 — see LICENSE for details.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/hasna/monitor'
If you have feedback or need assistance with the MCP directory API, please join our Discord server