MCP and connected tools

Connect a client

ZnowPulse exposes monitoring tools at https://znowpulse.com/api/mcp using stateless Streamable HTTP. Use a client that supports remote HTTP MCP servers and bearer authentication. The same organization API tokens and permissions apply as in the REST API.

Create a token in Settings → API access with the scopes the client actually needs. For read-only investigation, start with monitors:read, checks:read, and incidents:read; add Nexus or maintenance read scopes only if required. Keep write scopes separate from observation-only access.

The exact configuration format depends on your client. For clients using this format, replace the placeholder locally or supply it through the client's secret store:

{
  "mcpServers": {
    "znowpulse": {
      "type": "http",
      "url": "https://znowpulse.com/api/mcp",
      "headers": {
        "Authorization": "Bearer znp_live_YOUR_TOKEN"
      }
    }
  }
}

Do not commit the completed configuration. Start by listing monitors and confirm the expected organization before enabling writes.

Available tools

Tool	Scope	Operation
list_monitors	monitors:read	List with optional limit and cursor.
get_monitor	monitors:read	Inspect by monitor_id.
create_monitor	monitors:write	Create; editor or higher.
update_monitor	monitors:write	Edit by monitor_id; editor or higher.
delete_monitor	monitors:write	Permanently delete; editor or higher.
list_checks	checks:read	Recent checks by monitor_id, optional limit.
list_incidents	incidents:read	Optional monitor_id, status, and limit filters.
list_maintenance	maintenance:read	List windows.
create_maintenance	maintenance:write	Create a one-time window; editor or higher.
list_regions	monitors:read	Discover monitoring locations.
list_oncall_alerts	on_call:read	List alerts; Pro.
acknowledge_oncall_alert	on_call:write	Acknowledge by alert_id; editor or higher, Pro.
list_nexus_points	nexus_points:read	List aggregate views.
get_nexus_point	nexus_points:read	Inspect by nexus_id.
create_nexus_point	nexus_points:write	Create an aggregate view.
update_nexus_point	nexus_points:write	Update name, description, and conditions.
delete_nexus_point	nexus_points:write	Delete an aggregate view.

Monitor and maintenance tool inputs follow the corresponding API field names. Discover each tool's input schema through your client. Nexus Point writes still enforce organization permissions and plan quota. MCP does not expose every REST operation: incident creation/update and on-call schedule/policy creation are not in this tool list.

The MCP list_regions tool uses monitors:read; the REST /regions endpoint uses regions:read.

Transport and errors

Only POST is supported. GET streaming and DELETE session termination return 405 because the server does not retain MCP sessions. Responses use JSON rather than a long-lived server event stream.

Missing or invalid bearer authentication returns an HTTP 401 JSON error. Tool-level errors can return HTTP 200 with isError: true and an error object inside text content. Always inspect the tool result. Requests are subject to shared API rate limiting and can receive 429 before MCP processing.

Revoke access

Revoke the token in API access when disconnecting a client or responding to an exposed credential. Removing a client configuration alone does not revoke the token. Review requested actions before allowing an automation client to delete monitors or change alert coverage.

ZenSailor integration

ZnowPulse also supports an authenticated device-approval flow for ZenSailor. Start the connection from the integrating application, sign in to the intended ZnowPulse organization, and review the requested approval. Do not approve a device request you did not initiate. Use organization API access controls to review and revoke related access when needed.