WardenPoint runs on your own machine — the client starts it, so there is no endpoint to ping. 36 installs a week from npm. Last commit 14 Aug 2026.
Configure on-call alerting from an AI agent: recipients, groups, escalation policies, schedules.
Nothing serious here today
Today is the operative word: we check WardenPoint every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add wardenpoint-mcp -e 'WARDENPOINT_BASE_URL=<WARDENPOINT_BASE_URL>' -e 'WARDENPOINT_API_TOKEN=<WARDENPOINT_API_TOKEN>' -- npx -y @wardenpoint/mcp-server{
"mcpServers": {
"wardenpoint-mcp": {
"command": "npx",
"args": [
"-y",
"@wardenpoint/mcp-server"
],
"env": {
"WARDENPOINT_API_TOKEN": "<WARDENPOINT_API_TOKEN>",
"WARDENPOINT_BASE_URL": "<WARDENPOINT_BASE_URL>"
}
}
}
}[mcp_servers.wardenpoint-mcp]
command = "npx"
args = ["-y", "@wardenpoint/mcp-server"]
env = { WARDENPOINT_BASE_URL = "<WARDENPOINT_BASE_URL>", WARDENPOINT_API_TOKEN = "<WARDENPOINT_API_TOKEN>" }{
"mcpServers": {
"wardenpoint-mcp": {
"command": "npx",
"args": [
"-y",
"@wardenpoint/mcp-server"
],
"env": {
"WARDENPOINT_API_TOKEN": "<WARDENPOINT_API_TOKEN>",
"WARDENPOINT_BASE_URL": "<WARDENPOINT_BASE_URL>"
}
}
}
}{
"servers": {
"wardenpoint-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@wardenpoint/mcp-server"
],
"env": {
"WARDENPOINT_API_TOKEN": "<WARDENPOINT_API_TOKEN>",
"WARDENPOINT_BASE_URL": "<WARDENPOINT_BASE_URL>"
}
}
}
}Put your own values in place of
<WARDENPOINT_BASE_URL> (Origin of your WardenPoint installation, without a trailing slash and without /api/v1 — e.g. https://wardenpoint.com. The server reads the API description from it at startup, so the tools always match the version you actually run), <WARDENPOINT_API_TOKEN> (A company API key from Dashboard → Integrations → API keys. Abilities are chosen when you issue it; read-only is a good place to start. Not needed for --list-tools).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
WARDENPOINT_TIMEOUT_MS (Per-request timeout in milliseconds. Defaults to 30000), WARDENPOINT_ALLOW_INSECURE_TLS (Set to 1 to skip certificate verification. Development stands only — never against production).
Alternatives to WardenPoint
same job, measured the same wayManage incidents, on-call schedules, escalation policies, and alert notifications
MCP server for Jira Service Management Operations — alerts, on-call schedules and responders
Keeps AI agents from repeating costly mistakes: past decisions, rules and incidents, shared by all.
Real-device ad verification: malvertising and cloaking scans, AI policies, alerts, webhooks.
Coordination rooms for AI coding agents: path locks, tasks, and conflict alerts. Metadata only.
MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.
MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.
Incident management, on-call scheduling, and intelligent analysis powered by Rootly.
WardenPoint — questions
Answers built from our own checks of this server.