> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/agent-security/agentic-security-with-snyk-studio/quickstart-guides/windsurf-guide.md).

# Connect Devin Desktop to Snyk

How to connect Devin Desktop to the local Snyk MCP server

Connect the Devin Local agent in Devin Desktop to Snyk tools to scan code and dependencies.

[Devin Desktop is the new name for Windsurf](https://devin.ai/blog/windsurf-is-now-devin-desktop). Cognition removed the legacy Cascade agent from Devin Desktop on September 8, 2026. Visit the [Devin Desktop changelog](https://docs.devin.ai/desktop/changelog).

{% hint style="info" %}
This procedure configures agent-invoked MCP access. It does not install Studio Secure at inception hooks, remediation commands, or package-health skills.

The Studio installer still accepts `--ade=windsurf` and writes legacy configuration under `.codeium/windsurf`. It does not configure the Devin Local MCP files. Devin Local uses skills rather than legacy Cascade workflows.
{% endhint %}

## Configure the local Snyk MCP server

Install [Devin Desktop](https://devin.ai/desktop) and complete the account and product setup in [Getting started with Snyk Studio](/agent-security/agentic-security-with-snyk-studio/getting-started-with-snyk-studio.md).

1. Authenticate the Snyk CLI:

   ```bash
   snyk auth
   ```
2. Add the Snyk MCP server to `.devin/mcp_config.local.json` in your repository. Preserve existing entries in `mcpServers`:

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

   Replace the `command` value with the absolute path to your Snyk CLI executable. This local configuration is not shared with your team. Visit [Devin MCP configuration](https://docs.devin.ai/cli/extensibility/mcp/configuration) for other scopes.
3. Start a new Devin Local session in the repository and ask the assistant to scan it:

   ```
   Scan this repository for code and dependency vulnerabilities. Summarize the findings before making changes.
   ```
4. Approve the Snyk MCP tool calls and complete Snyk authentication or repository trust requests when prompted. Inspect the tool calls and scan results to verify the connection.

## Remove the MCP connection

Remove the `Snyk` entry from the configuration file where you added it, then start a new assistant session. Preserve other MCP server entries.

If the connection fails, visit [Troubleshooting](/agent-security/agentic-security-with-snyk-studio/troubleshooting.md).

If the connection fails, visit [Troubleshooting](/agent-security/agentic-security-with-snyk-studio/troubleshooting.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/agent-security/agentic-security-with-snyk-studio/quickstart-guides/windsurf-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.