Connect AI assistants to your Pulsetic monitoring platform using the [Model Context Protocol](https://modelcontextprotocol.io) (MCP).
Connect AI assistants to your Pulsetic monitoring platform using the Model Context Protocol (MCP). The pulsetic mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.
The Model Context Protocol is an open standard that allows AI assistants to interact with external tools and services. With Pulsetic's MCP server, you can ask your AI assistant to check monitor status, create incidents, schedule maintenance, and more — all through natural conversation.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Everything the assistant can do here goes through one of these:
Cursor — The Cursor tool exposed by this serverChatGPT — ChatGPT has native MCP support through Developer Mode. It uses OAuth to authenticate with PulseticMonitors — The Monitors tool exposed by this serverIncidents — The Incidents tool exposed by this serverMaintenance — The Maintenance tool exposed by this serverInitialize — The Initialize tool exposed by this serverlist_monitors — The list_monitors tool exposed by this serverget_monitor — Returns full details for a single monitor, including SSL certificate infoget_monitor_stats — Returns uptime %, downtime, incident count, and average response time across 1-day, 7-day, 30-day, and 90-day periodsget_monitor_events — Returns online/offline events in a date range (max 100, newest first)get_monitor_downtime — Returns total downtime in seconds and incident count for a periodcreate_monitor — The create_monitor tool exposed by this serverYou will need one environment variable: YOUR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Pulsetic MCP's toolset — Cursor, ChatGPT, Monitors and 11 more — is a fair guide to whether it matches your workflow. It is maintained by designmodo; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Cursor | The Cursor tool exposed by this server. |
| ChatGPT | ChatGPT has native MCP support through **Developer Mode**. It uses OAuth to authenticate with Pulsetic. |
| Monitors | The Monitors tool exposed by this server. |
| Incidents | The Incidents tool exposed by this server. |
| Maintenance | The Maintenance tool exposed by this server. |
| Initialize | The Initialize tool exposed by this server. |
| list_monitors | The list_monitors tool exposed by this server. |
| get_monitor | Returns full details for a single monitor, including SSL certificate info. |
| get_monitor_stats | Returns uptime %, downtime, incident count, and average response time across 1-day, 7-day, 30-day, and 90-day periods. |
| get_monitor_events | Returns online/offline events in a date range (max 100, newest first). |
| get_monitor_downtime | Returns total downtime in seconds and incident count for a period. |
| create_monitor | The create_monitor tool exposed by this server. |
| update_monitor | Updates an existing monitor's settings. Only include the fields you want to change. |
| delete_monitor | The delete_monitor tool exposed by this server. |
{
"mcpServers": {
"pulsetic": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://api.pulsetic.com/mcp",
"--header", "Authorization: Bearer YOUR_API_KEY"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.