---
title: "Kiwi for Snyk"
description: "Have the agent on a Kiwi step scan its code and dependencies for vulnerabilities through the MCP server in the Snyk CLI."
canonical: "https://kiwiflow.io/integrations/snyk"
---

# Kiwi for Snyk

Have the agent on a Kiwi step scan its code and dependencies for vulnerabilities through the MCP server in the Snyk CLI.

- Your agent works in Snyk through its own connection. Kiwi does not call Snyk and never holds its credentials.
- A workflow skill can list Snyk among the tools it requires. When you supply your agent's available tools to a skill check and Snyk is not among them, the check reports `SK15-UNSUPPORTED-TOOL`.
- A project Admin can add links to Snyk, with notes, under Connections and bind them to the steps that use them. The agent reads them with `list_connections`.
- The agent can report the tools and plugins it ran with, including its Snyk connection, with `report_configuration`.
- The agent submits links to its work in Snyk as the step's outputs. People review them, and sign-off stays with the people your workflow names.

## What your agent can do in Snyk

- Scan source code for security issues with Snyk Code.
- Scan open source dependencies for known vulnerabilities.
- Scan infrastructure as code files and container images.
- Generate a software bill of materials and check a package's health before adding it.

## Set up

### 1. Connect your agent to Kiwi

Add Kiwi's hosted MCP server, `https://kiwiflow.io/mcp`, to your coding agent.

- [Coding agents](https://kiwiflow.io/integrations#agent)
- [Quickstart](https://docs.kiwiflow.io/quickstart#connect-your-agent)

### 2. Connect your agent to Snyk

Run the Snyk MCP server where your agent runs. The credentials stay with your agent.

```
snyk mcp -t stdio
```

- [Snyk documentation](https://docs.snyk.io/agent-security/agentic-security-with-snyk-studio/getting-started-with-snyk-studio)

### 3. Example skill

Publish instructions like these as a workflow skill that lists Snyk among its required tools.

```
Start from the repository path and the changed files in the assignment.
Run the Snyk code and open source scans on the changed project.
Fix new high severity issues, then scan one more time and stop there.
Submit the scan summary and any remaining issue IDs as the step outputs.
If issues remain after the second scan, report a blocker to the step
owner; the assigned reviewer decides on the remaining risks.
```

## More code quality and security integrations

- [Kiwi for SonarQube](https://kiwiflow.io/integrations/sonarqube.md): Have the agent on a Kiwi step read the SonarQube quality gate and issues for its change through the SonarQube MCP server.
- [Kiwi for Codecov](https://kiwiflow.io/integrations/codecov.md): Have the agent on a Kiwi step read a pull request's coverage change from the Codecov API and return it with the step's outputs.
- [Kiwi for Semgrep](https://kiwiflow.io/integrations/semgrep.md): Have the agent on a Kiwi step scan the code it changed for security issues with Semgrep through the Semgrep CLI's MCP server.
- [Kiwi for CodeRabbit](https://kiwiflow.io/integrations/coderabbit.md): Have the agent on a Kiwi step review its own changes with the CodeRabbit CLI and fix the findings before it submits them.
- [Kiwi for Socket](https://kiwiflow.io/integrations/socket.md): Have the agent on a Kiwi step check the Socket scores of a dependency before adding it, through Socket's MCP server.

- [Get started](https://kiwiflow.io/get-started)
- [Read the setup guide](https://docs.kiwiflow.io/other-tools)