Product updates

More MCP Server Tools

September 15, 2026

Sematext’s MCP Server got four more tools, all for troubleshooting synthetic monitors.

list_synthetics_monitors Lists Synthetics monitors with their current status and availability over 24 hours, 7 days and 30 days. A good general starting point.
list_synthetics_failed_runs Lists failed monitor runs, either account-wide or for a single monitor. Handy when you’re interested in what might be down right now.
get_synthetics_run Full detail for a single monitor run, including per-condition results, errors and screenshots. Used to drill down into specific failures.
get_synthetics_availability Availability for a single monitor, broken down by location. Shows whether a problem is general, or specific to a certain region.

 

The addition of these new tools opens up new possibilities. You can now prompt your AI with questions such as:

  • Are any of our Synthetics monitors failing right now? If so, when did they start failing and from which locations?
  • Our checkout monitor has been flaky. Can you show me the failed runs from the last 7 days and what the actual errors were?
  • Is our API slow everywhere or just in one region? Break the availability down by location for the last week.

 

With answers to these questions you can then prompt the AI to find the actual reasons why your synthetic monitors failed. Instead of only seeing that the monitor received a 500 HTTP response code or that the page or API you monitor took too long to respond and timed out, the AI will be able to use other tools available in the Sematext MCP Server to dig out the root cause of these failures. For that workflow to work you will want to have your logs and/or your application traces in Sematext as well.

Of course, you can also drill into relevant logs, traces, or metrics via the Sematext UI yourself.

 

Start Free Trial