Gemini CLI guide

You can add the Snyk MCP server to Gemini CLI 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 Gemini CLI

• Install the Snyk CLI

• Install the Snyk MCP

Install Gemini CLI

Install the Gemini CLI to your local machine.

Install the Snyk Extension or MCP Server in Gemini CLI

Get started with Snyk and Gemini CLI by using the Gemini extension, which installs the Snyk MCP Server. Run in your terminal:

gemini extensions install [email protected]:snyk/agentic-integration-wrappers

To confirm the extension was installed, run the following command in the Gemini CLI:

/extensions list

To install the Snyk MCP Server manually, use the method that best suits your operating system and local development environment.

Install with Node.js and npx

Create or edit the file ~/.gemini/settings.json in the root directory of your Project.

If you have the Node.js npx executable installed in your environment, add the following JSON snippet to the file:

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

Install with pre-installed Snyk CLI

Create or edit the file ~/.gemini/settings.json in the root directory of your Project.

If you have the Snyk CLI installed and accessible on your system path, include the following JSON snippet in the file. Specify the full path to the Snyk executable CLI:

{
  "mcpServers": {
    "snyk": {
      "command": "/absolute/path/to/snyk",
      "args": [
        "mcp",
        "-t",
        "stdio"
      ]
    }
  }
}

If the snyk command is not available, add it by following the instructions on the Installing or updating the Snyk CLI page.

Run /mcp list to confirm the Snyk MCP Server is connected.

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.

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

Examples

Scanning code and dependencies for security vulnerabilities

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

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

Gemini CLI indicates that this request is related to security vulnerability scanning and calls the Snyk MCP Server for various scans.

Gemini CLI Rules

To practice Secure at Inception, Snyk recommends adopting rules that align the LLM for secure code generation and workflows.

Append the following contents to the context file at ~/.gemini/GEMINI.md

# Project security best practices

- Always run Snyk Code scanning tool for new first party code generated.
- Always run Snyk SCA scanning tool for new dependencies or dependency updates.
- If any security issues are found based on newly introduced or modified code or dependencies, attempt to fix the issues using the results context from Snyk.
- Rescan the code after fixing the issues to ensure that the issues were fixed and that there are no newly introduced issues.
- Repeat this process until no issues are found.