# Getting started with Snyk Studio

Snyk Studio supports a default hooks-based approach for some agentic development environments (ADEs) to ensure code written by AI coding assistants is secure at inception (SAI):

* Claude Code
* Cursor
* Codex CLI
* Gemini CLI

If you use one of these ADEs, use the [Snyk Studio installer script to install Snyk Studio](#install-snyk-studio-for-ades-with-hooks-support).

If your ADE does not support a hooks-based approach to SAI, use a rules-based approach. Install Snyk Studio by [configuring the Snyk MCP Server with your ADE](#install-snyk-studio-for-ades-without-hooks-support).

## Install Snyk Studio for ADEs with hooks support

If your ADE supports hooks, complete the following steps to install Snyk Studio using an installer script.

### Prerequisites

* Python 3.8+
* Snyk CLI

### Clone the studio-recipes repository

Clone the [studio-recipes repository](https://github.com/snyk/studio-recipes) locally.

### Build the Snyk Studio installer

Run the following command to build the Snyk Studio installer script:

```bash
cd installer
python3 build_installer.py
```

### Run the installer script

For macOS and Linux:

```bash
bash ./dist/snyk-studio-install.sh [options]
```

For Windows:

```powershell
pwsh .\dist\snyk-studio-install.ps1 [options]
```

For advanced options and additional information, visit the [studio-recipes repository](https://github.com/snyk/studio-recipes/tree/main/installer#options).

## Install Snyk Studio for ADEs without hooks support

{% hint style="info" %}
The Snyk MCP Server is designed as a local MCP server, running on your system using the Snyk CLI to ensure local file access.

Snyk does not offer a hosted remote MCP server.
{% endhint %}

If your ADE does not support the default hooks-based approach, install Snyk Studio by configuring the Snyk MCP server in your target ADE.

## Prerequisites

Snyk recommends that you have:

* `npx`
* `Node.js` installed on your machine

If these are not available, you can manually add the Snyk CLI to the MCP server configuration. For instructions, see your coding assistant's official documentation.

## Configure the Snyk MCP server

Navigate to the MCP server configuration for the coding assistant. This often involves modifying a file called `mcp.json` or similar. Use the following snippet to configure the Snyk MCP server:

{% code overflow="wrap" expandable="true" %}

```
{
  "mcpServers": {
    "Snyk": {
      "command": "npx",
      "args": ["-y", "snyk@latest", "mcp", "-t", "stdio"],
      "env": {}
    }
  }
}
```

{% endcode %}

To validate the MCP server configuration, prompt your coding agent with natural language, for example, "scan my directory for security issues".

## Configure the Snyk MCP profile

Snyk supports the following tool profiles that let you control which tools are available to your AI agent. Profiles help you balance token cost and capability based on your needs.

|  Profile type  | Description                                                                                                                  |
| :------------: | ---------------------------------------------------------------------------------------------------------------------------- |
|      Lite      | The minimum set of essential security scanning tools. Ideal for keeping token use and context size low.                      |
| Full (default) | All stable tools. Provides comprehensive security coverage across code, dependencies, containers, IaC, and SBOMs.            |
|  Experimental  | Everything in the full profile, plus new tools under evaluation. These may change or be promoted to full in future releases. |

These tools are available for the following profile types:

<table><thead><tr><th width="269.86328125" align="center">Tool</th><th data-type="checkbox">Lite profile</th><th data-type="checkbox">Full profile</th><th data-type="checkbox">Experimental profile</th></tr></thead><tbody><tr><td align="center"><code>snyk_auth</code></td><td>true</td><td>true</td><td>true</td></tr><tr><td align="center"><code>snyk_code_scan</code></td><td>true</td><td>true</td><td>true</td></tr><tr><td align="center"><code>snyk_sca_scan</code></td><td>true</td><td>true</td><td>true</td></tr><tr><td align="center"><code>snyk_version</code></td><td>true</td><td>true</td><td>true</td></tr><tr><td align="center"><code>snyk_logout</code></td><td>true</td><td>true</td><td>true</td></tr><tr><td align="center"><code>snyk_trust</code></td><td>true</td><td>true</td><td>true</td></tr><tr><td align="center"><code>snyk_send_feedback</code></td><td>true</td><td>true</td><td>true</td></tr><tr><td align="center"><code>snyk_container_scan</code></td><td>false</td><td>true</td><td>true</td></tr><tr><td align="center"><code>snyk_iac_scan</code></td><td>false</td><td>true</td><td>true</td></tr><tr><td align="center"><code>snyk_sbom_scan</code></td><td>false</td><td>true</td><td>true</td></tr><tr><td align="center"><code>snyk_aibom</code></td><td>false</td><td>true</td><td>true</td></tr><tr><td align="center"><code>snyk_package_health_check</code></td><td>false</td><td>true</td><td>true</td></tr></tbody></table>

To set a profile, use either the `--profile` CLI flag or the `SNYK_MCP_PROFILE` environment variable CLI flag:

```
npx -y snyk@latest mcp -t stdio --profile=lite
```

{% code title="mcp.json" %}

```
{
  "mcpServers": {
    "Snyk": {
      "command": "npx",
      "args": ["-y", "snyk@latest", "mcp", "-t", "stdio"],
      "env": {
        "SNYK_MCP_PROFILE": "experimental"
      }
    }
  }
}

```

{% endcode %}

If a profile is not specified in setup, the profile defaults to full.

## Configure Secure at inception directives

The Secure at inception directives are used to guide agents to test for security issues at the time of code generation. To learn how to configure these directives with code examples, visit [Secure at inception directives](/integrations/snyk-studio-agentic-integrations/directives.md#secure-at-inception-rules).

## Configure Remediation directives

Remediation directives are commands that can be used to accelerate the remediation of pre-existing security issues. To learn how to configure these directives with code examples, visit [Remediation directives](/integrations/snyk-studio-agentic-integrations/directives.md#remediation-directives).

{% hint style="info" %}
Snyk maintains quickstart guides for some of the more common coding assistants. For detailed configuration steps of a specific coding assistant, visit Quickstart guides.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.snyk.io/integrations/snyk-studio-agentic-integrations/getting-started-with-snyk-studio.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.