Use SoloNOC with your AI agent

SoloNOC exposes the same jobs through an MCP server, a documented REST API, and a zero-dependency CLI, so an agent can check your sites, triage alerts and pull device history without a human driving the dashboard. All three require an API key (Settings → Agent access, Pro plan or above) and never grant more than the web app does. Billing, account deletion, SSO configuration and remediation execution are never reachable from any of these surfaces.

Get an API key

Create one in Settings → Agent access. The raw key is shown once — store it somewhere a password manager can reach. Each key is scoped read or read+write and can be revoked at any time.

MCP server (Claude Code, claude.ai, Cursor)

A Streamable HTTP MCP endpoint at:

https://api.solonoc.com/mcp

Claude Code

claude mcp add --transport http solonoc https://api.solonoc.com/mcp \
  --header "Authorization: Bearer ${SOLONOC_API_KEY}"

claude.ai / Claude Desktop

Settings → Connectors → Add custom connector → paste the URL above, then add a fixed request header Authorization: Bearer YOUR_KEY.

Cursor

{
  "mcpServers": {
    "solonoc": {
      "url": "https://api.solonoc.com/mcp",
      "headers": { "Authorization": "Bearer ${env:SOLONOC_API_KEY}" }
    }
  }
}

ChatGPT / Codex

codex mcp add solonoc --url https://api.solonoc.com/mcp

Tools: list_sites, list_devices, list_alerts, acknowledge_alert, resolve_alert, get_device_metrics, request_discovery, list_config_backups, get_config_diff. The three that change state (acknowledge_alert, resolve_alert, request_discovery) describe what they would do when called without confirm: true, and only act on a second call that includes it.

REST API + OpenAPI

The same jobs as plain JSON over HTTPS, documented as an OpenAPI 3.1 document at:

https://api.solonoc.com/openapi.json

curl -H "Authorization: Bearer $SOLONOC_API_KEY" \
  https://api.solonoc.com/api/v1/sites

The legacy X-API-Key header also works. See the full REST API reference for every endpoint.

CLI

Zero-dependency npm package, same jobs as the MCP tools:

npx solonoc login $SOLONOC_API_KEY
npx solonoc sites list
npx solonoc alerts list --status firing
npx solonoc alerts ack <alert-id> --yes

Every command accepts --json. A command that changes data (alerts ack, alerts resolve, discover) refuses to run without --yes.

What agents cannot do

Billing and subscription changes, account deletion, SSO configuration, and triggering a remediation action are never exposed to an MCP tool, a REST endpoint in the agent document, or a CLI command — those stay human-only, in the dashboard.