Cursor

View Source

You can use Tidewave with Cursor.

Cursor allows you to place a file at .cursor/mcp.json, for configuration which is specific to your project. Given Tidewave is explicitly tied to your web application, that's our preferred approach.

Create a file at .cursor/mcp.json and add the following contents.

HTTP connection

Installing an MCP proxy

The HTTP integration of Cursor was shown to be unreliable in the past. For example, whenever you restarted your dev server, Cursor would not properly reconnect, leading to a frustrating user experience. If you run into such issues, consider using the MCP proxy.

{
  "mcpServers": {
    "tidewave": {
      "url": "http://localhost:$PORT/tidewave/mcp"
    }
  }
}

Where $PORT is the port your web application is running on. If the mcp-proxy command

See the MCP proxy documentation.

On macOS/Linux:

{
  "mcpServers": {
    "tidewave": {
      "command": "/path/to/mcp-proxy",
      "args": [
        "http://localhost:$PORT/tidewave/mcp"
      ]
    }
  }
}

On Windows:

{
  "mcpServers": {
    "tidewave": {
      "command": "/path/to/mcp-proxy.exe",
      "args": [
        "http://localhost:$PORT/tidewave/mcp"
      ]
    }
  }
}

Where $PORT is the port your web application is running on.

If you prefer, you can also add Tidewave globally to your editor by adding the same contents as above to the ~/.cursor/mcp.json file. If you have trouble locating such file, open up Cursor's assistant tab and click on the ⋯ icon on the top right and choose "Chat Settings". In the new window that opens, you can click "MCP" on the sidebar and follow the steps there.

If your application uses a SQL database, you can verify it all works by asking it to run SELECT 1 as database query. If it fails, check out our MCP Troubleshooting guide or Cursor's official docs.