WardenPoint MCP server

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.

{
  "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 {WARDENPOINTBASEURL}/docs). Nothing about the API is restated in this package.

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

server starts — no package upgrade involved;

• an endpoint added to your installation appears as a tool the next time the

failure and the reason --spec-report exists.

• a description reworded upstream rewords the agent's instructions with it;
• an operation nobody described is invisible to the agent, which is the correct

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

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:

agent can explain an account somebody else built and change nothing.

• config.read — read the whole configuration. A good place to start: the

• 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.

Shortened. The full README is on GitHub.