WardenPoint MCP Server

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 -- npx -y @wardenpoint/mcp-server

{
  "mcpServers": {
    "wardenpoint-mcp": {
      "args": [
        "-y",
        "@wardenpoint/mcp-server"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.wardenpoint-mcp]
command = "npx"
args = ["-y", "@wardenpoint/mcp-server"]

{
  "mcpServers": {
    "wardenpoint-mcp": {
      "args": [
        "-y",
        "@wardenpoint/mcp-server"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "wardenpoint-mcp": {
      "args": [
        "-y",
        "@wardenpoint/mcp-server"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: 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.), 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.). The author declared them in the registry entry; get the values from the project itself.