> 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/continue-guide.md).

# Connect Continue to Snyk

How to set up Snyk Studio and the Snyk MCP server in Continue

Connect Continue to the local Snyk MCP server to scan code and dependencies from your coding assistant.

{% hint style="info" %}
This setup provides MCP access. It does not install Studio Secure at inception hooks. Rules instruct the agent when to scan and depend on the model following those instructions.

For clients supported by the Studio CLI installer, use [Getting started with Snyk Studio](/agent-security/agentic-security-with-snyk-studio/getting-started-with-snyk-studio.md). For enterprise deployment, use the [Agentic Development Security (ADS) installer](/agent-security/evo-by-snyk/agentic-development-security-ads/activation-and-deployment.md).
{% endhint %}

## Prerequisites

* Install the Continue extension
* [Install the Snyk CLI](https://docs.snyk.io/developer-tools/snyk-cli/install-the-snyk-cli)

Add the Continue extension to your IDE. Visit the official [Continue installation page](https://docs.continue.dev/ide-extensions/install).

## Install the Snyk MCP server in Continue

Install the Snyk MCP server using the method that best suits your operating system and local development environment.

{% tabs %}
{% tab title="Pre-installed Snyk CLI" %}
Create or edit the MCP configuration file `~/.continue/mcpServers/new-mcp-server.yaml` .

```yaml
name: MCP Server
version: 0.0.1
schema: v1
mcpServers:
  - name: Snyk
    command: /absolute/path/to/snyk
    args:
      - "mcp"
      - "-t"
      - "stdio"      
    env: {}
```

If the `snyk` command is not available, add it by following the instructions on the [Install the Snyk CLI](https://docs.snyk.io/developer-tools/snyk-cli/install-the-snyk-cli) page.
{% endtab %}

{% tab title="Node.js and npx" %}
Create or edit the MCP configuration file `~/.continue/mcpServers/new-mcp-server.yaml` .

```yaml
name: MCP Server
version: 0.0.1
schema: v1
mcpServers:
  - name: Snyk
    command: npx
    args:
      - "-y"
      - "snyk@latest"
      - "mcp"
      - "-t"
      - "stdio"       
    env: {}
```

{% endtab %}
{% endtabs %}

## Set up the Snyk MCP server <a href="#setting-up-the-snyk-mcp-server" id="setting-up-the-snyk-mcp-server"></a>

The MCP server attempts to start automatically. The following example shows a Snyk MCP server that was successfully configured and started.

<figure><img src="https://2912686697-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN5N885PkllOWeBmgm3Bp%2Fuploads%2FmhTTkhlFkLoPADiY1Pgl%2Fimage.png?alt=media&amp;token=e9c108e0-991b-4b24-b64b-51520d5bc713" alt="Snyk MCP server configured and started in Continue"><figcaption></figcaption></figure>

Authenticate with Snyk and complete the client's trust request for the repository directory when prompted.

If you are already authenticated with the Snyk CLI installed on your system path, or through a prior interaction, then proceed to work with the Snyk MCP server.

## Use Agent mode

Continue only connects MCP servers in Agent mode. Select **Agent** before asking Continue to run a Snyk scan. Visit the [Continue MCP documentation](https://docs.continue.dev/customize/deep-dives/mcp).

## Secure at inception rules <a href="#secure-at-inception-rules" id="secure-at-inception-rules"></a>

Add rules to guide the assistant when invoking Snyk scans. Rules do not guarantee that the model runs a scan. For the generic rule text, visit [Rules for manual MCP integrations](/agent-security/agentic-security-with-snyk-studio/directives.md#rules-for-manual-mcp-integrations).

Create project rules for [Continue](https://docs.continue.dev/customize/deep-dives/rules) in the rules file at `.continue/rules/new-rule.md`. Start the file with the following front matter, then add the generic rule text:

```markdown
---
alwaysApply: true
---
```

## Examples

In the chat, you can tag specific files or functions and ask Continue to scan your code for safe deployment to production.

{% code title="prompt" overflow="wrap" %}

```
Scan this directory for code security & dependency vulnerabilities and security issues
```

{% endcode %}

Continue indicates that this request is related to security vulnerability scanning and calls the Snyk MCP server for various scans.

<figure><img src="https://2912686697-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN5N885PkllOWeBmgm3Bp%2Fuploads%2FuaHETKGihlMtTHOrFCKP%2Fimage.png?alt=media&amp;token=7dcbfed9-d625-494b-880e-9e1c36cdf822" alt="Continue calling the Snyk MCP server for a vulnerability scan"><figcaption></figcaption></figure>

Continue combines the code and dependency scan results with Snyk recommendations to suggest fixes for some or all of the findings.

<figure><img src="https://2912686697-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN5N885PkllOWeBmgm3Bp%2Fuploads%2FkrobOQazPaFktnxlSd0P%2Fimage%20(370).png?alt=media&amp;token=f0247c59-a95d-4a24-8c16-30499b74d2e8" alt="Continue reporting combined code and dependency scan results"><figcaption></figcaption></figure>


---

# 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/continue-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.
