Claude job search: Playwright setup and review checklist

Install a supported current Node.js LTS release and Claude Desktop. In Claude Desktop’s system-menu Settings, open Developer → Edit Config. Merge the following entry into the existing mcpServers object; keep other servers. Fully quit and restart Claude Desktop, then check that Playwright tools are available. A managed device may restrict local MCP servers.

{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": [
        "-y",
        "@playwright/mcp@latest",
        "--browser",
        "chrome",
        "--isolated"
      ]
    }
  }
}

This starts the official Microsoft package in an isolated Chrome session. Do not replace your personal browser profile or pass its cookies into a recording. The package requires Node.js 18 or newer; use a supported LTS version. No separate Playwright API key is required for the local server. Claude access and usage have their own terms and limits. Verify the installed package version before repeating this setup in production. Microsoft setup · Claude local-server configuration · Claude pricing.

Test with: “Use Playwright to open example.com and report its page heading. Do not fill or submit anything.” This tests the connection, not a job application.

For practice, use a fictional resume. For your actual search, provide only the personal details needed. Specify role, seniority, location, remote preference, work-authorization facts, a date window, and a few employer career pages. A vague query such as “new grad jobs this week” leaves location and eligibility unresolved.

Ask for direct listing links and the employer’s stated posting date. Missing date means unknown, not “this week.” Verify that the job remains open when you review it. Recency is a filter you choose; it is not evidence that your application will succeed.

Request up to ten matches, not exactly ten at any cost. Include the specific requirement, matching resume evidence and unresolved gaps. Import the returned CSV into your own spreadsheet. A Google Sheet is a separate destination: the browser tool does not automatically grant access or prove that a sheet was created.

Prepare fields and an original company-specific answer from your real experience and cited company information. Review the entire draft before entering it on an employer’s site. Only use automated form entry where the site permits it and you have approved sending your details there; pages can transmit data before the final button is pressed. Pause for authentication, CAPTCHA, certification and missing eligibility answers. You press Submit only after your own review.

LinkedIn prohibits unauthorized bots and scraping under its User Agreement. There is no verified “ten per day” safe limit for employer sites. Site-specific rules and technical compatibility still apply.

• Listing is still open, with the correct company and role.
• Date was read from the listing; unknown dates remain marked unknown.
• Resume evidence supports every qualification claimed.
• Graduation date, contact details and work authorization are correct.
• Company answer is specific and truthful; remove invented results.
• The selected resume file is correct and contains no unintended personal information.
• All fields, consent boxes and certifications have been reviewed.
• You decide whether to submit. No automated submission is part of this workflow.

Playwright can navigate, inspect, type and upload when the client and site support the action. It is not a universal application service. The sheet and rankings are outputs you ask the model to create and verify. Ten is a shortlist size, not a daily compliance allowance. The demo footage must show sample data and carry a visible “DEMO — SAMPLE DATA” label.

Sources checked 20 October 2026: Microsoft Playwright MCP, Claude Desktop local servers, MCP local setup, Claude plans, LinkedIn rules.