Skip to content
Agentmart
Submit a tool

How to connect Playwright to Cursor

Playwright MCP, from microsoft, is listed as the vendor's own server and runs on your machine through npx. No API key is listed. The guide ends at Cursor's MCP logs, where connection errors show up. The config comes from the listing's install data and Cursor's documentation.

Updated Oct 26, 2026 · Built from catalog data; how we rank and grade

Checked against Cursor's documentation on Oct 26, 2026. Commands and config blocks are generated from the same install data as each listing page.

Before you start

  • Cursor installed and able to start.
  • Node.js with npx (the server starts with npx).
  • No API key is listed for Playwright MCP.

  1. 1. Check what you need

    Cursor starts this server with npx, which means Node.js must be installed. The node --version block checks that.

    Check that it is installed
    node --version
    • The listing names no required key.

  2. 2. Add Playwright MCP to Cursor

    A single JSON entry is all Cursor needs: it names npx as the command and passes the Playwright package as an argument. Put it in the project file or the home-directory file, depending on where you want it available.

    Add this to .cursor/mcp.json in the project, or to ~/.cursor/mcp.json for every project.cursor/mcp.json
    {
  "mcpServers": {
    "playwright-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@playwright/mcp@0.0.82"
      ]
    }
  }
}

  3. 3. Restart or reload if it does not appear

    Missing from Cursor's list? This step holds the docs' wording on restarts and the approval Cursor asks for before an agent calls a tool.

    • The docs do not say whether editing mcp.json needs a restart. They tell you to restart Cursor after updating files of a custom local server.
    • Cursor asks for approval before an agent uses an MCP tool unless you allowlist it.

Check that it works

Cursor logs connection errors in its Output panel, and a working server shows its tools there.

  • Open the Output panel (Cmd+Shift+U on macOS), choose MCP Logs, and look for connection errors. A working server lists its tools under Available Tools; agent mcp list shows connection state from the terminal.

Troubleshooting

A server fails or an npm-based server misbehaves after an update
Check the MCP Logs channel in the Output panel. For npm-based servers the docs suggest removing the server, running npm cache clean --force, and adding it again. Source

Reported by other users

Issues in the server's repository (microsoft/playwright-mcp) about installing or starting it, as of Oct 26, 2026. They are links, not fixes: open one to see whether it was resolved.

Security notes

  • Publisher: microsoft, listed as the vendor's own server; license Apache-2.0.
  • It runs on your machine with your user account's permissions, so it can reach any file or network resource you can. Read its source before you give it access: https://github.com/microsoft/playwright-mcp.
  • The listing declares no required keys; use a token with the narrowest scope if the service asks for one.
  • This listing has no security grade: Agent Market has not published security grades yet, so the choice is yours to make from the source and the permissions.

How we grade security · Trust policy

Servers and skills in this guide

Keep going with other Playwright servers, a comparison, or the general Cursor guide.

  1. 1
    Playwright MCP

    microsoftOfficial

    Playwright Tools.

    ★ 38.6KLast active Oct 22, 2026Local (stdio)Claude Code, Codex, VS Code, Cursor +2

Related

Sources

Cite this page

How to connect Playwright to Cursor. Agent Mart. https://agentmart.dev/guides/connect-playwright-to-cursor (last updated 2026-10-26)