Data as of

Serena for Cursor: Setup & Config

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

Serena Cursor configuration

  1. Choose Cursor configuration scope

    For Serena, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add Serena to Cursor

    Use the serena entry below in mcpServers. Keep Serena's documented stdio connection fields and your other Cursor entries.

  3. Check Serena in Cursor

    Serena: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

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

Serena in Cursor: stdio checks

  • Serena's uv tool install command installs a package, not a persistent MCP process. Confirm the upstream launch command before connecting Cursor.
  • Cursor must find uv for Serena. Enable the project/user entry in MCP settings and inspect its tools.
Tools
search_for_pattern, replace_content, list_dir

Serena — details. Cursor guide

Frequently asked questions

Cursor's Serena entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's serena example uses stdio.

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

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