Skip to content

Summary

Gives coding agents your CI test results from Currents: failed runs, flaky tests, error trends, quarantine rules and Playwright trace evidence.

Features

  • Query CI runs, spec files and individual test results
  • Fetch failure context for agents to fix broken tests
  • Manage quarantine, skip and tag rules and webhooks
  • Collect screenshots, videos and Playwright traces as shareable evidence
  • Create and link Jira issues from failed tests
  • Ships fix-failing-tests and collect-evidence agent skills

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it, filling in the environment variables with your own values.
  3. Restart the agent — the "Currents MCP Server" tools will be available.
{
  "mcpServers": {
    "currents-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@currents/mcp"
      ],
      "env": {
        "CURRENTS_API_KEY": "your-api-key"
      }
    }
  }
}

Description

The Currents MCP Server connects Cursor, Claude and other MCP clients to the Currents test-reporting dashboard so an agent can work from what actually happened in CI instead of guessing. It exposes dozens of tools for browsing projects, runs, spec files and individual test results, pulling aggregated error and performance metrics, and managing actions such as quarantine, skip and tag rules, plus webhooks. A get-context tool returns the errors, steps and files of a failed run, spec or test, which is the starting point for fixing broken tests. Evidence tools collect screenshots, videos, traces and attachments with signed download URLs and can build shareable links backed by Playwright traces, with a text digest, filmstrip and DOM snapshots. Jira tools create or link issues straight from a failed test. The server also publishes three agent skills as MCP resources: fix-failing-tests, collect-evidence and browser-evidence. It runs through npx with a Currents API key, is licensed Apache-2.0, and suits teams that already report Playwright, Cypress or similar suites to Currents and want agents to triage flaky tests and CI failures.

Covered in the Weekly

MCP: Chrome DevTools MCP

by Google Chrome DevTools team

Google's official MCP server for driving and inspecting a real Chrome browser — automation, debugging, and performance traces.

Featured

Qase test management over MCP: 36 task-oriented tools for cases, runs, results, defects and QQL search, hosted at mcp.qase.io or self-run with your own API token.

Testing and evaluation workbench for MCP server authors — inspect tools and prompts, debug OAuth step by step, and score behaviour across 16 client configurations before shipping.

CircleCI's official MCP server: pull build failure logs, hunt flaky tests, validate config, trigger and rerun pipelines, and roll back - in natural language from your IDE.

Browse all MCP servers →