Snyk CLI

Install

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

This is third-party code. Review the repository files before installing.

What it does

Snyk CLI checks open-source dependencies with snyk test, source code with snyk code test, Docker images with snyk container test and Terraform or Kubernetes files with snyk iac test. For each issue it shows severity, how the vulnerable module got in and fix guidance. snyk monitor saves a dependency snapshot and alerts you about new vulnerabilities. For AI agents there is an experimental snyk agent test with compact output, and snyk mcp -t stdio starts an MCP server with scanning tools and lite, full and experimental profiles.

Who it is for. For developers and security engineers who want the agent to scan code and dependencies with Snyk.

Example request

Scan my directory for security issues

Limitations

A Snyk account and sign-in are required; the MCP server provides the snyk_auth tool for that. Private repositories have test limits. Many projects must be built before dependency scanning, and the package manager must be on PATH. Scanning goes through the Snyk cloud, and access from Russia is unverified. The CLI does not accept external contributions.

How to disable. Delete the Snyk block from the client's MCP config. Remove a global CLI install with npm uninstall -g snyk.

Security check

• Reads code and dependency manifests and sends data to the Snyk cloud
• May run the project build during scanning

README in short

The README explains which project types Snyk scans and points to install and auth docs. It gives commands for dependencies, code, containers and IaC, monitoring mode and useful flags such as --json and --severity-threshold. It mentions agent mode and test limits. MCP server setup is documented in the Snyk Studio docs.

Related