Qodo guide
You can access Snyk Studio, including Snyk's MCP server, in Qodo to secure code generated with agentic workflows through an LLM. This can be achieved in several ways. When you use it for the first time, the MCP server will ask for trust and trigger authentication if necessary.
Prerequisites
Install Qodo
Add the Qodo extension to the VS Code or JetBrains IDE. For more details, see the official Qodo.ai page.
Install the Snyk MCP Server in Qodo
Install the Snyk MCP Server using the method that best suits your operating system and local development environment.
In the Qodo chatbox, click the Add MCP tools > Add new MCP. Provide the required details for the Snyk MCP server:
The MCP Server name
command: Eithernpxor the full path to the Snyk CLI.args: The Snyk MCP command to start the MCP server.
npx option:
{
"Snyk": {
"command": "npx",
"args": ["-y", "snyk@latest", "mcp", "-t", "stdio"]
}
}
full path option:
For the full path option, if the snyk command is not available, add it by following the instructions on the Installing or updating the Snyk CLI page.
The following example shows a Snyk MCP Server that was successfully configured.

For additional MCP configuration options on VS Code and troubleshooting, consult the official VS Code MCP server documentation.
Setting up the Snyk MCP Server
As a one-time setup, you may need to authenticate and trust the current Project directory. If required, the agentic workflow will likely manage this automatically.
These workflows are mostly automatically executed by the underlying model and the agentic code assistant, and you will need to approve them using a browser confirmation dialog. The process should look similar to this:

If you need to authenticate and trust the current directory, then proceed and complete the process.

Examples
Scanning for security vulnerabilities
In the chat, you can tag specific files or functions and ask Qodo to scan your code for safely deploying to production:
Qodo indicates that this request is related to security vulnerability scanning and calls the Snyk MCP Server for various scans.
Qodo is then able to gather all the security scanning results, both code (SAST) and dependencies (SCA), and based on recommendations and contextual information provided by the Snyk MCP Server, it is now able to provide code changes that address some or all of the security vulnerabilities that were found.
"Secure at inception" rules
To practice Secure at Inception, Snyk recommends adopting rules that align the LLM for secure code generation and workflows.
The following is a suggested instruction for Qodo best practices. Append the following contents to the rules file at best_practices.md:
Qodo Workflows
Create a custom Snyk workflow to scan and remediate security vulnerabilities. The following is a suggestion for Qodo workflows. Append the following contents to a Qodo agent file remediate-snyk-studio.toml:
Last updated
Was this helpful?

