LastPing MCP server

LastPing is a monitoring service that works the other way round from most. Instead of watching a job and telling you when it looks wrong, it waits for the job to check in and tells you when it goes quiet. This MCP server lets your AI create those monitors, look at incidents, and see what happened, all from a chat.

What this MCP server does

You ask your AI something like "set up a monitor for my nightly backup." The AI uses this helper to create a monitor in your LastPing account and hands you back the ping commands to paste into your job. Later, if that job goes silent, LastPing raises an incident and your AI can pull up the details. You can also ask it to list open incidents, check a run's history, or pause a monitor you no longer need. Everything happens in the chat, no dashboard needed.

Click to zoom

What you can do with it

• Create a new monitor for a job, cron task, or AI agent
• List your monitors and see which ones are paused or snoozed
• Check open incidents and read what happened
• Look up the history of runs for a monitor
• Get the ping commands to paste into your own job
• Pause, resume, or delete a monitor you no longer need
• See which alert destinations are set up and test them

Try asking your AI

• “Create a monitor called nightly-backup that expects a ping every day at 3am”
• “What incidents are open right now?”
• “Show me the last ten runs for my nightly-etl monitor”
• “Pause the monitor for my old data sync job”

What it gives back to you

You get back plain answers in the chat: lists of monitors with their names and status, incident details with timestamps and any error text, or run histories showing when each run started and how it ended. When it creates or changes something, it tells you what it did. For new monitors, it also gives you the ping commands to paste into your job.

Before you start

Who it's for

Anyone who runs scheduled jobs, cron tasks, backups, or AI agents and wants to know when one quietly stops working.