WardenPoint

io.github.WardenPoint由 GitHub 账号 WardenPoint 发布v0.1.2更新于 Oct 24, 2026

Configure on-call alerting from an AI agent: recipients, groups, escalation policies, schedules.

概览

AI 生成的概览

让 AI 助手无需打开仪表盘即可配置 WardenPoint 值班告警账户:接收人、分组、升级策略、排班与路由。

可以做什么
  • 管理接收人、联系人与分组
  • 配置通知规则、升级策略与值班排班
  • 设置告警源集成与路由规则,包括电话通知
  • 按安装实例自身的 OpenAPI 描述为每个操作生成一个工具,启动时读取
  • 启动时报告工具数量与上下文开销,并可用模式变量收窄工具集
适用场景
适合让助手查看或修改值班告警配置的场景,例如搭建升级链、添加接收人,或解释他人已建好的配置,而不必在 WardenPoint 仪表盘中逐项点击。
运行要求
需要 Node 20 或更高版本,通过 npx 以 stdio 在本地运行。必须提供 WARDENPOINT_BASE_URL(安装实例的源地址,不带结尾斜杠和 /api/v1)以及 WARDENPOINT_API_TOKEN 中的公司 API 密钥,以 X-API-Key 发送;--list-tools 与 --spec-report 不需要令牌。可选:WARDENPOINT_TOOLS、WARDENPOINT_TIMEOUT_MS、WARDENPOINT_OPENAPI_PATH、WARDENPOINT_ALLOW_INSECURE_TLS。需要能访问该安装实例的网络;没有离线回退。
安装前请注意
API 密钥带有签发时选定的真实配置权限:config.write 允许创建、更新和删除,notifications.send 会触发告警,建议先用只读密钥。完整工具集约 89 个、约 64k token 上下文,可用 WARDENPOINT_TOOLS 收窄。WARDENPOINT_ALLOW_INSECURE_TLS 会关闭证书校验,仅限开发环境。告警源 webhook 的集成密钥作为工具参数传入,不会存储。Telegram 扫码和输入服务商密钥等步骤仍需人工完成。

安装

在 SourceWeft 中

  1. 打开 控制台中的 WardenPoint,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

WardenPoint MCP server

An MCP server that lets an agent configure a WardenPoint account — recipients, contacts, groups, notification rules, escalation policies, on-call schedules, alert-source integrations, routing rules and telephony — without anyone opening the dashboard.

It speaks stdio and exposes one tool per operation of your installation's own OpenAPI description.

json
{  "mcpServers": {    "wardenpoint": {      "command": "npx",      "args": ["-y", "@wardenpoint/mcp-server"],      "env": {        "WARDENPOINT_BASE_URL": "https://wardenpoint.com",        "WARDENPOINT_API_TOKEN": "acb_xxxxxxxx.xxxxxxxx"      }    }  }}

That is the whole installation. Your MCP client starts the server on demand; nothing runs between sessions.

The one rule this server exists to keep

There is no second copy of the contract here.

Every tool — its name, its text, its arguments, their descriptions, their enums and bounds, the responses it can answer with — is read at startup from the OpenAPI description served by the installation you are configuring (GET {WARDENPOINT_BASE_URL}/docs). Nothing about the API is restated in this package.

That is deliberate, and it is why the tools cannot quietly drift:

  • an endpoint added to your installation appears as a tool the next time the server starts — no package upgrade involved;
  • a description reworded upstream rewords the agent's instructions with it;
  • an operation nobody described is invisible to the agent, which is the correct failure and the reason --spec-report exists.

A description bundled inside this package would describe whatever was current when the package was published, while the agent talks to whatever you actually run. There is no offline fallback for the same reason: every tool here is an HTTP call to that installation, so if it cannot be reached, a complete tool list would be a list of things that cannot be done.

Requirements

Node 20 or newer. No build step, no native modules.

Environment

VariableRequiredMeaning
WARDENPOINT_BASE_URLyesOrigin of the installation — no trailing slash, no /api/v1 suffix. The description carries full paths.
WARDENPOINT_API_TOKENto callA company API key from Dashboard → Integrations → API keys. Sent as X-API-Key. Not needed for --list-tools or --spec-report.
WARDENPOINT_ALLOW_INSECURE_TLSno1 disables certificate verification. Development stands only — never against production.
WARDENPOINT_TIMEOUT_MSnoPer-request timeout, default 30000.
WARDENPOINT_TOOLSnoComma-separated patterns limiting which tools are offered, e.g. recipients,groups or v1_schedules_*. Unset means all of them.
WARDENPOINT_OPENAPI_PATHnoRead the description from a local file instead of the installation. For developing against a description that is not deployed yet.

The token is read from the environment at every start and is never written anywhere by this package.

What the key is allowed to do

Abilities are chosen when you issue the key, and a 403 names the one that was missing:

  • config.read — read the whole configuration. A good place to start: the agent can explain an account somebody else built and change nothing.
  • config.write — create, update, delete.
  • notifications.send / notifications.read — fire alerts and inspect them.

No ability can read a secret. There is no such ability in the vocabulary, so it cannot be granted by mistake. The API reports whether a credential is set and whether it verified — never its value.

What the tool list costs

Every tool definition is sent to the model before the person says anything, so it is spent whether or not the conversation ever touches WardenPoint. The full set of 89 tools is roughly 64k tokens — on a 200k context window, a third of it.

The server prints the figure at startup so it is not an invisible cost:

wardenpoint-mcp-server: 89 tools (~63k tokens of context; narrow it with WARDENPOINT_TOOLS) from …

If a session only ever touches part of the product, say so:

json
"env": { "WARDENPOINT_TOOLS": "recipients,groups,schedules" }

That drops the same run to a handful of tools and a few thousand tokens. Patterns match tool names (v1_recipients_store), and * works. Leave it unset and you get everything, which is the safe default: a tool that quietly disappeared looks like a missing product capability.

Running

bash
npx -y @wardenpoint/mcp-server --list-tools     # every tool, with its argumentsnpx -y @wardenpoint/mcp-server --spec-report    # gaps in the description itself

Both talk to WARDENPOINT_BASE_URL to fetch the description; neither needs a token. Without arguments the process speaks MCP over stdio and is meant to be started by a client, not by hand.

Two credentials, and why they are not interchangeable

  • API key (WARDENPOINT_API_TOKEN) — who you are. Every configuration tool uses it.
  • Integration secret — proves a specific alert-source webhook is genuine. Two tools accept it as an argument; it is not read from the environment and not stored here.

What this server deliberately cannot do

Two steps in setting up an account need a human at a screen, and both stay that way on purpose:

  • Scanning a Telegram QR code.
  • Typing a provider secret.

For each, the agent asks the installation to issue a one-time link, shows it to the person, and polls for the result. The person opens that link in the dashboard, behind their own login, and types the value themselves. Ask an agent to relay a secret through the conversation and it will refuse — that is what the link exists to avoid.

Errors reach the agent intact

The API spends real effort explaining refusals — which ability was missing, which field failed validation, why a send queued nothing. This server passes the body through whole, on success and failure alike, because an agent repairs itself from that text and nothing else.

Licence

MIT. See LICENSE.

Issues and contributions: https://github.com/WardenPoint/wardenpoint-mcp.

来源:README.md,提交 71d1c1b

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.1.2最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分