"Information about playwrights or Playwright (context-dependent)" matching MCP servers:

An MCP server for running Playwright tests and reading structured results, failed test details, and attachment content, designed for AI agents doing test failure analysis.

Enables syncing Playwright, Allure, and JUnit test results into existing Kiwi TCMS test executions, with dry-run safety, automatic failure comments and attachments, and guarded raw RPC access.

Deterministic dependency + CVE context for AI coding tools, over the Model Context Protocol. A ~0.85 MB pure-Rust MCP server.

An MCP server that unpacks and structures Playwright trace.zip archives so AI agents can perform root-cause analysis on CI failures, with 16 focused tools for inspection, DOM/UI analysis, root-cause analysis, and performance analysis.

Enables auditing MCP servers' tools by their estimated context token cost, ranking verbose names, descriptions, and schemas before they consume the agent window. Can run as an MCP tool so agents can budget their own context.

Enables AI coding assistants to inspect GitHub Actions CI runs, diagnose failures with failed-step summaries and filtered job logs, read per-job coverage, and view pull request checks through read-only, allowlisted access.

Enables agents to run Playwright suites, diagnose failures from trace-level DOM, network and console evidence, and apply locator fixes that are re-run and reverted if still red. It also repeats failing tests for per-test flaky, regressed or broken verdicts and surfaces the same diagnosis and fix diffs in CI job summaries and PRs.

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

Enables AI agents and external systems to programmatically trigger and monitor Jenkins jobs, retrieve build status and logs via MCP standards.

A Model Context Protocol server for checking package versions and metadata across multiple package managers including npm, PyPI, Maven, NuGet, RubyGems, Crates.io, and Go modules.

Enables AI assistants to summarize Playwright test runs, identify flaky tests, heuristically triage failures, generate Playwright test stubs, and retrieve recent GitHub CI status through MCP tool calls.

Enables AI coding tools to validate local projects and publish or update applications to Bedengan App Hub via API, with automated checks and live deployment without manual approval.

Detects breaking changes in a TypeScript library's public API and recommends the semver bump, comparing two npm releases, git refs or a working tree. Each finding is graded proven or review-only.

A Model Context Protocol server for Bitbucket Cloud that lets agents read pull request diffs, comments, and pipeline logs, as well as write PR comments and edit PR details.

A Model Context Protocol server that monitors shadow-cljs builds and provides real-time build status updates for ClojureScript projects, allowing LLMs to verify build status after making code changes.

Deploys and manages projects on Swigs Cloud from any MCP client, turning folders or git repositories into live HTTPS sites in about two minutes.

Compacts noisy test, build, and cloud-log output before an AI agent reads it — dedupes repeats, collapses stack frames, folds Playwright retries, and renders CloudWatch/GCP JSON logs down to the signal. Typically 80–95% fewer tokens on failures. Tool: compact_output. Run: npx -y logslim logslim-mcp

Combines GitHub releases from multiple repositories into a single product release note, with context sources for LLM synthesis.

Publishes what an AI made — a page, a markdown or PDF doc, or a whole site — to a live HTTPS link. Runs locally over stdio from the @drop2run/mcp npm package, or hosted at https://mcp.dropto.run/mcp for chats that connect by URL.

Developers are constantly feeding context files to AI tools like Cursor, Windsurf, Copilot Workspace, and Claude Code. If your agent doesn't understand your real database schema, it writes code that fails in production. LintBase acts as the bridge. It connects directly to your database, reads the ground truth of your live documents, and generates structured context optimized for AI. 🤖 Stops AI

Lets any MCP-capable client connect to the public Codemagic REST API to list apps and teams, inspect build history, and optionally trigger or cancel builds and manage team settings. Runs locally over stdio with the user's own API token and configurable read-only, build, or administrative permission modes.

Aegis keeps Claude Code, Codex CLI and Antigravity on your project's rules via a zero-dependency Model Context Protocol (MCP) server (aegis-mcp), AGENTS.md / CLAUDE.md bootstrap, git pre-commit hooks, and CI governance (aegis check). It serves each agent just-in-time rules for the files it is about to edit, then enforces AST and repository invariants before commit and in pull requests.

Checks whether software dependencies (npm packages, GitHub Actions, MCP servers, Docker images) are alive, dormant, abandoned, archived, or deleted using dated observations from lastseen.dev.

Enables agents and CI pipelines to audit MCP servers and agent tool-chains by statically scanning repositories, local checkouts, tools/list exports, or live endpoints for risks such as destructive actions without confirmation, mismatched safety annotations, injection surfaces, credential or PII exposure, and unguarded command, path, or URL sinks. All checks are read-only and never execute the scanned code or call tools/call.

A temporary MCP server that scrapes Bitrise Insights using Playwright to fetch flaky test data, providing tools to query workspace and app test insights until the official API is released.

.FAF (Foundational AI-context Format) with 50+ tools - Only Persistent project context that integrates seamlessly with Claude Desktop workflows. Officially merged (#2759) Anthropic MCP server.

Enables AI agents to run reusable Playwright test fixtures against live deployments, providing structured test results, screenshots, and assertions.

Read-only Playwright CI results for coding agents: tells whether a failing test is new in this PR, already failing on main, or known flaky, with per-test history.

Turns JUnit XML test reports from CI into queryable QA metrics, letting AI assistants answer plain-English questions about failures, flaky tests, regressions pinned to a commit, root-cause clusters, and performance drift. Also generates ready-to-share QA health reports and self-contained HTML dashboards without logging into separate tools.

A comprehensive and efficient Model Context Protocol server for task management that works with Claude, Cursor, and other MCP clients, providing powerful search, filtering, and organization capabilities across multiple file formats.