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.

Installing an MCP proxy

The SSE integration of Cursor has shown to be unreliable. Whenever the connection drops to the SSE server, for example when you restart your dev server, Cursor does not properly reconnect, leading to a frustrating user experience. For this reason, we highly recommend to use an MCP proxy, despite the built in SSE support.

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

MCP Proxy

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.

SSE connection

As mentioned above, we do not recommend this approach at the moment.

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

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

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 Troubleshooting guide or Cursor's official docs.