routermcp
← Back to Blog

QA/Test Engineer MCP Pack (2025) — Postman, Playwright, GitHub: Catch Regressions Early

• By RouterMCP Team

Run API and UI tests, capture failures, and file issues with context via MCP. Includes example flows and templates.

Test dashboard combining Postman results, Playwright screenshots, and GitHub issues.

QA/Test Engineer MCP Pack (2025) — Postman, Playwright, GitHub: Catch Regressions Early

TL;DR: Trigger API suites and E2E tests, then open actionable issues with logs and screenshots — from one endpoint.

Servers

  • Postman MCP. https://github.com/cappp/mcp-server-postman
  • Playwright MCP. https://github.com/LucaCappelletti94/mcp-server-playwright
  • GitHub MCP. https://github.com/modelcontextprotocol/servers/tree/main/servers/github

Flow

  1. Run Postman “smoke” on the PR preview URL.
  2. Run Playwright on critical journeys; collect failing step.
  3. File a GitHub issue with artifacts and labels.

Links

  • Pack docs: /packs/qa-engineer
  • Related posts: Developer pack (13), Benchmarking (07)

FAQ Q: Can we auto‑close flaky issues?
A: Tag suspected flake and require a stabilizing PR before re‑running.

Schema

Checklist (fast)

  1. Intent. 2) Title/meta. 3) Slug. 4) TL;DR. 5) Flow. 6) FAQ. 7) Links. 8) Images/alt. 9) Edit. 10) CTA.

CTA

  • Use the template: examples/packs/qa-engineer.mcp.json and the “PR checks” recipe (Postman + Playwright + GitHub labels).