Bring Sifflet data observability into Cursor. This plugin connects agents to Sifflet through the official MCP server and adds guidance for writing Monitors as Code.
This plugin is provided as-is and is not an officially supported Sifflet product.
- Sifflet MCP for catalog, monitor, incident, and lineage discovery from Agent chat.
- Quality as Code skills for drafting and reviewing
workspace.yamland monitor YAML. - Rules and commands that keep monitor changes reviewable before they are applied.
- A Sifflet account and API token.
- Cursor with plugin and MCP support.
uvavailable on your PATH so Cursor can runuvx sifflet-mcp.- The Sifflet CLI if you want to run
sifflet code workspace planorapply.
Install Sifflet from Cursor's plugin marketplace.
Install the plugin, then authenticate Sifflet once:
sifflet configureReload Cursor, enable the sifflet MCP server in Cursor settings, then ask Agent chat a Sifflet question:
Find datasets related to customer orders in Sifflet.
Catalog and lineage:
Search Sifflet for the orders dataset and show its downstream assets.
Which monitors are attached to this dataset?
Monitors as Code:
Create a Sifflet monitor YAML for freshness on this table.
Review this workspace.yaml before I run a plan.
Run a dry-run plan for quality/workspace.yaml and summarize the changes.
The plugin registers the sifflet MCP server through mcp.json. It starts run-sifflet-mcp.sh, which launches sifflet-mcp with uvx.
sifflet-mcp- explore catalog assets, monitors, incidents, and lineage before changing data or YAML.sifflet-quality-as-code- draft and refine Sifflet monitor and workspace YAML using MCP context and the Monitors as Code schema.
sifflet-mac-yaml- conventions for safe Monitors as Code YAML changes.
configure-sifflet-auth- help configure Sifflet authentication.mac-plan-workspace- run and review a dry-run plan.mac-apply-workspace- apply a reviewed workspace change.
Use MCP for discovery and the Sifflet CLI for workspace changes:
sifflet code workspace plan --file workspace.yaml
sifflet code workspace apply --file workspace.yamlRun sifflet configure before using Monitors as Code commands.
If MCP tools do not appear, reload Cursor and confirm the sifflet MCP server is enabled in settings.
If authentication fails, run sifflet configure again, then reload Cursor.
If uvx is missing, install uv and restart Cursor.
Publish from a dedicated public repository or generated mirror that contains only this plugin tree. The manifest keeps logo as assets/logo.svg so the Cursor Marketplace can resolve it after publication.