Currents MCP

What currents-dev/currents-mcp MCP server does

The currents-dev/currents-mcp MCP server exposes Currents dashboard and CI test data to MCP-compatible coding agents. It is aimed at diagnosing Playwright test failures using recorded execution data rather than inferred results. Agents can inspect runs, spec instances, test results, failure context, error aggregates, historical performance, and test evidence such as screenshots, videos, traces, and attachments.

The server also supports operational workflows around Currents projects. Agents can create, update, enable, disable, and archive actions such as quarantine, skip, or tag rules. They can manage project webhooks, inspect pull-request cards, retrieve project terms, and create or link Jira issues through the organization’s Jira integration.

How it works

MCP clients invoke named Currents tools, with each tool handling a focused query or mutation. Read operations cover projects, runs, individual executions, test signatures, affected tests, errors, performance, and evidence. Date-range and filtering options are available for several project and execution queries.

Run operations include finding runs, retrieving run details, cancelling an in-progress run, resetting failed spec files for re-execution, deleting runs, and cancelling a run through a GitHub Actions workflow run ID and attempt number. Test debugging can be narrowed to a run, instance, or test level through failure-context retrieval.

Jira operations use the organization’s existing Jira integration. The available tools can list Jira projects and issue types, create an issue from a run test, or link an existing issue to one. Evidence retrieval returns signed download URLs grouped by test, according to the README.

Setup and configuration

Install currents-dev/currents-mcp MCP server with the project’s documented command:

npx -y @currents/mcp

Configure the CURRENTS_API_KEY environment variable with a Currents API key. The repository’s Cursor installation configuration passes this variable to the server. The supplied material does not document additional environment variables, authentication scopes, or account setup steps.

The README identifies Cursor and Claude as supported agent integrations. It does not provide client-specific configuration details beyond the Cursor installation link and environment-variable example.

Tools and capabilities

The documented tool groups include:

• Actions: list, create, retrieve, update, archive, enable, and disable project actions.
• Affected tests: inspect tests and executions influenced by actions within a date range.
• Projects and analytics: list projects, retrieve a project, inspect insights, terms, error metrics, spec-file performance, and test performance.
• Runs and debugging: query runs, inspect details, find runs, cancel or reset runs, delete runs, inspect spec instances, retrieve historical test results, and get failure context.
• Collaboration: list pull-request cards and create or link Jira issues.
• Artifacts and automation: retrieve test evidence, manage webhooks, and cancel GitHub Actions CI runs.
• Test identity: generate signatures from a project, spec-file path, and test title.

Limitations and notes

The currents-dev/currents-mcp MCP server depends on access to Currents data and a configured API key. The provided material does not state whether Currents accounts or particular features require payment. It also does not document permissions, rate limits, retention, webhook payloads, or the exact schemas for tool arguments and responses.

Actions that change or remove data include updating, disabling, archiving, cancelling, resetting, deleting, and creating resources. Review agent permissions before enabling these operations in an automated workflow. Jira tools likewise depend on an organization Jira integration being available.