search_alerts
Search alerts across tools/channels with severity, source, time breakdowns
LABSCO SUMMARY
Writing runbooks from an incident is the loop worth having, and it is rare to find it as a tool.
The moment you know what a runbook should say is halfway through the incident it would have prevented, and that is exactly when nobody has time to write one. Having create_runbook reachable from the same conversation where the alert is being triaged is the only way that habit survives. Be deliberate with manage_alert_definitions though — it deletes, and an agent removing an alert definition is a silent failure that only shows up the next time something breaks.
What it is
Doctor Droid's AIOps endpoint. Twelve tools that split into reading the incident picture, reading configuration, and changing both.
What you get
- search_alerts — across tools and channels, with severity, source and time breakdowns
- search_resources — dashboards, services and infrastructure across connected platforms
- get_service_catalog — services with their owners, dependencies and metadata
- list_investigations and list_runbooks — recent AI investigations, and the runbooks and wiki documents
- update_service, create_runbook, update_runbook — write the catalogue and the runbooks
- view_alert_definitions and view_auto_investigation_rules — the configuration, with sample alerts and DSL
- manage_alert_definitions and manage_auto_investigation_rules — create, update and delete them
Requirements
A bearer API key; there is no OAuth. The Business plan offers self-hosting inside your own VPC with no outbound traffic to Doctor Droid.
Setup effort
Paste a URL with a key — add the endpoint to your client
USE CASES
01
Understanding what is firing
Search alerts across every connected channel with severity and time breakdowns, in one place.
02
Finding who owns the broken thing
Read the service catalogue for owners and dependencies rather than asking around.
03
Capturing what you just learned
Write the runbook while the incident is fresh, from the same conversation.
04
Tuning noisy alerts
Read the definitions with their sample alerts, then change them — carefully, since this tool also deletes.
12 tools
Listed in project docs. Your client may show a different list.
search_resources
Search dashboards, services, infra across connected platforms
get_service_catalog
List services with owners, dependencies, metadata
list_investigations
View recent AI investigations with status
list_runbooks
List runbooks and wiki documents
update_service
Update a service catalog entry (WRITE)
create_runbook
Create a runbook with markdown content (WRITE)
update_runbook
Update or archive a runbook (WRITE)
view_alert_definitions
List/get alert definitions with sample alerts and DSL setup
view_auto_investigation_rules
List/get auto-investigation rules
manage_alert_definitions
Create/update/delete alert definitions (WRITE)
manage_auto_investigation_rules
Create/update auto-investigation rules (WRITE)
BEFORE YOU INSTALL
What to know first
Tools you get
12 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- Bearer API key (no OAuth)
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
ENDPOINT URL
https://aiops.drdroid.io/mcp/Requirements
- Bearer API key (no OAuth)
