Integration

Pulsetic integration

Pulsetic is an uptime and website monitoring service. Create, update, pause and delete monitors, read their checks, hourly snapshots, online/offline events and 1, 7, 30 and 90 day uptime statistics, and attach email, phone, webhook, Slack, Discord, Microsoft Teams or SIGNL4 alert channels; manage cron heartbeats and domain-expiry monitors; publish status page incidents, incident updates and maintenance windows; and read Real User Monitoring (RUM) analytics (pageviews, load times, Core Web Vitals, errors, realtime visitors). Creating or reconfiguring a status page itself (its domain, password and captcha keys) and the raw downtime-seconds counter are not exposed. Authentication is an API key created on the API page of the Pulsetic dashboard, sent as the raw value of the Authorization header (no Bearer prefix); a Read only key can call every read tool and is refused with 403 on any write. Requests are limited to three times the account's monitor limit per minute, at most 7000 per minute.

Connect Pulsetic How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Pulsetic.Built from the 52 Pulsetic tools below, on the connection you add once.

What you can do with Pulsetic

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Notification channel, 9 operations

add_discord_webhook_channelAdd discord webhook channelPOSTAdds a Discord notification channel to the monitor: Pulsetic then sends that monitor's alerts to this Discord webhook. Remove it with delete_notification_channel.
add_email_notification_channelAdd email notification channelPOSTAdds an email notification channel to the monitor: Pulsetic then sends that monitor's alerts to this email address. Remove it with delete_notification_channel.
add_phone_notification_channelAdd phone notification channelPOSTAdds a phone number notification channel to the monitor, alerting by SMS, by voice call, or both. Remove it with delete_notification_channel.
add_signl4_notification_channelAdd signl4 notification channelPOSTAdds a SIGNL4 notification channel to the monitor: Pulsetic then sends that monitor's alerts to this SIGNL4 webhook. Remove it with delete_notification_channel.
add_slack_notification_channelAdd slack notification channelPOSTAdds a Slack notification channel to the monitor: Pulsetic then sends that monitor's alerts to this Slack incoming webhook. Remove it with delete_notification_channel.
add_teams_notification_channelAdd teams notification channelPOSTAdds a Microsoft Teams notification channel to the monitor: Pulsetic then sends that monitor's alerts to this Teams webhook. Remove it with delete_notification_channel.
add_webhook_notification_channelAdd webhook notification channelPOSTAdds a generic webhook notification channel to the monitor: Pulsetic then sends that monitor's alerts to this URL. Remove it with delete_notification_channel.
delete_notification_channelDelete notification channelDELETERemoves a notification channel from its monitor.
list_monitor_notification_channelsList monitor notification channelsGETLists the notification channels attached to a monitor (email, webhook, Slack, Teams, SIGNL4 and others), each with its id for delete_notification_channel.

Heartbeat, 5 operations

create_heartbeatCreate heartbeatPOSTCreates a heartbeat monitor for a cron job or scheduled task, with its expected interval, grace period and alert channels (email, SMS, voice).
delete_heartbeatDelete heartbeatDELETEDeletes a heartbeat (cron job) monitor.
get_heartbeatGet heartbeatGETReturns one heartbeat monitor with its interval, grace period, alert settings and tags.
list_heartbeatsList heartbeatsGETLists the heartbeat (cron job) monitors, each with its interval, grace period, alert settings and tags.
update_heartbeatUpdate heartbeatPUTUpdates a heartbeat monitor's name, interval, grace period, alert channels or tags. Only the fields sent are changed.

Monitor, 5 operations

create_monitorsCreate monitorsPOSTCreates one monitor per URL in urls (several at once are allowed) and returns the created monitors. Configure the check itself afterwards with update_monitor.
delete_monitorDelete monitorDELETEDeletes a monitor and stops its checks.
get_monitorGet monitorGETReturns one monitor with its URL, status, check frequency, request and expected-response settings, uptime, response time, Lighthouse scores, SSL certificate, check nodes and tags.
list_monitorsList monitorsGETLists the monitors of the account, 20 per page by default, with each monitor's URL, status, check settings, uptime, response time, Lighthouse scores, SSL certificate and tags. Use per_page and page to paginate.
update_monitorUpdate monitorPUTUpdates a monitor (only fields sent): URL, name, check frequency, offline notification delay, SSL check, request (type, method, body, headers), expected response (body text, headers, negative match), tags. is_running false pauses, true resumes.

Domain, 4 operations

create_domainsCreate domainsPOSTAdds one or more domains to monitor (domain expiry), optionally tagging them all.
delete_domainDelete domainDELETEStops monitoring a domain and deletes it.
list_domainsList domainsGETLists the domains monitored for expiry, each with its alias, active flag, alert settings and tags.
update_domainUpdate domainPUTUpdates a monitored domain: its alias, whether it is active, which alerts are disabled (expired, expiring soon, status) and its tags. Only the fields sent are changed.

Incident, 4 operations

