MCP setup guide

Cursor

Cursor puts MCP servers in the editor's chat and agent workflows. Project installs are easy to share with a repository; global installs are available in every workspace.

Paths checked against the client's docs · November 2026

Surfaces

Desktop

Scope

Project or global

Project config.cursor/mcp.json
Installer agentcursor
1 / How it works

How Cursor handles MCP

Cursor puts MCP servers in the editor's chat and agent workflows. Project installs are easy to share with a repository; global installs are available in every workspace.

Project or global. Project scope keeps the server with the repository; global scope makes it available in every workspace.

Best for

Editor-led work where the MCP server belongs with the code.

Installer flag-a cursor
2 / Where it goes

Where the MCP config lives

The installer writes this file for you. Use the paths below when you want to inspect, edit, or remove a server by hand.

Project
.cursor/mcp.json
Global
~/.cursor/mcp.json

Project paths are relative to the workspace. Global paths are per user. On Windows, ~ means your user folder; use %USERPROFILE% in Explorer or PowerShell. A project config is shared with the team; a global config is personal.

3 / Install

Add a remote server

Start with a server in the MCP directory, or use your provider's endpoint. The examples use https://mcp.example.com/mcp so you can see the shape; replace it with the real URL.

  1. 01

    Find the endpoint

    Open a server page and copy its hosted endpoint. Do not use a local command or an npm package name for a remote server; those are different connection types.

    Open the MCP directory
  2. 02

    Run the installer

    Use the project config for a repository-specific server, or the global config for every workspace. The server name becomes example in the config.

    Cursor · project
    # Add this to Cursor MCP settings:
    {
      "mcpServers": {
        "example": {
          "type": "http",
          "url": "https://mcp.example.com/mcp"
        }
      }
    }
    Cursor · global
    # Add this to Cursor MCP settings:
    {
      "mcpServers": {
        "example": {
          "type": "http",
          "url": "https://mcp.example.com/mcp"
        }
      }
    }

    If the server page says SSE instead of HTTP, add --transport sse:

    SSE variant
    # Add this to Cursor MCP settings:
    {
      "mcpServers": {
        "example": {
          "type": "sse",
          "url": "https://mcp.example.com/mcp"
        }
      }
    }

    Cursor keeps MCP servers in a project config or a global config. The MCP settings panel shows whether a saved server is enabled.

    1. 1
      Open Cursor Settings

      Open Cursor Settings and choose Tools & MCP. The panel lists configured servers and their connection state.

    2. 2
      Add a custom server

      Choose Add custom MCP or New MCP Server, depending on the Cursor version. This opens the MCP config for the current project or the user-level config.

    3. 3
      Add the server entry

      Add the server under mcpServers. Use the project file for repository-specific tools or the global file for every workspace.

      Cursor MCP config
      {
        "mcpServers": {
          "example": {
            "url": "https://mcp.example.com/mcp"
          }
        }
      }
    4. 4
      Save, enable, and authenticate

      Save the file, return to Tools & MCP, and toggle the server on. If Cursor opens a provider sign-in, complete it before using the server.

    5. 5
      Verify the server in chat

      Start a new chat and ask which MCP tools are available. A server that is listed but disabled will not expose tools, even when its config is valid.

    Project config lives in .cursor/mcp.json. The global file is ~/.cursor/mcp.json. The same server can exist in both places; check both if the expected tools do not appear.

  3. 03

    Authorize if the provider asks

    The first connection may open a browser for OAuth. Sign in with the provider and approve only the scopes you need. If the server uses an API key, create it in the provider's dashboard and add it through the client's auth flow or config.

    Never paste a provider token into a project config you will commit. Prefer the client's secret store or a user-level config for credentials.

  4. 04

    Reload and verify

    Open the Customize page in Cursor and confirm the server is enabled.

    Then ask for a task, not a tool: “Find the open issues assigned to me” or “Summarize the latest release.” The client decides which advertised tool to call.

4 / Use

What changes in the chat

Once the server is connected, its tools appear in the client's tool list. You still talk to the agent normally; MCP is plumbing, not a different chat interface.

Read

“Find the customer notes mentioning the migration and summarize the blockers.”

Write

“Create a draft page with this outline, but do not publish it yet.”

Investigate

“Check the failed deployment and list the last three changes that touched it.”

Verify

“Which MCP tools do you have available for this task?”

If the agent ignores the server, check that the server is enabled and that its tools are approved. Some clients require a per-tool confirmation before the first call.

5 / Troubleshooting

When it does not connect

The server is missing

Confirm the file exists at the path above, the JSON or TOML is valid, and you restarted the client or opened a new session.

It connects but tools are empty

Enable the server in the client's MCP UI, approve its tools, and check that the provider has not revoked your token.

OAuth keeps reopening

Remove the server from the client, revoke the app's access in the provider's account settings, then add it again.

A project server is ignored

Some clients require you to trust the folder before loading project MCP config. Trust the repository, then start a new session.

6 / Notes

What to watch for in Cursor

  • Cursor requires you to enable a newly added server on the Customize page.
  • Use project scope for repo-specific tools and global scope for personal ones.
  • Remote servers may request OAuth the first time Cursor connects.
7 / Remove

Remove or reset the server

Remove the server when it is no longer needed, or reset it when a credential or connection state gets stuck.

  1. Open the Customize page in Cursor and find the server.
  2. Disable the server first, then remove it or delete its entry from .cursor/mcp.json.
  3. Reload the window and confirm that the server is gone.

Delete the server entry, restore it from the provider instructions, and complete sign-in again.

Sources

Official documentation

Client behavior changes. These links are the source of truth for paths, flags, and approval behavior.

Next setup guideVS Code