MyMCPTools
Guides7 min read

Best MCP Servers for QA Engineers in 2026

QA engineers need access to test suites, bug trackers, browser automation, and build pipelines. These MCP servers connect your AI to Playwright, Sentry, GitHub, Jira, and your CI system — so testing and triage move faster.

By MyMCPTools Team·

Quality assurance is about context. When a bug report comes in, you need to understand what changed, what the test suite covers, what errors are surfacing in production, and whether CI passed — before you can even reproduce the issue. That context is spread across GitHub, Jira, Sentry, and your test runner output.

MCP servers close that gap. With the right setup, your AI can read recent pull requests, check Sentry for the error trace, find relevant test cases, and draft a reproduction script — in a single conversation. Here are the best MCP servers for QA engineers in 2026.

1. Playwright MCP Server — Browser Automation in Conversation

Playwright is the standard for end-to-end testing. The Playwright MCP server gives your AI direct control of a real browser — clicking, filling forms, navigating, and asserting page states — making it possible to explore bugs and draft test scripts interactively.

Key capabilities:

  • Navigate to any URL and interact with page elements
  • Fill forms, click buttons, and submit actions
  • Take screenshots and capture DOM snapshots
  • Generate Playwright test code from browser interactions

Best for: QA engineers who want AI to reproduce reported bugs step-by-step, draft e2e test cases from user stories, or identify flaky test root causes by replaying the failing interaction. Ask "reproduce this login bug" and get a working Playwright script.

2. Sentry MCP Server — Error Context for Faster Triage

Sentry captures production errors with full stack traces, breadcrumbs, and user context. The Sentry MCP server makes all that error data available in your AI conversation — so instead of copying error messages, your AI can read the full trace and suggest fixes or test coverage.

Key capabilities:

  • List recent issues by project, environment, and severity
  • Read full stack traces and breadcrumb events
  • Check error frequency trends and affected user counts
  • Link errors to source code releases and commits

Best for: QA engineers triaging production issues who want AI to analyze Sentry errors, identify the code path that caused them, and draft regression test cases to prevent recurrence. Critical for teams doing shift-left quality work.

3. GitHub MCP Server — Code and PR Context

Most bugs are introduced by code changes. The GitHub MCP server gives your AI access to pull requests, commits, and diffs — making it straightforward to correlate a bug report with the specific change that introduced it.

Key capabilities:

  • Read pull request diffs and review comments
  • Search issues for related bug reports or duplicate tickets
  • Check commit history for recent changes to affected files
  • Read test files to understand current coverage

Best for: QA engineers performing root cause analysis who want to know "what changed in the checkout flow this week?" before writing reproduction steps. Also useful for reviewing new PRs to identify testing gaps before they reach production.

4. Jira MCP Server — Bug Tracking in Your Workflow

Bug tracking context belongs in your AI conversation. The Jira MCP server makes your issue backlog searchable and readable — letting AI help you write clear bug reports, identify duplicate tickets, or understand acceptance criteria for features under test.

Key capabilities:

  • Search issues by JQL query, project, assignee, or status
  • Read issue details including description, comments, and attachments
  • Create and update issues with structured fields
  • List sprint contents and check issue priority

Best for: QA engineers who want AI to draft detailed bug reports from their observations, search for existing tickets before filing duplicates, or summarize what's in the current sprint's test scope.

5. GitHub Actions MCP Server — CI Pipeline Visibility

Understanding whether tests passed in CI is critical context for QA. The GitHub Actions MCP server exposes your workflow runs, job logs, and test outputs — so your AI can read why a build failed and suggest fixes without you hunting through log files.

Key capabilities:

  • List recent workflow runs and their status
  • Read job logs and step output for failed runs
  • Check which test files are part of which CI workflow
  • Identify flaky tests from run history patterns

Best for: QA engineers managing CI pipelines who want AI to diagnose test failures in GitHub Actions without manually scanning thousands of log lines. Ask "why did the nightly regression suite fail?" and get a specific answer.

6. Browserbase MCP Server — Cloud Browser Testing

Browserbase provides managed cloud browsers for automation. The Browserbase MCP server gives your AI access to cloud browser sessions — useful for cross-browser testing, running tests against staging environments, or investigating rendering issues in specific browsers.

Key capabilities:

  • Launch browser sessions across Chrome, Firefox, and Safari
  • Run Playwright or Puppeteer scripts in isolated cloud environments
  • Capture screenshots and videos of test sessions
  • Test against specific browser versions for compatibility

