datawatch
Provides tools for working with Snowflake data assets in the data-observability platform, including listing Snowflake-sourced assets and creating Snowflake assets for monitoring.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
datawatch
datawatch talks to a data-observability platform's API: platform health and a daily briefing, alerts (summaries, inbox, trends, history and rules), the data assets under observation and their discovery, freshness summaries, checks and schedules, and schema summaries, change lists, baselines and monitoring. One binary serves a command-line interface and a stdio MCP server.
An API key is required. Set ARMOR_API_KEY before use; when it
is missing or blank, every tool fails with an error naming the
variable before any request is made. The API base URL can be
overridden with DATAWATCH_API_URL; when it is not set, calls
go to https://api.anomalyarmor.ai (a labelled reconstruction).
Scope note: the platform's documentation enumerates 52 tool names (its own heading says 29 and its version line says 52; the enumerated sections list 52). datawatch implements a labelled core subset of 24 of them — alerts, assets, freshness and schema drift — and omits the metrics, validity, referential, destination, coverage, recommendation, Q&A, intelligence, lineage, job, tag and API-key tools.
Install
npx @reneturcios/datawatch get_alerts_summaryOr run the container image:
docker run -i ghcr.io/cloudcorprecords/datawatchThe container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
Related MCP server: Datadog MCP Server
CLI
The subcommands mirror the MCP tool names:
export ARMOR_API_KEY=...
datawatch health_summary
datawatch get_todays_briefing
datawatch list_alerts --status open --severity high
datawatch list_inbox_alerts --limit 20
datawatch update_alert --alert-id al1 --action acknowledge --comment "looking into it"
datawatch get_alert_trends --period 7d
datawatch list_alert_rules --asset-id a1 --is-active true
datawatch create_alert_rule --asset-id a1 --rule-type freshness --config '{"threshold_hours":24}'
datawatch list_assets --source snowflake --search orders
datawatch create_asset --name warehouse --source-type snowflake
datawatch trigger_asset_discovery --asset-id a1
datawatch check_freshness --asset-id a1 --table-path db.schema.orders
datawatch setup_freshness --asset-id a1 --table-path db.schema.orders --check-interval 1h
datawatch list_schema_changes --severity breaking
datawatch create_schema_baseline --asset-id a1 --description initial
datawatch get_schema_monitoring --asset-id a1
datawatch --versionResults print the upstream JSON payload. Exit codes: 0 on
success, 1 when a call fails (including a missing key or an
upstream API error), 2 for usage errors.
MCP server
One bin serves both faces. The mcp subcommand starts a stdio
MCP server:
npx -y @reneturcios/datawatch mcpMCP client configuration:
{
"mcpServers": {
"datawatch": {
"command": "npx",
"args": ["-y", "@reneturcios/datawatch", "mcp"],
"env": { "ARMOR_API_KEY": "..." }
}
}
}Tools
Tool | Input | What it does |
| (none) | Overall platform health summary. |
| (none) | Today's observability briefing. |
| (none) | Summary of current alerts. |
|
| List alerts with optional filters. |
|
| List inbox alerts. |
|
| Apply an action to an alert. |
|
| Alert trends for a period. |
|
| History of one alert. |
|
| List alert rules. |
|
| Create an alert rule. |
|
| Manage an alert rule. |
|
| List data assets. |
|
| Create a data asset. |
|
| Manage a data asset. |
|
| Trigger asset discovery. |
| (none) | Freshness summary across assets. |
|
| Check one asset's freshness. |
|
| Set up freshness monitoring. |
|
| List freshness schedules. |
|
| Manage a freshness schedule. |
| (none) | Schema monitoring summary. |
|
| List schema changes. |
|
| Create a schema baseline. |
|
| Schema monitoring for one asset. |
Development
npm install
npm run build # tsc -> dist/
npm test # node test runner over test/*.test.ts, no network (fake fetch fixtures)
npm run dev # run the CLI from source via tsxLicense
MIT — see LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
Data observability tools for engineering teams: alerts, freshness, schema drift, lineage, quality.
Schema-aware API monitoring: diff OpenAPI specs for breaking changes, manage endpoints.
Monitor websites, APIs, and servers: create monitors, triage incidents, and query uptime stats.
Define, ship & query your analytics tracking from one source of truth, trusted by humans and agents.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with DataDog's observability platform through a standardized interface. Supports monitoring infrastructure, managing events, analyzing logs and metrics, and automating operations like alerts and downtimes.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Datadog's observability platform via natural language, covering metrics, logs, APM, monitors, dashboards, incidents, and infrastructure.2,313 npm1MIT
- AlicenseBqualityDmaintenanceEnables natural-language investigation of Datadog data including logs, metrics, monitors, traces, hosts, dashboards, events, and incidents, all through read-only API access.141,876 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables monitoring and management of Apache Cassandra and DataStax Enterprise clusters through the DataStax OpsCenter API, providing tools for cluster metrics, node monitoring, schema access, and event tracking.1MIT