Skip to main content

Connect Cursor

Cursor (1.0+) supports MCP servers via local configuration, with the same shape as Claude Desktop. This guide is nearly identical to the Claude Desktop one.

Prerequisites​

  • Cursor 1.0 or higher.
  • Whet Desktop installed and running (download).
  • The agent token Whet generated on first launch (read from Settings → Agent tokens in the workbench, or whet auth status).

Edit the config​

Open Settings → MCP (or manually edit ~/.cursor/mcp.json):

{
  "mcpServers": {
    "whet": {
      "url": "http://localhost:7891/mcp",
      "transport": "streamable-http",
      "headers": {
        "Authorization": "Bearer <agent-token>"
      }
    }
  }
}

For a Team / Enterprise deployment, swap the URL for your team's host (https://your-team.whet.so/api/mcp).

Activate the connection​

After saving, Cursor refreshes MCP connections on boot or when you reopen the config file. If it does not detect the change, fully quit (Cmd+Q) and reopen.

Verify​

In the Cursor chat, write something like:

Use the Whet MCP to list the latest posts from pipeline pp_a1b2c3.

Cursor asks for permission to invoke the tool and shows the arguments. If you confirm, it runs and returns the list.

Differences from Claude Desktop​

  • Cursor lets you define MCP servers per workspace in addition to the global one. If you want a specific repo to have its own Whet MCP (for example, pointing at staging), edit .cursor/mcp.json inside the workspace.
  • Cursor shows the arguments of each tool call before executing — useful to audit what the agent is about to do.

Other MCP clients​

Any client that supports Streamable HTTP MCP works with the same config. transport: "streamable-http" is the format the modern spec recommends — if your client only supports SSE or stdio, you will have to wait for an update (or use proxies like mcp-proxy).