---
title: "Integrations | Clearly AI: Continuous Threat Modeling Platform"
description: "Clearly AI connects to Jira, GitHub, Confluence, ServiceNow, OneTrust, Wiz, and more. It gathers review context from your existing tools and routes cited findings back where your team works."
canonical: https://clearly-ai.com/integrations
---

_Integrations_

# Threat models built from the tools you already use

Clearly AI connects to your tickets, design docs, code, and governance systems. It autonomously gathers the context each review needs, then routes cited findings back to the tools where security and the business already work. No manual diagramming or workflow changes required.

- [Contact Enterprise Sales](https://clearly-ai.com/demo)
- [View setup docs](https://clearly-ai.com/docs)

- Ericsson
- PayPal
- Modern Health
- Hagerty
- Rivian
- Infineon
- Bastion

## How it works

### Connect your context

Add Jira issues, design docs, repositories, and GRC records as project sources.

### Trigger reviews automatically

A new Jira ticket, an opened pull request, or a ServiceNow change request can start a review with no manual kickoff. Every change that ships gets reviewed as it moves through the SDLC.

### Route findings back

Findings, comments, tickets, and review exports land in Jira, GitHub, Linear, Azure DevOps, ServiceNow, Slack, and OneTrust. Developers get feedback without waiting on security.

_For developers and the agents they build with_

## Clearly AI, wherever you work

### MCP server

_Run reviews from your AI assistant_

Connect Cursor, Claude Code, Kiro, Devin, Codex, Claude Desktop, Windsurf, VS Code with Copilot, or any MCP-compatible client to Clearly AI. Anything you can do in Clearly AI, you can do through our MCP server.

Ask a chatbot how your third-party approval process works today. Plan a feature with a coding agent, grounded in your data classification policy. Or wire Clearly AI into your existing workflows from your managed-agents platform.

Every action runs as you, with your identity and your organization's permissions. Authentication uses OAuth 2.0 with your existing Clearly AI sign-in.

[See more about Clearly AI’s MCP server](https://clearly-ai.com/platform/ide-and-mcp)

> “Can we use Copilot to analyze customer support emails?”

> “When was our last vendor review of Twilio?”

> “Run a threat model against https://github.com/org/document-service/pull/742”

> “We need to start collecting phone numbers in our ATS, can you update the Clearly AI review?”

### Review templates as code

_Your review standards, versioned like code_

Author and maintain review templates in YAML, in Cursor or your editor of choice. Start from a working STRIDE threat model, draft new templates with your AI coding assistant, and validate them with tests before they go live.

Every upload creates a new version, and every review stays tied to the exact template version it ran against. Your standards stay consistent, reviewable, and auditable. Clearly AI is built for teams that already have a process, or need to build one.

Prefer scripting? Use the Clearly AI CLI and REST API to create projects, upload sources, start reviews, and fetch results.

[See documentation](https://clearly-ai.com/docs)

## Integration directory

Connect the systems your review process already runs on. Each integration can act as a context source, a workflow trigger, a write-back destination, or all three.

### Jira

Category: Issue trackers

Tags: Source, Trigger, Write-back

The whole loop stays inside Jira

**Trigger:** Start a review the moment a ticket is created or labeled, for example `needs-security-review`.

**Source:** Clearly AI pulls the issue in as context.

**Write-back:** It then posts a summary comment, creates follow-up tickets, assigns owners, or attaches the full review export.

Auth: Personal token

[Jira documentation](https://clearly-ai.com/docs/integrations/issue-trackers/jira)

### Aha! Roadmaps

Category: Issue trackers

Tags: Source

Security sees what's planned early, while design changes are still cheap

**Source:** Bring roadmap features and requirements into a review before anything is built.

Auth: See setup docs

[Aha! Roadmaps documentation](https://clearly-ai.com/docs/integrations/issue-trackers/aha)

### Azure DevOps Work Items

Category: Issue trackers

Tags: Source, Trigger, Write-back

**Trigger:** Trigger reviews from new or updated work items, filtered by tag, project, or state.

**Write-back:** Findings return as comments, new work items, assignments, or attached review exports.

Auth: Personal token

[Azure DevOps Work Items documentation](https://clearly-ai.com/docs/integrations/issue-trackers/azure-devops-work-items)

### Linear

Category: Issue trackers

Tags: Source, Trigger, Write-back

**Trigger:** Kick off reviews from Linear issues by label or team.

**Write-back:** Clearly AI comments on the issue, creates follow-ups, assigns owners, and attaches the review, all where your engineers already track work.

Auth: OAuth 2.0 or personal token

[Linear documentation](https://clearly-ai.com/docs/integrations/issue-trackers/linear)

### ServiceNow

Category: Issue trackers

Tags: Source, Trigger, Write-back

**Trigger:** Trigger reviews from records on the tables you choose, such as change requests and incidents.

**Write-back:** Results come back as comments, new records, assignments, or attached exports.

Auth: OAuth 2.0 client credentials

[ServiceNow documentation](https://clearly-ai.com/docs/integrations/issue-trackers/service-now)

### Confluence

Category: Documents and knowledge

Tags: Source

**Source:** Point a review at the design docs and architecture pages your team already wrote. Clearly AI builds the picture of the system from them, with no re-diagramming, and cites the page behind every finding.

[Confluence documentation](https://clearly-ai.com/docs/integrations/documents/confluence)

### Google Drive

Category: Documents and knowledge

Tags: Source, Write-back

**Source:** Use Drive docs as review context.

**Write-back:** Have workflows write generated documents back to Google Docs.

[Google Drive documentation](https://clearly-ai.com/docs/integrations/documents/google-drive)

### SharePoint

Category: Documents and knowledge

Tags: Source, Write-back

**Source:** Pull design docs and policies from SharePoint as review sources.

**Write-back:** Publish review output back as SharePoint files.

Auth: OAuth 2.0

[SharePoint documentation](https://clearly-ai.com/docs/integrations/documents/sharepoint)

### Notion

Category: Documents and knowledge

Tags: Source, Write-back

**Source:** Use specs and wikis in Notion as review context.

**Write-back:** Have workflows create Notion pages with review results.

Auth: OAuth 2.0

[Notion documentation](https://clearly-ai.com/docs/integrations/documents/notion)

### GitHub

Category: Code repositories

Tags: Source, Trigger, Write-back

**Trigger:** Reviews can trigger when a pull request is opened, merged, or labeled, or from other repository events.

**Source:** Add repositories and branches as review context, with include and exclude patterns to keep scope tight.

**Write-back:** A summary and review link can post directly on the PR.

Auth: OAuth 2.0 or personal token

[GitHub documentation](https://clearly-ai.com/docs/integrations/code/github)

### GitLab

Category: Code repositories

Tags: Source

**Source:** Add GitLab repositories as review context so findings are grounded in the code that actually ships.

Auth: Personal token

[GitLab documentation](https://clearly-ai.com/docs/integrations/code/gitlab)

### Azure Repos

Category: Code repositories

Tags: Source

**Source:** Add Azure Repos branches as review context alongside your Azure DevOps work items.

Auth: Personal token

[Azure Repos documentation](https://clearly-ai.com/docs/integrations/code/azure-repos)

### Bitbucket

Category: Code repositories

Tags: Source

**Source:** Add Bitbucket repositories as review context, scoped to the files that matter.

Auth: Personal token

[Bitbucket documentation](https://clearly-ai.com/docs/integrations/code/bitbucket)

### Slack

Category: Communication

Tags: Write-back

**Write-back:** Deliver review summaries and high-priority findings directly to the right reviewers in Slack, so decisions don't wait on someone checking a dashboard.

[Slack documentation](https://clearly-ai.com/docs/integrations/communication/slack)

### Archer IRM

Category: Governance, risk, and compliance

Tags: Source

**Source:** Search your Archer policies, standards, and procedures during a review. Clearly AI cites the matching records with a link back to Archer, so every finding traces to your governing policy. Configured with the Clearly AI team.

Auth: Personal token, guided setup

[Archer IRM documentation](https://clearly-ai.com/docs/integrations/governance/archer)

### OneTrust

Category: Governance, risk, and compliance

Tags: Source, Write-back

Privacy teams complete PIAs without retyping and without a second process

**Source:** Read OneTrust assets into a review.

**Write-back:** Publish review answers straight into OneTrust assessments.

Auth: OAuth 2.0 client credentials

[OneTrust documentation](https://clearly-ai.com/docs/integrations/governance/onetrust)

### Snyk

Category: Security tools

Tags: Source

Scanner results become one input to a complete review, not the review itself

**Source:** Import Snyk vulnerability and code-security findings as review context. Workflows can also scan a project's repositories with Snyk automatically.

Auth: Personal token

[Snyk documentation](https://clearly-ai.com/docs/integrations/security/snyk)

### Wiz

Category: Security tools

Tags: Source

Your threat model reflects how the system is actually deployed, not just how it was designed

**Source:** Import Wiz projects and cloud posture findings as review context.

Auth: OAuth 2.0 client credentials

[Wiz documentation](https://clearly-ai.com/docs/integrations/security/wiz)

### MCP Server

Category: Developer tools

Tags: None

Review agent plans, threat model risky changes, and run any Clearly AI operation from Cursor, Claude Code, Kiro, Devin, Codex, and other MCP clients

[MCP Server documentation](https://clearly-ai.com/docs/mcp)

### CLI

Category: Developer tools

Tags: None

Create projects, upload sources, start reviews, and fetch results from the command line

[CLI documentation](https://clearly-ai.com/docs/cli)

### Microsoft Power Apps

Category: Developer tools

Tags: None

Kick off intake from a custom app your team built

[Microsoft Power Apps documentation](https://clearly-ai.com/docs/integrations)

### REST API

Category: Developer tools

Tags: None

Build Clearly AI reviews into your own pipelines and tooling

[REST API documentation](https://clearly-ai.com/docs/api-reference)

### Clearly Quickstart

Category: Developer tools

Tags: None

Author, test, and version review templates as code. Repository access is available from your Clearly AI team.

[Clearly Quickstart documentation](https://clearly-ai.com/docs/clearly-quickstart)

## Connected on your terms

Every integration authenticates through OAuth 2.0, client credentials, or a token you control. Credentials can be scoped to a single user or shared across your workspace.

Workflows can only take the actions you've configured, using the credentials you've authorized, and they never get open-ended access to unrelated systems. Every finding carries its source, so your reviewers can challenge it, push back, and sign.

[Security and privacy](https://clearly-ai.com/trust/security-privacy)

## Coverage that doesn't depend on someone remembering the next step

- **90%** Reduction in review turnaround time
- **4x** Review capacity with the same headcount.
- **From 10 to 100%** Product coverage

> “As soon as we started using Clearly AI, we saw an immediate reduction in the amount of time that not only my team was spending on the reviews, but that the business owners were actually spending having to give us the answers for the assessments.”
>
> — Ashley Haynes, Senior Director of Privacy, Trust and AI Governance, Ericsson Enterprise Wireless Solutions

[Read the Ericsson story](https://clearly-ai.com/customer-stories/ericsson)

![Four Ericsson colleagues working together around a table in a bright office.](https://clearly-ai.com/platform/figma/ericsson-team.jpg)

_FAQ_

## Answers to your top questions

### What does Clearly AI integrate with?

Clearly AI integrates with issue trackers (Jira, Aha! Roadmaps, Azure DevOps, Linear, ServiceNow) and document tools (Confluence, Google Drive, SharePoint, Notion). It also connects to code repositories (GitHub, GitLab, Azure Repos, Bitbucket), Slack, GRC platforms (Archer IRM, OneTrust), and security tools (Snyk, Wiz). An MCP server, CLI, and REST API are available for developer workflows.

### Can Clearly AI start a threat model automatically?

Yes. Workflows trigger reviews from Jira, GitHub, Azure DevOps, Linear, and ServiceNow events, such as a labeled ticket, an opened pull request, or a new change request. No one has to start the review by hand.

### Does Clearly AI replace Snyk or Wiz?

No. Clearly AI imports their findings as context for a complete review. Scanners flag issues. Clearly AI automates the review workflow around them, covering triage, analysis, and next steps, with every finding cited to its source.

### Does Clearly AI have an MCP server?

Yes! Clearly AI's MCP server is generally available and works with Cursor, Claude Code, Kiro, Devin, Codex, and other MCP-compatible coding agents. It reviews agent plans against your security policies, threat models security-impacting changes, and runs every action under your own identity and permissions.

[See how it works](https://clearly-ai.com/platform/ide-and-mcp)

### Can we manage review templates as code?

Yes. Teams author review templates in YAML in their editor, validate them with tests, and upload them to Clearly AI. Each upload is versioned, and every review stays tied to the template version it ran against.

### Do privacy and GRC teams use the same integrations?

Yes. The same connectors power threat models, privacy impact assessments, vendor risk reviews, and AI governance evaluations, all on one platform and one license.

## See Clearly AI in your stack

Bring a real Jira ticket or design doc. We'll show you a cited, structured threat model built from it.

[Contact Enterprise Sales](https://clearly-ai.com/demo)

## Learn more

- [Secure everything that ships](https://clearly-ai.com)
- [We built the tool we wished we had](https://clearly-ai.com/about-us)
- [One platform. From intake to remediation.](https://clearly-ai.com/platform)
- [Know everything that needs a review. Skip the 300-question form.](https://clearly-ai.com/platform/security-intake)
- [Ask only what matters. Get it right the first time.](https://clearly-ai.com/platform/conversational-intake)
- [Every finding, tracked to a decision](https://clearly-ai.com/platform/resolve/risk-registry)
- [Show leadership and auditors exactly what security reviewed](https://clearly-ai.com/platform/resolve/reporting)
- [Security reviews you can stand behind, every time](https://clearly-ai.com/platform/quality)
- [Threat models built from the tools you already use](https://clearly-ai.com/integrations)
- [Threat models that know about today's attacks](https://clearly-ai.com/platform/threat-intelligence)
- [Automate every step around the review](https://clearly-ai.com/platform/workflows)
- [Threat models your teams can work on together](https://clearly-ai.com/platform/collaboration)
- [Understand the system before the review starts](https://clearly-ai.com/platform/enterprise-context-graph)
- [Trust, security, and deployment](https://clearly-ai.com/platform/trust-security-and-deployment)
- [Every plan reviewed. Every risky change threat modeled.](https://clearly-ai.com/platform/ide-and-mcp)
- [Verify what actually shipped](https://clearly-ai.com/platform/control-and-remediation-verification)
- [A current threat model for everything that ships](https://clearly-ai.com/solutions/continuous-threat-modeling)
- [Prove every product that ships meets your security bar](https://clearly-ai.com/solutions/product-security-assurance)
- [Privacy reviews your team can stake decisions on](https://clearly-ai.com/solutions/privacy)
- [Every vendor reviewed against your standards](https://clearly-ai.com/solutions/third-party-risk)
- [Review every design before it's built](https://clearly-ai.com/solutions/design-and-architecture-reviews)
- [Secure the AI you build, buy, and code with](https://clearly-ai.com/solutions/ai-agentic-security)
- [Every regulation you answer to. One review process.](https://clearly-ai.com/solutions/compliance)
- [Every product ready for the Cyber Resilience Act without growing your team](https://clearly-ai.com/solutions/compliance/cyber-resilience-act)
- [Build vs. buy for security review automation](https://clearly-ai.com/compare/claude-chatgpt)
- [The ThreatModeler alternative built from your own docs, code, and policies](https://clearly-ai.com/compare/threatmodeler)
- [The Clover Security alternative with findings your team can trust](https://clearly-ai.com/compare/clover)
- [The Prime Security alternative for every review your team runs](https://clearly-ai.com/compare/prime)
- [Security and Privacy](https://clearly-ai.com/trust/security-privacy)
- [Clearly AI Privacy Policy](https://clearly-ai.com/trust/privacy-policy)
- [Clearly AI Subprocessors](https://clearly-ai.com/trust/subprocessors)
- [AI Risk Reviews](https://clearly-ai.com/use-cases/ai-risk-reviews)
- [Automate Triage](https://clearly-ai.com/use-cases/automate-triage)
- [Privacy Impact Assessments](https://clearly-ai.com/use-cases/privacy-impact)
- [Vendor Risk Assessments](https://clearly-ai.com/use-cases/vendor-risk)
- [Threat Modeling](https://clearly-ai.com/use-cases/threat-modeling)
- [Contact](https://clearly-ai.com/contact)
- [Contact Enterprise Sales](https://clearly-ai.com/demo)
- [Latest from the Clearly AI blog](https://clearly-ai.com/blog)
- [In the news](https://clearly-ai.com/press)
- [How Ericsson Enterprise Wireless Solutions cut review times by up to 80%](https://clearly-ai.com/customer-stories/ericsson)
- [How HID Global reviews 300+ products for the Radio Equipment Directive with the team it already has](https://clearly-ai.com/customer-stories/hid-global)
- [How Rivian scaled privacy and AI governance reviews 4x without adding headcount](https://clearly-ai.com/customer-stories/rivian)
- [Part 2! Okay, privacy is different from security. Now what?](https://clearly-ai.com/blog/part-2-okay-privacy-is-different-from-security-now-what)
- [How AI is rewiring our product engineering workflow](https://clearly-ai.com/blog/how-ai-is-rewiring-our-product-engineering-workflow)
- [Good Data Scientists and Bad Outcomes, Part 1: What's the difference between security and privacy work?](https://clearly-ai.com/blog/good-data-scientists-and-bad-outcomes-what-s-the-difference-between-security-and-privacy-work)
- [Why I Joined Clearly AI](https://clearly-ai.com/blog/why-vp-marketing-joined-clearly-ai)
- [Skip the Marketing: Clearly AI for Technical People](https://clearly-ai.com/blog/clearly-ai-technical-explanation)
- [Clearly AI Raises $8.4M Seed Round to Scale Product Security](https://clearly-ai.com/blog/seed-round)
- [Why We Started Clearly AI](https://clearly-ai.com/blog/why-we-started-clearly-ai)
- [Applying AI to Threat Modeling - Where AI Thrives, Survives, and Dies](https://clearly-ai.com/blog/applying-ai-to-threat-modeling)
- [Why We Build in Public](https://clearly-ai.com/blog/why-we-build-in-public)
- [Solving the Threat Modeling Bottleneck with AI Workflows](https://clearly-ai.com/blog/solving-the-threat-modeling-bottleneck-with-ai-workflows)
- [Clearly AI Named Finalist in the 2025 Okta Startup Challenge](https://clearly-ai.com/blog/clearly-ai-named-finalist-in-the-2025-okta-startup-challenge)
- [Security, SOC 2, & Startups](https://clearly-ai.com/blog/security-soc-2-startups)
- [Building Reliable AI Systems for Security and Privacy Reviews](https://clearly-ai.com/blog/building-reliable-ai-systems-for-security-and-privacy-reviews)
- [How to Automate Security and Privacy Reviews with Clearly AI](https://clearly-ai.com/blog/how-to-automate-security-and-privacy-reviews-with-clearly-ai)
- [One Year of Clearly AI](https://clearly-ai.com/blog/one-year-of-clearly-ai)
- [Navigating EU RED Compliance: Meeting the August 2025 Deadline](https://clearly-ai.com/blog/navigating-eu-red-compliance-meeting-the-august-2025-deadline)
- [The AI Engineer Cheat Sheet](https://clearly-ai.com/blog/the-ai-engineer-cheat-sheet)
- [Intelligent Vendor Risk Assessments](https://clearly-ai.com/blog/intelligent-vendor-risk-assessments)
- [Clearly AI wins the AWS Bedrock Builder's Challenge](https://clearly-ai.com/blog/clearly-ai-wins-the-aws-bedrock-builder-s-challenge)
- [Reviews, reviews, reviews!](https://clearly-ai.com/blog/reviews-reviews-reviews)
- [Halfway through YC](https://clearly-ai.com/blog/halfway-through-yc)
- [llms.txt — site overview for LLMs](https://clearly-ai.com/llms.txt)
- [llms-full.txt — full site content for LLMs](https://clearly-ai.com/llms-full.txt)
- [sitemap.xml — all public routes](https://clearly-ai.com/sitemap.xml)
- [Documentation](https://docs.clearly-ai.com/docs)

[Canonical page](https://clearly-ai.com/integrations)
