WardenPoint MCP Server

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

Packages and local setup

The published npm package is @wardenpoint/mcp-server, version 0.1.2. Its declared MCP transport is stdio.

The package declares WARDENPOINT_BASE_URL (required): 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 (required): 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.; 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related monitoring & observability MCP servers for tools that cover the same kind of work.