quietwatcher-mcp 0.1.0

MCP server for QuietWatcher — manage cloud monitors from any AI client.

QuietWatcher MCP server

Manage your QuietWatcher cloud monitors from any MCP-capable AI client (Claude Desktop, Claude Code, etc.). The server wraps the public REST API (api.quietwatcher.com) and authenticates with a customer API key.

Get an API key

In the QuietWatcher app: Account → API keys → New key. Copy the qwk_… value (shown once).

Tools

Tool	What it does
get_subscription	Your plan + subscription status
list_monitors	All cloud monitors on the account
get_monitor(monitor_id)	One monitor
create_monitor(name, target, type="http", interval_seconds=60)	Add a monitor
delete_monitor(monitor_id)	Remove a monitor
get_results(monitor_id, since=None)	Recent check results
export_config()	Back up every monitor as a portable JSON blob
import_config(monitors)	Restore/clone a config (preserves ids → idempotent re-import)
export_results_csv(monitor_id, since=None)	Download a monitor's readings as CSV

All actions are scoped to the API key's account. export_config / import_config round-trip with the quietwatcher export / import CLI commands.

Run it

QW_API_KEY=qwk_… uvx quietwatcher-mcp
# or, from this directory:
QW_API_KEY=qwk_… uv run quietwatcher-mcp
# or:
pip install -e . && QW_API_KEY=qwk_… python -m quietwatcher_mcp

Env:

• QW_API_KEY (required) — your qwk_… key.
• QW_API_BASE (optional) — defaults to https://api.quietwatcher.com.

Claude Desktop config

{
  "mcpServers": {
    "quietwatcher": {
      "command": "uvx",
      "args": ["quietwatcher-mcp"],
      "env": { "QW_API_KEY": "qwk_…" }
    }
  }
}

Notes

• The same key works for any HTTP client (Authorization: Bearer qwk_… or X-API-Key: qwk_…) — the MCP server is just a thin, AI-friendly wrapper.
• The full REST API is documented at https://api.quietwatcher.com/api/v1/docs/ (OpenAPI), so AI agents can also discover endpoints directly.