MCP
Connect anything with an MCP server
Point Cleric at any HTTP MCP server, including ones in front of your internal tools, and it uses that server’s tools in its investigations.
Set up Generic MCPCleric works with the tools your team already runs, and with anything that has an MCP server.
Logs, metrics, traces, errors, and alerts: the evidence Cleric reads in every investigation.
Reads logs, metrics, monitors, and dashboards to explain why an alert fired.
Setup guideQueries metrics, Loki logs, dashboards, and firing alert rules.
Setup guideQueries metrics and alert rules, including VictoriaMetrics, to compare against baseline.
Setup guideRuns NRQL over logs, metrics, traces, and alert incidents.
Setup guideSearches logs across indexes for errors, patterns, and trace IDs.
Setup guideSearches indexed logs and groups errors by pattern.
Setup guideReads triggers to explain what an alert measures, and queries your data.
Setup guideInspects issues, stack traces, and releases to tie an error spike to a change.
Setup guideChecks whether event volumes or active users moved when an incident started.
Setup guideThe clusters, cloud accounts, edge, and databases your services run on.
Reads pods, events, deployments, and logs to find why a workload is failing.
Setup guideQueries CloudWatch, Lambda, EC2, and load balancers through a read-only IAM role.
Setup guideInvestigates EKS clusters using IAM authentication and Kubernetes RBAC.
Setup guideReads Cloud Logging, Cloud Monitoring, and GKE health.
Setup guideChecks DNS, WAF events, Workers errors, traffic, and configuration changes.
Setup guideFinds slow queries, missing indexes, connection spikes, and replication lag.
Setup guideInspects failing queries and inserts, merges, replication, memory, and disk.
Setup guideWhat changed, when it shipped, and which flags turned it on.
Reads code, commits, and Actions runs, and opens fix PRs when you allow it.
Setup guideReads code, pull requests, and Pipelines, and opens fix PRs when you allow it.
Setup guideDrills into failing builds, job logs, and annotations to explain a broken deploy.
Setup guideChecks whether a feature flag change caused, or coincided with, an incident.
Setup guideOpen incidents, past resolutions, and who owns what.
Reads open incidents and on-call patterns for the alert it is investigating.
Setup guideUses incident history and service ownership, and posts updates and follow-ups.
Setup guideWhere your team works with Cleric, and the runbooks and tickets it draws on.
Where your team works with Cleric: alerts start investigations and findings land in thread.
Setup guideFiles and comments on issues with the findings from an investigation.
Setup guideReads Confluence runbooks and Jira issue history during investigations.
Setup guideSearches the runbooks and postmortems you share with it.
Setup guideSearches runbooks, incident procedures, and architecture notes.
Setup guideAnything with an MCP server, including your internal tools.
Connects any HTTP MCP server, so Cleric can use your internal tools.
Setup guideCleric isn’t limited to the list above.
MCP
Point Cleric at any HTTP MCP server, including ones in front of your internal tools, and it uses that server’s tools in its investigations.
Set up Generic MCPOn request
If a system has no MCP server, tell us what you run. We add integrations on demand, and we move quickly.
Ask for an integrationPermissions and setup steps for each integration are in the docs .
Put Cleric to work on your production changes.