Best for: QA teams doing cross-browser compatibility testing who want to reproduce browser-specific bugs or run smoke tests against a staging deployment from within their AI conversation.

7. Datadog MCP Server — Performance Testing Context

Performance regressions are bugs too. The Datadog MCP server makes your APM data, latency metrics, and trace information available to your AI — so performance testing has real comparison data, not just anecdotal observations.

Key capabilities:

  • Query response time metrics before and after a deployment
  • Read distributed traces to identify slow spans
  • Check error rates and throughput by endpoint
  • Compare performance across environments

Best for: QA engineers running performance regression testing who want to quantify whether a new release degraded API response times or increased error rates compared to the previous version.

Recommended Stacks for QA Engineers

  • E2E test authoring: Playwright + GitHub + Filesystem (automate → check code → write test files)
  • Bug triage: Sentry + GitHub + Jira (error trace → code change → ticket)
  • CI debugging: GitHub Actions + GitHub + Sentry (pipeline failure → code context → production errors)
  • Performance QA: Datadog + GitHub + Jira (metrics → code change → document regression)
  • Full QA stack: Playwright + Sentry + GitHub + Jira + GitHub Actions — the complete context loop from user action to error to code to ticket

Browse all Browser Automation MCP servers on MyMCPTools. For security testing context, see Best MCP Servers for Security.

Recommended Tools

Better Stack

Free Plan

Get alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.

Start monitoring free →

1Password

14-day Free Trial

Store and inject API keys, payment credentials, tokens, and file access secrets into your MCP server configs. Trusted by 150K+ developers.

Try 1Password free →

🔧 MCP Servers Mentioned in This Article

🌍

Playwright MCP Server (ExecuteAutomation)

ExecuteAutomation's Playwright MCP Server is a community-maintained browser automation server (5,500+ GitHub stars) distinct from Microsoft's official microsoft/playwright-mcp — it leans further into test generation and visual workflows rather than pure accessibility-tree navigation. Beyond standard navigate/click/fill/screenshot tools, it can generate Playwright test code from a live browsing session, scrape full page content and structured data, execute arbitrary JavaScript in the page context, and drive API testing (GET/POST/PUT/PATCH/DELETE requests) alongside the browser tools. A standout feature is 143 real device presets for responsive testing — a single call like playwright_resize({ device: "iPhone 13" }) swaps in the correct viewport, user-agent, touch support, and device pixel ratio, and natural-language prompts like "test on iPad landscape" work directly through Claude. Install via `npm install -g @executeautomation/playwright-mcp-server`, Smithery, mcp-get, or the one-line `claude mcp add --transport stdio playwright npx @executeautomation/playwright-mcp-server` for Claude Code; VS Code one-click installers are also published. No API keys are required — it launches and drives a local Chromium/Firefox/WebKit browser directly. Choose this over Microsoft's official server when you specifically need auto-generated Playwright test scripts, JS execution, or device-emulation testing; choose Microsoft's for pure lightweight accessibility-tree page navigation. One maintenance fact the listings omit, checked against GitHub and npm on 2026-08-15: this repository has not been pushed since 2025-12-13 and npm 1.0.12 was published 2025-12-12, with 32 issues open. It is neither archived nor deprecated, so nothing warns you at install time — it installs, connects and works while its Playwright dependency drifts, whereas Microsoft's server ships continuously. Weigh the codegen, 143-preset device emulation and HTTP request tools against running an eight-month-old build. Note also that headless defaults to false on playwright_navigate, so it opens a visible browser window unless told otherwise, and that stdio-mode logging goes only to ~/playwright-mcp-server.log to keep the JSON-RPC stream clean.

Local📘
💻

GitHub MCP Server

