How to Add a Remote MCP Server to Cursor

How do I add a remote MCP server to Cursor?

Open Customize from the Cursor sidebar, find the MCP section, and add the server with its URL. On Cursor 3.9 and later that is where MCP servers live; older builds keep the same controls under Cursor Settings. Remote servers connect over native Streamable HTTP, so there is nothing to install in between, and because Cursor supports dynamic client registration, it triggers the browser authorization on its own the first time it connects — there is no token to paste.

Where the setting actually lives

Cursor consolidated MCP servers, plugins, skills, and rules into a single Customize page in version 3.9, released June 2026. Before that, the same controls sat under Cursor Settings.

That move is a common reason a setup walkthrough stops matching what is on screen. If your sidebar has no Customize entry, you are on an older build: either update Cursor, or open the command palette and search for "MCP" to jump straight to the settings regardless of which build you are running.

The config

Cursor reads remote servers from an mcpServers object, keyed by the name you want the server to appear under, with a url field:

{
  "mcpServers": {
    "my-server": {
      "url": "https://mcp.example.com/mcp"
    }
  }
}

A remote server needs no command and no arguments; Cursor connects over native Streamable HTTP with no proxy in between.

Worth knowing if you are moving between editors: url is the right key here, but the shape is not universal. VS Code nests servers under a servers root key rather than mcpServers; Gemini CLI and Qwen Code want httpUrl for Streamable HTTP, treating plain url as legacy SSE; and Antigravity specifies serverUrl. Devin Desktop (formerly Windsurf) accepts either serverUrl or url, so that one is more forgiving than it is often described. Copying a working Cursor block into another editor is still a reliable way to produce a server that saves cleanly and never appears — check the target's own key names first.

Authorization

When Cursor first connects to the server, it triggers that server's authorization flow in your browser. Approve the request and setup is complete.

Cursor supports dynamic client registration, so this is zero-config: Cursor registers itself and there is no token to paste.

What usually goes wrong

Symptom	Cause and fix
Can't find where to add an MCP server	Cursor moved this to Customize in the sidebar in version 3.9 (June 2026). On older builds, look under Cursor Settings instead.
The connection drops during a long session	Restart the chat session to reconnect. Cursor isolates server failures, so other servers keep working while one reconnects.
"Unauthorized" error	The authorization expired rather than the connection dropping. Re-authorize with the server and the OAuth flow will issue fresh tokens.

The middle row is the one people misread. A dropped connection in a long session is not a broken config — Cursor's per-server isolation means you will see one server go quiet while everything else keeps working, and a session restart brings it back.

A worked example

To make the above concrete, here is what it looks like with a real server. Tempreon is a hosted MCP server that gives whichever AI tool you are working in a persistent memory of how you work, so the example is a single URL with no credentials:

{
  "mcpServers": {
    "tempreon": {
      "url": "https://api.tempreon.com/functions/v1/tempreon-mcp/mcp"
    }
  }
}

Add that under Customize, and Cursor opens a browser tab to approve the connection the first time it connects. There is also a one-click install link and a full account-holder walkthrough in the Cursor setup doc.

Any other MCP server follows the same shape — swap the name and the URL.