1. Home
  2. Serena
  3. Serena for VS Code: Setup & Config

Data as of

Serena for VS Code: Setup & Config

Serena gives VS Code symbol-aware retrieval, editing, refactoring, and debugging capabilities through MCP.

Serena VS Code configuration

  1. Choose VS Code configuration scope

    For Serena, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

  2. Add Serena to VS Code

    Use the serena entry below in servers. Keep Serena's documented stdio connection fields and your other VS Code entries.

  3. Check Serena in VS Code

    Serena: Start in VS Code’s MCP controls; inspect output and trust prompts.

Config file · Workspace: .vscode/mcp.json

JSON
{
  "servers": {
    "serena": {
      "type": "stdio",
      "command": "uv",
      "args": [
        "tool",
        "install",
        "-p",
        "3.13",
        "serena-agent"
      ],
      "env": {}
    }
  }
}

Serena in VS Code: stdio checks

  • Serena's uv tool install command installs a package, not a persistent MCP process. Confirm the upstream launch command before connecting VS Code.
  • Make uv available in the workspace, container, or remote environment hosting Serena. Start through VS Code's MCP controls; inspect output and trust prompts.
Tools
search_for_pattern, replace_content, list_dir

Serena — details. VS Code guide

Frequently asked questions

For Serena, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.

VS Code's serena example uses stdio.

Serena's VS Code configuration invokes uv. Serena's uv tool install command installs a package, not a persistent MCP process. Confirm the upstream launch command before connecting VS Code.

Serena's stored list contains 6 tools, including search_for_pattern, replace_content, list_dir. Compare those names with VS Code's connected tool list; the stored list is not a live check.