authenticated access to the whole GitHub platform — repositories, files, branches, issues, pull requests, Actions runs, security alerts, discussions and notifications — from Claude, Cursor, VS Code, Copilot CLI and any other MCP host. There is no npm package for this server, and that trips up most people who try to install it: `@github/mcp-server` is not published to the npm registry, so any `npx` line you find for it will fail. GitHub ships it three other ways. The easiest is the hosted remote server at https://api.githubcopilot.com/mcp/, which needs no install at all — point an HTTP-transport MCP client at that URL and log in with OAuth (VS Code 1.101+, Claude Desktop, Claude Code, Cursor and Windsurf all support this). The second is the official Docker image ghcr.io/github/github-mcp-server, which is what the copy-paste command on this page runs; on github.com it now performs a browser-based OAuth login on first use and keeps the token in memory only, which is why the published Docker configs map a fixed loopback callback port (-p 127.0.0.1:8085:8085 with GITHUB_OAUTH_CALLBACK_PORT=8085) so the container can receive the callback. Prefer a token? Set GITHUB_PERSONAL_ACCESS_TOKEN instead — it takes precedence over OAuth, and the minimum useful scopes are repo, read:org and read:packages. The third is the native Go binary from the repository's releases, which needs no fixed port for the OAuth flow. GitHub Enterprise Server has no hosted option: use the local server with --gh-host or GITHUB_HOST set to your instance (include the https:// scheme — it defaults to http://, which GHES rejects). Toolsets can be narrowed with GITHUB_TOOLSETS, and an insiders channel is available at /mcp/insiders or via the X-MCP-Insiders header.

Auth required📘✓
🔧

Sentry MCP Server

The Sentry MCP Server is Sentry's official Model Context Protocol integration, purpose-built for human-in-the-loop coding agents like Claude Code, Cursor, and Windsurf. Rather than exposing every Sentry API endpoint, it focuses tightly on developer debugging workflows: searching and triaging issues, pulling stack traces and event details, inspecting performance traces, and querying project/team/org metadata in natural language. The primary deployment is a hosted remote MCP server at mcp.sentry.dev, built on Cloudflare's remote-MCP infrastructure, so most users connect with zero local setup — just add the remote URL to their client. For self-hosted Sentry instances or local development, a stdio transport is also available via npx @sentry/mcp-server, authenticated with a Sentry User Auth Token scoped to org:read, project:read, project:write, team:read, team:write, and event:write. AI-powered search tools (search_events, search_issues) translate natural-language queries into Sentry's query syntax, but require a configured LLM provider (OpenAI, Azure OpenAI, Anthropic, or OpenRouter) — all other tools work without one. Claude Code users can also install it as a plugin (claude plugin install sentry-mcp@sentry-mcp) for automatic subagent delegation whenever a conversation touches Sentry errors, issues, or traces. This turns "why did this deploy break in production" into a direct conversational debugging session instead of tab-switching into the Sentry dashboard.

Auth required📘✓
📋

Jira MCP Server

The Jira MCP server is Atlassian's official Remote MCP Server, giving AI assistants like Claude and Cursor direct, enterprise-grade access to Jira Software project management through natural-language interactions. Powered by Atlassian's Teamwork Graph and hosted on Cloudflare infrastructure, it requires no local process to run — authentication is handled via OAuth 2.1, making it the most secure way to connect AI to Jira in corporate environments. With this MCP server, product managers, engineers, and team leads can ask their AI to create and update Jira issues, transition ticket statuses through workflow stages, search with JQL (Jira Query Language), summarize sprint progress, view open epics and their child issues, retrieve assignee workloads, and bulk-triage backlogs. AI assistants can connect sprints to related Confluence documentation through Atlassian's graph layer, giving richer context for planning and retros. Enterprise customers including AT&T, NVIDIA, and Pfizer use Atlassian's MCP integration in production. Connect from Claude Desktop via Settings > Connectors, or add it to Claude Code with: `claude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcp/authv2`. Cursor and Windsurf users add the remote URL to their MCP config file. No install command needed — it's a fully hosted remote MCP server.

Auth required📘✓
💻

Cypress

End-to-end testing MCP for Cypress. Run test suites, inspect test results, generate test code, and debug failing tests with AI-powered analysis.

Local✓
🔧

GitHub Actions

Manage GitHub Actions workflows, runs, and secrets. Trigger workflows, inspect run logs, manage environment variables, and debug CI failures via AI.

Local✓
🌍

Browserbase MCP Server

