MCP server + Playwright reporter that builds a flakiness knowledge graph from test run history
MCP server + Playwright reporter that builds a flakiness knowledge graph from test run history. That is what the flakiness mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
A Playwright custom reporter + MCP server that builds a local flakiness knowledge graph from your test run history. Ask your AI agent which tests are unreliable, on which browser, and whether they're getting worse.
The server publishes 8 tools. What each one is for:
get_flaky_tests — db_path, min_runs?, limit?, since_days?get_test_history — db_path, test_id, limit?get_failure_patterns — db_path, since_days?get_slow_tests — db_path, limit?get_error_groups — db_path, min_failures?, limit?, since_days?get_flakiness_trend — db_path, test_id, days?cluster_semantic_error_trees — db_path, min_instances?, since_days?correlate_git_commit_flakiness — db_path, min_stable_runs?, since_days?Installation goes through your MCP client rather than a global install: point it at flakiness-graph-seed on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Flakiness's toolset — get_flaky_tests, get_test_history, get_failure_patterns and 5 more — is a fair guide to whether it matches your workflow. It is maintained by vola-trebla; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| get_flaky_tests | db_path, min_runs?, limit?, since_days? |
| get_test_history | db_path, test_id, limit? |
| get_failure_patterns | db_path, since_days? |
| get_slow_tests | db_path, limit? |
| get_error_groups | db_path, min_failures?, limit?, since_days? |
| get_flakiness_trend | db_path, test_id, days? |
| cluster_semantic_error_trees | db_path, min_instances?, since_days? |
| correlate_git_commit_flakiness | db_path, min_stable_runs?, since_days? |
{
"mcpServers": {
"flakiness-knowledge-graph": {
"command": "npx",
"args": ["-y", "flakiness-graph-seed"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.