MCPwell

Home › Clients › Cursor

Cursor

The file locations and the placeholder JSON below are from Cursor's MCP docs. The Figma and Chrome DevTools blocks use the URL or package on those registry entries.

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.

Figma, remote

Cursor
{
  "mcpServers": {
    "figma": {
      "url": "https://mcp.figma.com/mcp"
    }
  }
}

Chrome DevTools, local

Cursor
{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ]
    }
  }
}

AWS is a local uvx package with an endpoint argument. See the AWS fact sheet.

Every fact sheet