4 #incidents MCP Servers & Clients

Every MCP server and client below is tagged #incidents — install one to give Claude, Cursor, VS Code, or any other MCP-compatible client access to incidents tools.

Drumbeats Mcp

drumbeats-io

Operate Drumbeats monitoring from any AI client — create cron/heartbeat and uptime monitors, triage incidents, and run HTTP/SSL/DNS diagnostics (no account needed for diagnostics).

Added 24 days ago

Pulsetic Mcp Server

designmodo

The Pulsetic MCP Server connects Pulsetic monitoring with AI agents and MCP-compatible tools, enabling direct access to uptime data, cron monitoring results, incident management workflows, and status page information through the Model Context Protocol (MCP).

Added 5 months ago

UptimeRobot MCP

uptimerobot

UptimeRobot lets you monitor websites, APIs, servers, and services through natural conversation. Create and configure monitors of every type — HTTP, keyword, ping, port, heartbeat, DNS, API, and UDP — then pause, resume, retarget, or retag them as your infrastructure changes. Whe

Added 27 days ago

New Relic MCP Server

cloudbring

Run NRQL, NerdGraph, and REST v2 operations to query data, manage incidents, create synthetics, and annotate deployments — all from your MCP client.

Added 12 months ago

Frequently asked questions

Common questions about MCP servers and clients tagged #incidents

What is a #incidents MCP server?

An MCP server tagged #incidents implements the Model Context Protocol so AI assistants like Claude, Cursor, and VS Code can access incidents-related tools, data, or APIs.

How many #incidents MCP servers and clients are there?

mcp.so currently lists 4 MCP servers and clients tagged #incidents.

How do I install a #incidents MCP server?

Open any server below and copy its install snippet into Claude Desktop, Cursor, VS Code, or another MCP client's configuration — remote servers need no separate download.

All