ConnectoryIndex of MCP servers — No. 060

Index / Guides / List

MCP servers for Cursor

Picks from our verified index for a Cursor coding workflow: code hosting, live docs, a browser, issues, errors and a database. Each entry includes the mcp.json snippet from the server's own docs.

Updated Oct 15, 2026 · 1 source

§1Where Cursor reads MCP config

Cursor reads servers from .cursor/mcp.json in a project (project-specific tools) or ~/.cursor/mcp.json in your home directory (tools available everywhere). Both use a top-level mcpServers object.

Cursor supports three transports: stdio (a local command Cursor manages), SSE and Streamable HTTP (a URL). Remote servers can use OAuth; Cursor asks for approval before running MCP tools by default.

~/.cursor/mcp.json — shape
{
  "mcpServers": {
    "local-server": { "command": "npx", "args": ["-y", "mcp-server"], "env": { "API_KEY": "value" } },
    "remote-server": { "url": "https://example.com/mcp" }
  }
}

§2How we picked

  • Official server from the vendor, or the reference implementation
  • A documented JSON config we could verify, so the snippet below is real
  • Useful inside a code editor: repo context, docs, a browser, issues, errors, data

§3The picks

  1. 01

    GitHub

    Official · Remote HTTP + local stdio · OAuth (remote) or Personal Access Token

    Repos, issues and pull requests without leaving the editor.

    ~/.cursor/mcp.json · derived
    {
      "mcpServers": {
        "github": {
          "url": "https://api.githubcopilot.com/mcp/"
        }
      }
    }
  2. 02

    Context7

    Official · Remote (HTTP) · API key recommended (Bearer header)

    Version-specific library docs so the agent stops guessing at APIs.

    ~/.cursor/mcp.json · derived
    {
      "mcpServers": {
        "context7": {
          "url": "https://mcp.context7.com/mcp"
        }
      }
    }
  3. 03

    Playwright

    Official · Local (stdio) · None (local browser)

    Lets the agent open your app in a real browser and check its work.

    ~/.cursor/mcp.json · from docs
    {
      "mcpServers": {
        "playwright": {
          "command": "npx",
          "args": [
            "@playwright/mcp@latest"
          ]
        }
      }
    }
  4. 04

    Chrome DevTools

    Official · Local (stdio) · None (local browser)

    Performance traces, network and console from a live Chrome.

    ~/.cursor/mcp.json · from docs
    {
      "mcpServers": {
        "chrome-devtools": {
          "command": "npx",
          "args": [
            "-y",
            "chrome-devtools-mcp@latest"
          ]
        }
      }
    }
  5. 05

    Linear

    Official · Remote (HTTP) · OAuth (remote server)

    Read the ticket, then update it when the change lands.

    ~/.cursor/mcp.json · derived
    {
      "mcpServers": {
        "linear": {
          "url": "https://mcp.linear.app/mcp"
        }
      }
    }
  6. 06

    Sentry

    Official · Remote (HTTP) · OAuth (remote server)

    Pull the actual error and trace into the fix.

    ~/.cursor/mcp.json · derived
    {
      "mcpServers": {
        "sentry": {
          "url": "https://mcp.sentry.dev/mcp"
        }
      }
    }
  7. 07

    Supabase

    Official · Remote (HTTP) · OAuth (remote server)

    The documented URL supports project scoping and read-only mode.

    ~/.cursor/mcp.json · derived
    {
      "mcpServers": {
        "supabase": {
          "url": "https://mcp.supabase.com/mcp?project_ref=<project-ref>&read_only=true"
        }
      }
    }
  8. 08

    Neon

    Official · Remote (HTTP) · OAuth (remote) or Neon API key

    Branches and SQL for Neon Postgres projects.

    ~/.cursor/mcp.json · derived
    {
      "mcpServers": {
        "neon": {
          "url": "https://mcp.neon.tech/mcp"
        }
      }
    }
  9. 09

    Figma

    Official · Remote (HTTP) · Figma account sign-in (remote server)

    Design context (frames, variables, components) from Figma.

    ~/.cursor/mcp.json · derived
    {
      "mcpServers": {
        "figma": {
          "url": "https://mcp.figma.com/mcp"
        }
      }
    }
  10. 10

    Vercel

    Official · Remote (HTTP) · OAuth (remote server)

    Manage Vercel projects and deployments and search Vercel docs.

    ~/.cursor/mcp.json · derived
    {
      "mcpServers": {
        "vercel": {
          "url": "https://mcp.vercel.com"
        }
      }
    }

Want several at once? Tick them in the Config Builder and copy one combined mcp.json.

§4Debugging

Cursor's docs point to the Output panel (Cmd+Shift+U) → "MCP Logs" for connection errors, auth problems and crashes. Servers can be toggled off without removing them.

§5FAQ

Where is Cursor's MCP config file?
Project config lives in .cursor/mcp.json; global config lives in ~/.cursor/mcp.json. Both use a top-level mcpServers object.
Does Cursor support remote MCP servers?
Yes. Cursor supports stdio, SSE and Streamable HTTP transports; remote servers are added with a url and can use OAuth.
How many MCP servers should I add?
Only the ones you use. Every server adds tools the model has to choose between, and Cursor lets you toggle servers off without deleting them.

§6Sources

  1. Cursor docs — Model Context Protocol ↗

Sources checked Oct 15, 2026. Spot something out of date? Tell us.

The Weekly Digest · Every Thursday

New MCP servers, weekly.

One short email: the newest servers, what changed in the ones you use, and one setup tip. No tracking pixels, no fluff.