Managing Saved Views

Create, read, update, and delete SigNoz saved Explorer views via the SigNoz MCP server. A saved view is a reusable snapshot of an Explorer query on the Logs, Traces, Metrics, or Cost Meter page: name + filters + panel type, scoped to one source. They are not dashboards and not alerts.

The tools call the v2 /api/v2/saved_views API. The create/update payloads are the typed v2 shape (source + spec), not the retired v1 compositeQuery/category/tags/extraData shape; the sourcePage parameter was renamed to source.

This skill covers the full CRUD surface in one place because the operations share the same schema, the same identity model (UUID per view), and the same prerequisite resources. The only operation with real blast radius is delete, and update has a sharp edge (full-body replace); both get explicit guards below.

Prerequisites