Snyk Studio MCP

Snyk security scans of local code, dependencies, IaC, containers and SBOMs from a coding assistant

Official · Snyk Go Local · stdio SecurityDeveloper tools

76 popularity score ★ 58 ↓ 781k/wk

Connect your client

Local (npm)

Add in one click

Opens the app, which asks before it adds the server.

Or add it by command or config

Claude CodeTerminal
claude mcp add snyk-studio -- npx -y snyk@latest mcp -t stdio
Claude Desktopclaude_desktop_config.json
{
  "mcpServers": {
    "snyk-studio": {
      "command": "npx",
      "args": [
        "-y",
        "snyk@latest",
        "mcp",
        "-t",
        "stdio"
      ]
    }
  }
}
Cursor~/.cursor/mcp.json
{
  "mcpServers": {
    "snyk-studio": {
      "command": "npx",
      "args": [
        "-y",
        "snyk@latest",
        "mcp",
        "-t",
        "stdio"
      ]
    }
  }
}
VS Code.vscode/mcp.json
{
  "servers": {
    "snyk-studio": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "snyk@latest",
        "mcp",
        "-t",
        "stdio"
      ]
    }
  }
}
Codex~/.codex/config.toml
[mcp_servers.snyk-studio]
command = "npx"
args = ["-y", "snyk@latest", "mcp", "-t", "stdio"]
Gemini CLITerminal
gemini mcp add --scope user snyk-studio npx -- -y snyk@latest mcp -t stdio

Settings 2

SNYK_MCP_PROFILE Optional: Tool profile: lite, full (default) or experimental; same as --profile.
SNYK_TOKEN Optional: Snyk API token; when set, the snyk_auth browser sign-in is skipped and refused.

What it does

Snyk Studio MCP is Snyk's own MCP server. It is part of the Snyk CLI and starts with the `snyk mcp -t stdio` subcommand. It gives a coding assistant Snyk's scanners for the project on your disk: static analysis of source code, open-source dependency checks, infrastructure-as-code misconfiguration checks, container image scans, vulnerability checks of an existing SBOM, and detection of hard-coded secrets. It can also build an AI bill of materials for Python projects and look up the health and security record of a single package before you add it.

The assistant gets the findings back in the chat, so it can fix issues in code it has just written or in existing code. Snyk adds rule files it calls directives on top of the server, to nudge agents to scan new code as they write it.

Tools come in three profiles, set with `--profile` or `SNYK_MCP_PROFILE`. `lite` has the basic scans plus the account and trust tools. `full` is the default and adds container, IaC, SBOM, secret, AIBOM, package-health and breaking-change tools. `experimental` adds tools still under evaluation. The source checks two things before a scan runs: the folder must have been marked as trusted with `snyk_trust`, and the user must be signed in to Snyk. If Snyk Code is not turned on for the organisation, `snyk_code_scan` first asks the assistant to get the user's consent. Called again, it turns Snyk Code on for that organisation (internal/mcp/tools.go).

What it needs

RuntimeNode.js

A Snyk account (free sign-up exists). Node.js with npx for the documented `npx -y snyk@latest mcp -t stdio` command. Otherwise, an installed Snyk CLI configured by hand. Network access to Snyk's platform. Dependency scans may need the project's own build tools (for example Gradle or Maven) installed locally.

Limits

Local only: Snyk offers no hosted remote MCP server. Scans refuse to run in a folder that has not been trusted with `snyk_trust` and return an error asking for it. The `snyk_auth` tool will not run while `SNYK_TOKEN` is set. `snyk_aibom` handles Python projects only. `snyk_sbom_scan` needs components identified by PackageURLs. The README lists a `snyk_auth_status` tool that the current tool definitions (internal/mcp/snyk_tools.json) do not contain. Those definitions do contain `snyk_breakability_check` and `snyk_send_feedback`, which the README leaves out, so older CLI releases may differ. The repository does not accept public contributions.

Who it suits

Teams already on Snyk who want an assistant to scan the code it writes, and its dependencies, IaC and containers, without leaving the editor. It runs on your machine through the Snyk CLI and needs a Snyk account, so it does not suit anyone who wants scanning with no vendor account or offline. Use the `lite` profile to keep the tool list and context small. For testing a running web app or API instead of source, Snyk publishes a separate server, the Snyk API & Web MCP server (snyk/saw-mcp), which we also list.

Tools 14

snyk_auth
Signs the user in to Snyk; refused while SNYK_TOKEN is set
snyk_sca_scan
Checks a project's open-source dependencies for known vulnerabilities and licence issues
snyk_code_scan
Runs static analysis on source code to find security flaws
snyk_container_scan
Scans a container image's OS packages and app dependencies for vulnerabilities
snyk_iac_scan
Checks Terraform, Kubernetes, CloudFormation and ARM files for misconfigurations
snyk_sbom_scan
Checks the components in an existing SBOM file for known vulnerabilities
snyk_secret_scan
Looks for hard-coded keys, tokens and passwords in project files
snyk_version
Reports the installed Snyk MCP/CLI version
snyk_logout
Removes the locally stored Snyk token
snyk_aibom
Builds a CycloneDX AI bill of materials for a Python project
snyk_trust
Marks a folder as trusted so scans may run in it
snyk_send_feedback
Reports counts of issues the agent prevented or fixed in this run to Snyk
snyk_package_health_check
Looks up a package's vulnerabilities, maintenance and popularity in Snyk's package data
snyk_breakability_check
Assesses whether upgrading a package version is likely to break the project

Similar servers