# Integrations

> Cleric works with the tools your team already runs, and with anything that has an MCP server.
>
> Markdown version of https://cleric.ai/integrations for AI agents and LLMs. Site index: https://cleric.ai/llms.txt

Each integration below links to its setup steps and required permissions in the docs. The docs list is authoritative: https://docs.cleric.ai/integrations/supported-integrations.md

## 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: https://docs.cleric.ai/integrations/supported-integrations#datadog
- **Grafana**: Queries metrics, Loki logs, dashboards, and firing alert rules. Setup: https://docs.cleric.ai/integrations/supported-integrations#grafana
- **Prometheus**: Queries metrics and alert rules, including VictoriaMetrics, to compare against baseline. Setup: https://docs.cleric.ai/integrations/supported-integrations#prometheus
- **New Relic**: Runs NRQL over logs, metrics, traces, and alert incidents. Setup: https://docs.cleric.ai/integrations/supported-integrations#new-relic
- **Splunk**: Searches logs across indexes for errors, patterns, and trace IDs. Setup: https://docs.cleric.ai/integrations/supported-integrations#splunk
- **Elasticsearch**: Searches indexed logs and groups errors by pattern. Setup: https://docs.cleric.ai/integrations/supported-integrations#elasticsearch
- **Honeycomb**: Reads triggers to explain what an alert measures, and queries your data. Setup: https://docs.cleric.ai/integrations/supported-integrations#honeycomb
- **Sentry**: Inspects issues, stack traces, and releases to tie an error spike to a change. Setup: https://docs.cleric.ai/integrations/supported-integrations#sentry
- **Amplitude**: Checks whether event volumes or active users moved when an incident started. Setup: https://docs.cleric.ai/integrations/supported-integrations#amplitude

## 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: https://docs.cleric.ai/integrations/supported-integrations#kubernetes
- **Amazon Web Services**: Queries CloudWatch, Lambda, EC2, and load balancers through a read-only IAM role. Setup: https://docs.cleric.ai/integrations/supported-integrations#amazon-web-services
- **Amazon EKS**: Investigates EKS clusters using IAM authentication and Kubernetes RBAC. Setup: https://docs.cleric.ai/integrations/supported-integrations#elastic-kubernetes-service
- **Google Cloud Platform**: Reads Cloud Logging, Cloud Monitoring, and GKE health. Setup: https://docs.cleric.ai/integrations/supported-integrations#google-cloud-platform
- **Cloudflare**: Checks DNS, WAF events, Workers errors, traffic, and configuration changes. Setup: https://docs.cleric.ai/integrations/supported-integrations#cloudflare
- **MongoDB Atlas**: Finds slow queries, missing indexes, connection spikes, and replication lag. Setup: https://docs.cleric.ai/integrations/supported-integrations#mongodb-atlas
- **ClickHouse**: Inspects failing queries and inserts, merges, replication, memory, and disk. Setup: https://docs.cleric.ai/integrations/supported-integrations#clickhouse

## 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: https://docs.cleric.ai/integrations/supported-integrations#github
- **Bitbucket Cloud**: Reads code, pull requests, and Pipelines, and opens fix PRs when you allow it. Setup: https://docs.cleric.ai/integrations/supported-integrations#bitbucket-cloud
- **Buildkite**: Drills into failing builds, job logs, and annotations to explain a broken deploy. Setup: https://docs.cleric.ai/integrations/supported-integrations#buildkite
- **Unleash**: Checks whether a feature flag change caused, or coincided with, an incident. Setup: https://docs.cleric.ai/integrations/supported-integrations#unleash

## 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: https://docs.cleric.ai/integrations/supported-integrations#pagerduty
- **incident.io**: Uses incident history and service ownership, and posts updates and follow-ups. Setup: https://docs.cleric.ai/integrations/supported-integrations#incident.io

## 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: https://docs.cleric.ai/integrations/supported-integrations#slack
- **Linear**: Files and comments on issues with the findings from an investigation. Setup: https://docs.cleric.ai/integrations/supported-integrations#linear
- **Atlassian**: Reads Confluence runbooks and Jira issue history during investigations. Setup: https://docs.cleric.ai/integrations/supported-integrations#atlassian
- **Notion**: Searches the runbooks and postmortems you share with it. Setup: https://docs.cleric.ai/integrations/supported-integrations#notion
- **Slite**: Searches runbooks, incident procedures, and architecture notes. Setup: https://docs.cleric.ai/integrations/supported-integrations#slite

## 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: https://docs.cleric.ai/integrations/supported-integrations#generic-mcp

## Don’t see your tool?

Cleric isn’t limited to the list above.

### 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: https://docs.cleric.ai/integrations/supported-integrations#generic-mcp

### 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: https://cleric.ai/contact

## Catch failures before your customers do

Put Cleric to work on your production changes.

- Start free trial: https://cleric.ai/start
- Explore the product: https://demo.cleric.ai
- Book a demo: https://cleric.ai/demo