-testing s

This MCP server exposes a Playwright-based browser automation service that your AI agent can interact with inside MCP-native IDEs. It enables the agent to launch browsers, navigate to pages, inspect DOM content, perform actions (clicks, form fills, selections), run inline Playwright code, capture screenshots, and run end-to-end test files. Use the Playwright server to explore a live UI, generate UI-driven tests, and execute those tests within your project context. Tools such as launch_browser, get_page_content, perform_action, execute_test_script, capture_screenshot, run_test_file, close_session, and list_sessions give you a rich set of capabilities for dynamic test generation, maintenance, and debugging in an agentic testing workflow.

Prerequisites:

• Node.js 18+ (LTS) installed on your system
• npm (comes with Node.js)
• An MCP-native IDE (Cursor, GitHub Codespaces, or compatible)

Install and set up locally:

# Clone the repository
git clone https://github.com/ElaMCB/mcp-testing-servers.git
cd mcp-testing-servers

# Install dependencies
npm install

# Install Playwright browsers (Chromium, example shown for Chromium)
npx playwright install chromium

# Build the project (if applicable for this server)
npm run build

Configure the MCP server in your IDE using the provided example:

{
  "mcpServers": {
    "playwright": {
      "command": "node",
      "args": ["./dist/servers/playwright/server.js"],
      "env": {
        "PLAYWRIGHT_BROWSERS_PATH": "0"
      }
    }
  }
}

If you are integrating into Codespaces or Cursor, place the above configuration in the appropriate MCP settings file as shown in the README examples.

Tips and notes:

• The PLAYWRIGHT_BROWSERS_PATH environment variable is set to 0 to ensure Playwright uses the bundled browsers in typical environments; adjust if you maintain a custom browser install path.
• Ensure your IDE has network access to the Node server built from your repository (the server.js path should exist after build).
• If you encounter issues with launching browsers, verify that the required browsers are installed (e.g., npx playwright install chromium) and that the environment supports GUI or headless operation as needed.
• This server focuses on Playwright-based browser automation; other MCP-enabled servers (Selenium, Jira, ADO, etc.) are planned, as described in the README, but not included in this configuration.
• For debugging, use list_sessions to confirm active sessions and inspect get_page_content for current DOM state before performing actions.