Add the Bright Data MCP server to Cursor

{
  "mcpServers": {
    "bright-data": {
      "command": "npx",
      "args": [
        "-y",
        "@brightdata/mcp"
      ],
      "env": {
        "API_TOKEN": "<your API_TOKEN>"
      }
    }
  }
}

Scopes, env vars, OAuth and limits: Cursor MCP config guide

Cursor prompts you to sign in the first time a remote OAuth server is used. Bright Data runs locally and needs API_TOKEN. Replace the placeholder values above with your own before starting Cursor.

Ask Cursor for something Bright Data can do. Search, extract and navigate the web through Bright Data's scraping infrastructure. Approve the first tool call and check the result before allowing write actions automatically.

• · Remote servers take a url; local servers take command and args.
• · Values can reference ${env:NAME} so secrets stay out of the file.

How do I add the Bright Data MCP server to Cursor?

Run: { …. Cursor prompts you to sign in the first time a remote OAuth server is used.

Is this the official Bright Data MCP server?

Yes. It is published by Bright Data as io.github.brightdata/brightdata-mcp in the official MCP registry.

Does the Bright Data MCP server need an API key?

Yes. It runs locally and requires API_TOKEN.