MCPwell

Home › Clients › Cursor

Cursor MCP Setup

File locations and the placeholder JSON are from Cursor's MCP docs. The same material is on the Cursor page. A fact sheet's Cursor block is separate: it is generated from that server's registry entry, and the page links to it with the anchor #cursor on the Figma fact sheet as one example.

From the Cursor docs

Cursor's MCP docs say project config is .cursor/mcp.json and global config is ~/.cursor/mcp.json. The same page says Cursor supports stdio, SSE, and Streamable HTTP. These two examples are copied from that page. The names and URLs are Cursor's placeholders.

{
  "mcpServers": {
    "server-name": {
      "command": "npx",
      "args": ["-y", "mcp-server"],
      "env": {
        "API_KEY": "value"
      }
    }
  }
}
{
  "mcpServers": {
    "server-name": {
      "url": "http://localhost:3000/mcp",
      "headers": {
        "API_KEY": "value"
      }
    }
  }
}

The docs also say a stdio entry's type field is stdio, with command required. The remote example above is the one the docs print for HTTP or SSE.

What this page does not call verified

The endpoints below answered initialize and tools/list on 2026-10-17 with no credential. That is Verified on MCPwell. It is not a test inside this client. Config snippets further up that name a product are either copied from that client's docs or, on a fact sheet, generated from a registry entry. A registry snippet is not a statement that we opened the client and connected.

13 other checked URLs, including Figma, GitHub, Notion, and Stripe, returned HTTP 401. They are listed on the badge page and are not in the list above. Read the security checklist before you approve a local command or a sign-in.

FAQ

Does Verified on MCPwell mean this client connected?

No. It means initialize and tools/list returned a result for that public URL on the printed date. The check does not open Claude, Cursor, or VS Code.

Where do the JSON examples come from?

From the client document linked on the page. Server URLs on a fact sheet come from that server's registry entry, not from the client document.