currents-cancel-run
Cancel a run in progress. This will stop the run and mark it as cancelled. Requires runId.
LABSCO SUMMARY
The test data an agent needs to fix a failure, next to the controls that stop a flaky test blocking everyone while it works.
Most CI integrations stop at "here is the run". This one goes as deep as a fix actually needs: failure context formatted for a model, a stable test signature so history survives a rename, and flakiness ranked across the whole suite. The other half is action — quarantine rules, run resets and cancels, and a Jira issue created from the failing test — so an agent can change what CI does rather than only read what it did.
What it is
A server over the Currents dashboard covering CI test data end to end: projects and runs, individual test results and their history, spec-file and test performance, aggregated error metrics, the rules that skip or quarantine tests, Jira issue creation, and webhooks.
What you get
- Runs found and read: currents-get-runs filters by branch, tags with AND/OR, status, author and date range; currents-find-run returns the most recent completed run for a ciBuildId or a branch-and-tag combination; currents-get-run-details opens one
- currents-get-context returns test-failure context shaped for debugging at run, instance or test level, as JSON or Markdown, with a detail level and pagination
- currents-get-tests-signatures builds a test's stable signature from project, spec path and title, and currents-get-test-results returns that signature's history filtered by branch, tags, author, status and flakiness
- Trends across the suite: currents-get-tests-performance and currents-get-spec-files-performance rank by flakiness, failure rate, duration or executions, and currents-get-errors-explorer aggregates errors by message, category and target
- Actions — the rules that automatically skip, quarantine or tag tests — created, updated, enabled, disabled and archived, with currents-list-affected-tests and currents-get-affected-executions showing what each rule has actually caught
- Run control: cancel a run in progress, cancel one by GitHub Actions workflow run ID and attempt number, reset failed spec files for re-execution, or delete a run and its data outright
- Jira straight from a failing test: list the projects and issue types the organisation integration offers, then create an issue from a run test or link an existing one
- Webhooks per project listed, created, updated and deleted, with the run events that fire them
- currents-get-project-insights returns run and test metrics over a date range at a chosen resolution, and currents-list-pull-requests groups runs into pull-request cards
Requirements
A Currents API key in CURRENTS_API_KEY, launched over stdio with npx as @currents/mcp. You can also run the same server yourself as a Streamable HTTP server for remote connectors (npm run build, then npm run start:http, or Docker); it performs no authentication of its own, so each request must carry your Currents API key as a Bearer token. The server publishes its agent skills as MCP resources under skill://currents/, so a connected agent can read them without a local copy.
Setup effort
One command plus a key — npx -y @currents/mcp, then supply credentials
USE CASES
01
Debugging a CI failure the agent never saw happen
Find the run by branch or CI build ID, open it, then pull the failure context in Markdown for the tests that failed.
02
Deciding whether a test is flaky or genuinely broken
Turn the spec path and title into a signature, read that signature's history across branches and authors, and compare its flakiness against the rest of the suite.
03
Stopping a flaky test from blocking the branch
Create a quarantine or skip rule with a matcher and an expiry, watch which tests it catches, and disable it once the fix lands.
04
Seeing what is failing across the whole project
Aggregated error metrics by message and category, run and test metrics over a date range, and the spec files that cost the most time or fail most often.
05
Turning a failure into a tracked ticket
List the Jira projects and issue types on the organisation integration, then open an issue from the failing run test — or link one that already exists.
06
Rerunning only what failed
currents-reset-run puts the failed spec files back in play for the named machines; currents-cancel-run stops a run that is no longer worth finishing.
38 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
currents-cancel-run-github-ci
Cancel a run by GitHub Actions workflow run ID and attempt number. Optionally scope by projectId or ciBuildId. Requires githubRunId and githubRunAttempt.
currents-create-action
Create a new action for a project. Actions define rules that automatically skip, quarantine, or tag tests based on conditions like test title, file path, git branch, etc. Requires projectId, name, action array, and matcher object.
currents-create-jira-issue
Create a Jira issue from a run test using the organization Jira integration. Requires projectId, runId, testId, jiraInstallationId, jiraProjectId, and jiraIssueType. Optional customFields array.
currents-create-webhook
Create a new webhook for a project. Specify the URL to receive POST notifications, optional custom headers (as JSON string), events to trigger on (RUN_FINISH, RUN_START, RUN_TIMEOUT, RUN_CANCELED), and an optional label. Requires projectId and url.
currents-delete-action
Delete (archive) an action. This is a soft delete - the action will be marked as archived but not permanently removed. The actionId is globally unique.
currents-delete-run
Delete a run and all associated data. This is a permanent deletion. Requires runId.
currents-delete-webhook
Delete a webhook. This permanently removes the webhook. The hookId is a UUID.
currents-disable-action
Disable an active action. Changes the action status to disabled, temporarily preventing it from applying to tests. The actionId is globally unique.
currents-enable-action
Enable a disabled action. Changes the action status from disabled to active, making it apply to matching tests again. The actionId is globally unique.
currents-find-run
Find a run by query parameters. Returns the most recent completed run matching the criteria. Can search by ciBuildId (exact match) or by branch/tags. Supports pwLastRun flag for Playwright last run info. Requires projectId.
currents-get-action
Get a single action by ID. The actionId is globally unique, so projectId is not required. Returns full action details including matcher conditions and current status.
currents-get-affected-executions
List test executions where a specific action/rule was applied, within a date range. Uses cursor-based pagination. Requires actionId, date_start, and date_end.
currents-get-affected-test-executions
Get execution details for a specific affected test (by signature) within a date range. Returns individual test execution records with action info. Uses cursor-based pagination. Requires projectId, signature, date_start, and date_end.
currents-get-context
Get test failure context for AI debugging at run, instance, or test level. Supports json or md format, detail level, and pagination for failed tests. Requires run_id for run-level, or instance_id with optional test_id.
currents-get-errors-explorer
Get aggregated error metrics for a project within a date range. Supports filtering by error_target, error_message, error_category, error_action, tags, branches, authors, and groups. Supports grouping by target, action, category, or message. Returns error counts, affected tests and branches, with timeline data. Requires projectId, date_start, and date_end.
currents-get-project
Get a single project by ID. Returns project details including name, creation date, failFast setting, inactivity timeout, and default branch name.
currents-get-project-insights
Get aggregated run and test metrics for a project within a date range. Returns overall metrics and timeline data with configurable resolution (1h/1d/1w). Supports filtering by tags, branches, groups, and authors. Requires projectId, date_start, and date_end.
currents-get-projects
Retrieves projects available in the Currents platform. Supports cursor-based pagination with limit, starting_after, ending_before parameters, or set fetchAll=true for automatic pagination. This is a prerequisite for using any other tools that require project-specific information.
currents-get-run-details
Retrieves details of a specific test run. Requires a user-provided runId.
currents-get-runs
Retrieves a list of runs for a specific project with optional filtering. Supports filtering by branch, tags (with AND/OR operators), status (PASSED/FAILED/RUNNING/FAILING), completion state, date range, commit author, and search by ciBuildId or commit message. Requires a projectId. If the projectId is not known, first call 'currents-get-projects' and ask the user to select the project.
currents-get-spec-files-performance
Retrieves spec files performance metrics for a specific project within a date range. Supports ordering by avgDuration, failedExecutions, failureRate, flakeRate, flakyExecutions, fullyReported, overallExecutions, suiteSize, timeoutExecutions, or timeoutRate. Supports filtering by tags, branches, groups, and authors. Requires a projectId. If the projectId is not known, first call 'currents-get-projects' and ask the user to select the project.
currents-get-spec-instance
Retrieves debugging data from a specific execution of a test spec file by instanceId.
currents-get-test-results
Retrieves historical test execution results for a specific test signature. Supports filtering by date range, branch, tags, git author, test status (passed/failed/pending/skipped), run group, flaky status, and annotations. Requires the test signature. If the signature is not known, first call 'currents-get-tests-signatures'.
currents-get-tests-performance
Retrieves aggregated test metrics for a specific project within a date range. Supports ordering by failures, passes, flakiness, duration, executions, title, and various delta metrics. Supports filtering by spec name, test title, tags, branches, groups, authors, minimum executions, test state, and annotations. Requires a projectId. If the projectId is not known, first call 'currents-get-projects' and ask the user to select the project.
currents-get-tests-signatures
Generates a unique test signature based on project, spec file path, and test title. The test title can be a string or array of strings (for nested describe blocks). Requires a projectId. If the projectId is not known, first call 'currents-get-projects' and ask the user to select the project.
currents-get-webhook
Get a single webhook by ID. The hookId is a UUID. Returns full webhook details including url, headers, events, label, and timestamps.
currents-link-jira-issue
Link an existing Jira issue to a run test using the organization Jira integration. Requires projectId, jiraIssueKey, runId, testId, jiraInstallationId, jiraProjectId, and jiraIssueType. Optional comment and includeContextInComment.
currents-list-actions
List all actions for a project with optional filtering. Actions are rules that automatically modify test behavior (skip, quarantine, tag). Supports filtering by status (active/disabled/archived/expired) and search by name. Requires a projectId.
currents-list-affected-tests
List tests affected by actions (quarantine, skip, tag) for a project within a date range. Returns aggregated data grouped by test signature. Supports filtering by action types, action ID, status, and search. Requires projectId, date_start, and date_end. Preview endpoint: fields and path may change.
currents-list-jira-issue-types
List Jira issue types and custom fields for a Jira project. Requires jiraProjectId and jira_installation_id.
currents-list-jira-projects
List Jira projects available for the organization integration. Use returned project IDs as jiraProjectId when creating issues. Requires jira_installation_id.
currents-list-project-terms
List cursor-paginated project terms for one type (tag, branch, authorName, etc.). Supports search, sort direction, and starting_after or ending_before cursors. Requires projectId and termType.
currents-list-pull-requests
List pull-request cards for a project (runs grouped by meta.pr.id). Supports cursor pagination, runs_per_pr preview count, and filters by tags, branches, authors, and latest-run status. Requires projectId.
currents-list-webhooks
List all webhooks for a project. Webhooks allow you to receive HTTP POST notifications when certain events occur in your test runs: RUN_FINISH (run completed), RUN_START (run started), RUN_TIMEOUT (run timed out), RUN_CANCELED (run was cancelled). Requires a projectId.
currents-reset-run
Reset failed spec files in a run to allow re-execution. Requires runId and machineId array (1-63 machine IDs). Optionally supports batched orchestration.
currents-update-action
Update an existing action. The actionId is globally unique. You can update name, description, action array, matcher, or expiration date. All fields are optional.
currents-update-webhook
Update an existing webhook. You can update the url, headers (as JSON string), hookEvents array, or label. All fields are optional. The hookId is a UUID.
BEFORE YOU INSTALL
What to know first
Tools you get
38 tools when we connected; the project documents 39. The 39th is currents-get-test-evidence, which collects screenshots, videos and traces from a CI run; no documented flag holds it back, so it is likely in a newer release.
Requires
- npx on PATH
- CURRENTS_API_KEY in your environment
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @currents/mcpMCP Clients
Cursor, Claude Desktop
JSON
{
"mcpServers": {
"currents": {
"command": "npx",
"args": [
"-y",
"@currents/mcp"
],
"env": {
"CURRENTS_API_KEY": "<YOUR_CURRENTS_API_KEY>"
}
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --transport stdio currents --env CURRENTS_API_KEY=<YOUR_CURRENTS_API_KEY> -- npx -y @currents/mcp<YOUR_CURRENTS_API_KEY> is your Currents API key (create one in the Currents dashboard).
