> Markdown version of [Devin Desktop](https://vaadin.com/docs/v25/building-apps/agentic-development/mcp/supported-tools/devin-desktop). Section index: [llms.txt](https://vaadin.com/docs/v25/building-apps/llms.txt)

# Devin Desktop

Devin Desktop, formerly Windsurf, is Cognition’s AI-native IDE with built-in HTTP MCP support. Both of its agents, Devin Local, the default one, and the legacy Cascade agent, read MCP servers from the same configuration file.

## <a id="configuration"></a>Configuration

Add the following to `~/.config/devin/mcp_config.json` (on Windows, `%APPDATA%\devin\mcp_config.json`):

```json
{
  "mcpServers": {
    "vaadin": {
      "url": "https://mcp.vaadin.com/docs"
    }
  }
}
```

Create the file if it doesn’t exist. If it already has an `mcpServers` entry, add `vaadin` to it.

> **Note:** Devin Local can also read MCP servers from a project. To share the server with everyone who works on a project, add the same configuration to `.devin/mcp_config.json` in the project root and commit it.

## <a id="verify-the-setup"></a>Verify the Setup

1. Open the MCP section of the agent panel. It lists the Vaadin server and its tools.

2. Ask a question about Vaadin (e.g., "How to implement routing in Vaadin?")

3. The agent uses the Vaadin MCP server to provide accurate, documentation-based responses

Devin Local asks for your approval before it calls an MCP tool for the first time. You can allow a single tool, or every tool on the Vaadin server, for the current session or permanently.

## <a id="resources"></a>Resources

- [Devin Local MCP Configuration](https://docs.devin.ai/cli/extensibility/mcp/configuration)

- [Cascade MCP Documentation](https://docs.devin.ai/desktop/cascade/mcp)

- [Devin Desktop FAQ: Moving from Windsurf](https://docs.devin.ai/desktop/devin-desktop-faq)