> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/agent-security/agentic-security-with-snyk-studio/quickstart-guides/kiro-guide.md).

# Connect Kiro to Snyk

How to set up Snyk Studio in Kiro with the Snyk CLI

Set up Snyk Studio in Kiro to invoke Snyk scanning tools, evaluate package health, and use remediation workflows.

This integration includes MCP access and remediation and package-health components. The Studio installer does not add Secure at inception hooks for Kiro. For the differences between assistants, visit the [capability matrix](https://docs.snyk.io/agent-security/agentic-security-with-snyk-studio/getting-started-with-snyk-studio.md#coding-assistant-support).

For enterprise deployment, use the [Agentic Development Security (ADS) installer](https://docs.snyk.io/agent-security/evo-by-snyk/agentic-development-security-ads/activation-and-deployment.md).

## Install Snyk Studio

Install Kiro and the [Snyk CLI](https://docs.snyk.io/developer-tools/snyk-cli/install-the-snyk-cli). Enable the Snyk products you want to scan with. Complete the account and product setup in [Getting started with Snyk Studio](https://docs.snyk.io/agent-security/agentic-security-with-snyk-studio/getting-started-with-snyk-studio.md).

1. Authenticate with Snyk:

   ```bash
   snyk auth
   ```
2. Run the installer as the developer who uses Kiro:

   ```bash
   snyk studio install --experimental --ade=kiro
   ```
3. Start a new session in Kiro and open the repository you want to work in. Complete any MCP authentication or folder-trust request.

## Verify installation

Run:

```bash
snyk studio install --experimental --verify --ade=kiro
```

This checks the installed assets. For merged configuration files, the verifier checks only file existence. It does not confirm that a scan completed.

Ask Kiro to scan the repository:

```
Scan this repository for code and dependency vulnerabilities. Summarize the findings before making changes.
```

## Invoke scans and remediation

Ask the assistant to invoke Snyk tools when you want a scan. If you add rules about when to scan, they rely on the model following those instructions and do not provide programmatic hook execution.

Use the installed remediation and package-health workflows for existing vulnerabilities and package selection. Visit [Directives](https://docs.snyk.io/agent-security/agentic-security-with-snyk-studio/directives.md) for their behavior and limitations.

## Update or remove Snyk Studio

After updating the Snyk CLI, run the installation command again to refresh the components, then start a new assistant session.

To remove the local setup for Kiro, run:

```bash
snyk studio install --experimental --uninstall --ade=kiro
```

If your company deployed Studio through ADS, use the [ADS removal procedure](https://docs.snyk.io/agent-security/evo-by-snyk/agentic-development-security-ads/activation-and-deployment.md#uninstall).

## Manual MCP configuration

For an MCP-only connection, use the [manual configuration instructions](https://docs.snyk.io/agent-security/agentic-security-with-snyk-studio/getting-started-with-snyk-studio.md#configure-the-snyk-mcp-server) with your client's supported configuration format. Manual MCP setup does not install the full Studio components.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/agent-security/agentic-security-with-snyk-studio/quickstart-guides/kiro-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
