Integrations

Cleric works with the tools your team already runs, and with anything that has an MCP server.

Observability

Logs, metrics, traces, errors, and alerts: the evidence Cleric reads in every investigation.

  • Datadog

    Reads logs, metrics, monitors, and dashboards to explain why an alert fired.

    Setup guide
  • Grafana

    Queries metrics, Loki logs, dashboards, and firing alert rules.

    Setup guide
  • Prometheus

    Queries metrics and alert rules, including VictoriaMetrics, to compare against baseline.

    Setup guide
  • New Relic

    Runs NRQL over logs, metrics, traces, and alert incidents.

    Setup guide
  • Splunk

    Searches logs across indexes for errors, patterns, and trace IDs.

    Setup guide
  • Elasticsearch

    Searches indexed logs and groups errors by pattern.

    Setup guide
  • Honeycomb

    Reads triggers to explain what an alert measures, and queries your data.

    Setup guide
  • Sentry

    Inspects issues, stack traces, and releases to tie an error spike to a change.

    Setup guide
  • Amplitude

    Checks whether event volumes or active users moved when an incident started.

    Setup guide

Cloud and infrastructure

The clusters, cloud accounts, edge, and databases your services run on.

  • Kubernetes

    Reads pods, events, deployments, and logs to find why a workload is failing.

    Setup guide
  • Amazon Web Services

    Queries CloudWatch, Lambda, EC2, and load balancers through a read-only IAM role.

    Setup guide
  • Amazon EKS

    Investigates EKS clusters using IAM authentication and Kubernetes RBAC.

    Setup guide
  • Google Cloud Platform

    Reads Cloud Logging, Cloud Monitoring, and GKE health.

    Setup guide
  • Cloudflare

    Checks DNS, WAF events, Workers errors, traffic, and configuration changes.

    Setup guide
  • MongoDB Atlas

    Finds slow queries, missing indexes, connection spikes, and replication lag.

    Setup guide
  • ClickHouse

    Inspects failing queries and inserts, merges, replication, memory, and disk.

    Setup guide

Code and CI

What changed, when it shipped, and which flags turned it on.

  • GitHub

    Reads code, commits, and Actions runs, and opens fix PRs when you allow it.

    Setup guide
  • Bitbucket Cloud

    Reads code, pull requests, and Pipelines, and opens fix PRs when you allow it.

    Setup guide
  • Buildkite

    Drills into failing builds, job logs, and annotations to explain a broken deploy.

    Setup guide
  • Unleash

    Checks whether a feature flag change caused, or coincided with, an incident.

    Setup guide

Incident and paging

Open incidents, past resolutions, and who owns what.

  • PagerDuty

    Reads open incidents and on-call patterns for the alert it is investigating.

    Setup guide
  • incident.io

    Uses incident history and service ownership, and posts updates and follow-ups.

    Setup guide

Chat and collaboration

Where your team works with Cleric, and the runbooks and tickets it draws on.

  • Slack

    Where your team works with Cleric: alerts start investigations and findings land in thread.

    Setup guide
  • Linear

    Files and comments on issues with the findings from an investigation.

    Setup guide
  • Atlassian

    Reads Confluence runbooks and Jira issue history during investigations.

    Setup guide
  • Notion

    Searches the runbooks and postmortems you share with it.

    Setup guide
  • Slite

    Searches runbooks, incident procedures, and architecture notes.

    Setup guide

MCP and custom tools

Anything with an MCP server, including your internal tools.

  • Generic MCP

    Connects any HTTP MCP server, so Cleric can use your internal tools.

    Setup guide

Don’t see your tool?

Cleric isn’t limited to the list above.

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 MCP

On request

We’ll add what’s missing

If a system has no MCP server, tell us what you run. We add integrations on demand, and we move quickly.

Ask for an integration

Permissions and setup steps for each integration are in the docs .

Catch failures before your customers do

Put Cleric to work on your production changes.