Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Data observability: alerts, freshness checks and schema drift for your data assets.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"datawatch": {
"command": "npx",
"args": [
"-y",
"@reneturcios/datawatch",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add datawatch -- npx -y @reneturcios/datawatch mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"datawatch": {
"command": "npx",
"args": [
"-y",
"@reneturcios/datawatch",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"datawatch": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/datawatch",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 CloudCorpRecords 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0)于4天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, Docker。
同一分类中有:Spec Driven Development, Remote Desktop Commander, zanadir
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Find what a repository's CI is missing, and which security checks cannot fail the build.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
npx @reneturcios/datawatch get_alerts_summary
Or run the container image:
docker run -i ghcr.io/cloudcorprecords/datawatch
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
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 --version
Results 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.
One bin serves both faces. The mcp subcommand starts a stdio MCP server:
npx -y @reneturcios/datawatch mcp
MCP client configuration:
{
"mcpServers": { "datawatch": { "command": "npx", "args": ["-y", "@reneturcios/datawatch", "mcp"], "env": { "ARMOR_API_KEY": "..." } } } }
| Tool | Input | What it does |
|---|---|---|
health_summary | (none) | Overall platform health summary. |
get_todays_briefing | (none) | Today's observability briefing. |
get_alerts_summary | (none) | Summary of current alerts. |
list_alerts | status, severity, asset_id, from_date, to_date | List alerts with optional filters. |
list_inbox_alerts | status, limit (integer) | List inbox alerts. |
update_alert | alert_id, action (both required), comment | Apply an action to an alert. |
get_alert_trends | period | Alert trends for a period. |
get_alert_history | alert_id (required) | History of one alert. |
list_alert_rules | asset_id, is_active (boolean) | List alert rules. |
create_alert_rule | asset_id, rule_type (both required), config (object) | Create an alert rule. |
manage_alert_rule | rule_id, action (both required) | Manage an alert rule. |
list_assets | source, asset_type, search | List data assets. |
create_asset | name, source_type (both required), connection_config (object) | Create a data asset. |
manage_asset | asset_id, action (both required) | Manage a data asset. |
trigger_asset_discovery | asset_id (required) | Trigger asset discovery. |
get_freshness_summary | (none) | Freshness summary across assets. |
check_freshness | asset_id (required), table_path | Check one asset's freshness. |
setup_freshness | asset_id, table_path (both required), check_interval | Set up freshness monitoring. |
list_freshness_schedules | asset_id | List freshness schedules. |
manage_freshness_schedule | schedule_id, action (both required) | Manage a freshness schedule. |
get_schema_summary | (none) | Schema monitoring summary. |
list_schema_changes | asset_id, severity, from_date, to_date | List schema changes. |
create_schema_baseline | asset_id (required), description | Create a schema baseline. |
get_schema_monitoring | asset_id (required) | Schema monitoring for one asset. |
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 tsx
MIT — see LICENSE.