create_status_page_incidentCreate status page incidentPOSTCreates an incident on a status page together with its first update (status and message). Subscribers who have verified their email are notified by email. Needs a Full access API key.
delete_status_page_incidentDelete status page incidentDELETEDeletes a status page incident and removes it from the page.
list_status_page_incidentsList status page incidentsGETLists the incidents of a status page, each with its status and its updates.
update_status_page_incidentUpdate status page incidentPUTChanges an incident's title, and only its title. To change its status or resolve it, add an update with create_incident_update (status resolved); the incident and its history are kept. Needs a Full access API key.

Rum error, 4 operations

get_rum_error_summaryGet rum error summaryGETReturns a RUM site's error summary for a date range: total, JavaScript and HTTP error counts, affected pages, pageviews and error rate.
get_rum_error_timeseriesGet rum error timeseriesGETReturns a RUM site's JavaScript and HTTP error counts over time, bucketed by hour or day, for a date range.
list_rum_http_errorsList rum http errorsGETLists a RUM site's most frequent HTTP errors for a date range, with host, path, status, method, occurrences and last seen time.
list_rum_js_errorsList rum js errorsGETLists a RUM site's most frequent JavaScript errors for a date range, with message, source file, line, a sample stack, occurrences and last seen time.

Incident update, 3 operations

create_incident_updateCreate incident updatePOSTAdds an update to a status page incident and sets the incident's status to the update's status. Send status resolved to resolve the incident; the incident and its update history are kept.
delete_incident_updateDelete incident updateDELETEDeletes one update of a status page incident.
update_incident_updateUpdate incident updatePUTEdits an existing incident update's status, message or date.

Maintenance, 3 operations

create_status_page_maintenanceCreate status page maintenancePOSTSchedules a maintenance window on a status page: name, optional description, start and end date and time in a timezone, and the affected monitors.
delete_status_page_maintenanceDelete status page maintenanceDELETEDeletes a scheduled maintenance window from its status page.
update_status_page_maintenanceUpdate status page maintenancePUTUpdates a scheduled maintenance window: its name, description, dates, times, timezone and affected monitors. name, date, time and timezone are required on every update.

Status page, 3 operations

delete_status_pageDelete status pageDELETEDeletes a status page from the account.
get_status_pageGet status pageGETReturns one status page with its title, slug, domain, privacy, branding and style settings, and live and upcoming maintenance.
list_status_pagesList status pagesGETLists the account's status pages with their title, slug, domain, privacy, branding and style settings, and live and upcoming maintenance.

Rum site, 2 operations

get_rum_siteGet rum siteGETReturns one Real User Monitoring site with its domain, settings, tracking snippet and usage.
list_rum_sitesList rum sitesGETLists the Real User Monitoring (RUM) sites of the account with their domain, settings, tracking snippet and usage.

Check, 1 operation

list_monitor_checksList monitor checksGETReturns the individual checks the monitor ran in a time range: response code, size, headers, success or failure reason, timing phases and the node that ran it. Filter by node and response code.

Event, 1 operation

list_monitor_eventsList monitor eventsGETReturns the monitor's events in a time range, such as its Online and Offline transitions. Filter by type with monitor_event_type.

Monitor stats, 1 operation

get_monitor_statsGet monitor statsGETReturns the monitor's uptime percentage, downtime (HH:MM:SS) and average response time for the past 1, 7, 30 and 90 days.

Rum breakdown, 1 operation

get_rum_breakdownGet rum breakdownGETBreaks down a RUM site's pageviews and load time by one dimension (path, country, city, browser, os, device or referrer) for a date range.

Rum overview, 1 operation

get_rum_overviewGet rum overviewGETReturns a RUM site's pageviews, median, 75th and 95th percentile page load times, 75th percentile time to first byte (ms), and distinct pages and visitor countries, for a date range (last 7 days by default, at most 92 days).

Rum realtime, 1 operation

get_rum_realtimeGet rum realtimeGETReturns a realtime snapshot of a RUM site: current visitors (last 5 minutes), visitors and pageviews over 30 minutes, a per-minute visitor series and top pages, sources and breakdowns.

Rum timeseries, 1 operation

get_rum_timeseriesGet rum timeseriesGETReturns a RUM site's pageviews and load time percentiles over time, bucketed by hour or day, for a date range (last 7 days by default, at most 92 days).

Rum usage, 1 operation

get_rum_usageGet rum usageGETReturns the account's Real User Monitoring usage for the current billing period, its limit and whether it is over quota.

Rum vitals, 1 operation

get_rum_vitalsGet rum vitalsGETReturns good, needs-improvement and poor counts and the 75th percentile for each Core Web Vital (LCP, CLS, INP, FCP) of a RUM site over a date range.

Snapshot, 1 operation

list_monitor_snapshotsList monitor snapshotsGETReturns the monitor's hourly snapshots in a time range: check counts, failed checks, uptime and summed and average timing phases (DNS lookup, connect, TLS, first byte, total), per check node. 100 per page by default.

Use Pulsetic from Claude Code, Cursor or Codex

Connect Pulsetic in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Pulsetic operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Pulsetic

Create your workspace
Sign up free. Nothing to install.
Connect Pulsetic once
Add your Pulsetic connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.