Browserbase MCP and Stagehand MCP are the same server under two names, and this catalog lists both because people search for both — this page is the platform view, /servers/stagehand covers the natural-language automation layer that runs inside it. What Browserbase supplies is the browser itself: a headless Chrome session running in Browserbase's cloud rather than on the machine your agent is on, which is the reason to use it at all. The session is a real, addressable browser with its own residential-proxy and stealth configuration and a recorded replay you can watch afterwards, so an agent's browsing survives being run from a datacenter IP, and a failed run is debuggable after the fact instead of being a black box. Nothing renders on the developer's machine, so a long-running agent is not tied to a desktop staying awake. Browserbase's recommendation is the hosted server at https://mcp.browserbase.com/mcp over streamable HTTP — they operate it and absorb the model inference that the instruction-following tools require. Clients without HTTP transport connect via npx mcp-remote https://mcp.browserbase.com/mcp. Self-hosting installs @browserbasehq/mcp-server-browserbase from npm and needs BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID from your dashboard. Six tools are exposed — start and end for session lifecycle, navigate, act, observe and extract — and they are documented in detail on the Stagehand entry, because the act/observe/extract trio is Stagehand's model rather than Browserbase's. One thing to know before self-hosting: the browserbase/mcp-server-browserbase repository was archived on 2026-07-20 and its README now says it is kept for historical reference and should not be read as representative of the current production service. The npm package still installs and the star count on this page belongs to that archived repo; the hosted endpoint is the path Browserbase actually maintains.

Local✓
📊

Datadog MCP Server

The Datadog MCP Server is Datadog's official, vendor-hosted Model Context Protocol endpoint — not a package. Each Datadog site has its own URL of the form https://mcp.<your-site>/api/unstable/mcp-server/mcp (US1: mcp.datadoghq.com, EU1: mcp.datadoghq.eu), and OAuth 2.0 is the recommended way in; a Personal or Service Access Token as an Authorization bearer header is the documented fallback for CI, with DD_API_KEY plus DD_APPLICATION_KEY headers as a third option. Datadog ships first-party client integrations rather than expecting hand-written config: a Claude Code plugin (/plugin install datadog@claude-plugins-official, then /ddsetup and /ddtoolsets), a Claude connector from the Connectors Directory, plugins for Cursor, VS Code/Copilot, JetBrains and OpenCode, and a ChatGPT app in Preview for US1. Tools are grouped into toolsets selected with a ?toolsets= query parameter, and only `core` — logs, metrics, traces, dashboards, monitors, incidents, hosts, services, events, notebooks — loads by default; two dozen more cover alerting, DBM, DDSQL, RUM, profiling, security, Kubernetes, error tracking, feature flags, cost management and data observability, with apm, cases, code-exec and remote-actions in Preview and excluded from toolsets=all. Access requires the mcp_read or mcp_write role permission in addition to the normal resource permission, which is why a working connection can still return no data. Limits at time of writing are 50 requests per 10 seconds of tool-call burst and 50,000 tool calls per month, and the server is not GovCloud compatible.

Local📘✓
📋

Linear MCP Server

The Linear MCP server connects your AI assistant directly to Linear's project management platform via an officially hosted remote endpoint at mcp.linear.app — no local installation required. This is Linear's own first-party server, authenticated with OAuth 2.1 and centrally managed so you always run the latest version without updates. Available tools let you search issues by keyword, team, cycle, or filter; create new issues with title, description, and assignee; update status, priority, labels, and comments; and navigate Linear's project and cycle structure. In Claude Code, add it with: `claude mcp add --transport http linear-server https://mcp.linear.app/mcp`, then run /mcp to complete the OAuth flow. For older clients, use the mcp-remote bridge for backwards compatibility. Claude Desktop and Claude.ai users can connect via Settings > Connectors. Cursor and Codex have native support via their MCP config. Linear is used by thousands of engineering and product teams to plan, track, and ship software — the Linear MCP server brings that data into every AI-powered workflow without copy-paste or context-switching.

Auth required📘✓
💻

Jest

JavaScript testing framework MCP for Jest. Run tests, analyze coverage, inspect failures, and generate test code. Works with React, Node, and TypeScript projects.

Local✓

📚 More from the Blog

Guides

Best MCP Servers for Developers in 2026: The Complete Guide

Discover the top MCP servers that every developer should know about. From filesystem access to database queries, these Model Context Protocol servers supercharge your AI coding workflow.

8 min readGuides

Best MCP Servers for Data Engineering: Database, ETL & Analytics

Top MCP servers for data engineers and analysts. Connect your AI to PostgreSQL, BigQuery, Snowflake, and more for AI-powered data workflows.

7 min readTutorials

Getting Started with MCP: A Beginner's Guide to Model Context Protocol

New to MCP? Learn what Model Context Protocol is, how it works, and how to set up your first MCP server in under 5 minutes. Complete beginner's guide.

10 min read