Docs

Docs

Devin Desktop

Learn how to configure Devin Desktop, formerly Windsurf, to access Vaadin documentation through the Model Context Protocol server

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.

Configuration

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

Source code
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.

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.

Resources