Currents MCP Server: Setup for Claude, Cursor and Other Apps

• Shows why a CI run, spec file or test failed, with errors and steps

  Returns the errors, steps and files of the failed tests in a run, a spec file or a single test. It is the same content as the Fix button in the Currents dashboard, and the server tells the assistant to call it first when tests fail.

  Try: “Why did the checkout tests fail in the latest CI run on main?”

  Network · currents-get-context

• Lists recent test runs for a project, with filters

  Lists runs for a project and filters them by branch, tags, status, date range, author or free text such as a commit message or pull request title. It needs a project ID, which the assistant can look up first.

  Try: “Show the failed runs on the main branch from the last 3 days.”

  Network · currents-get-runs

• Shows one run: status, commit, branch and spec files

  Returns a run's status, commit, branch, groups and spec files, each with its instance ID, and how many attached files the run has.

  Try: “Give me the details of this run: https://app.currents.dev/run/abc123”

  Network · currents-get-run-details

• Finds a run from details such as a commit or build

  Looks up a run by query parameters instead of its ID, for when you know the branch, commit or CI build but not the run.

  Try: “Find the run for commit 4f2a9c1 in the web-app project.”

  Network · currents-find-run

• Shows the raw result of one spec file execution

  Returns each test's state and attempts for one spec file execution, plus links to its artifacts such as screenshots.

  Try: “Show every attempt of the tests in checkout.spec.ts for this run.”

  Network · currents-get-spec-instance

• Shows the history of one test across runs

  Returns past executions of a single test, found by its signature. You can filter by date, branch, tags, author, status or flaky state.

  Try: “Has the 'applies coupon' test failed on main in the last two weeks?”

  Network · currents-get-test-results

• Works out the ID used to look up one test

  Builds the unique signature for a test from the project, spec file path and test title. The history tools need this signature.

  Try: “Get the signature for the 'logs in' test in auth.spec.ts.”

  Network · currents-get-tests-signatures

• Ranks tests by failures, flakiness or duration

  Returns aggregated metrics per test for a date range. You can sort by failures, flakiness, duration or runs, and filter by spec, title, tags, branches or authors.

  Try: “Which 10 tests were flakiest this month?”

  Network · currents-get-tests-performance

• Ranks spec files by failure rate, flake rate or duration

  Returns metrics per spec file for a date range, sortable by average duration, failure rate, flake rate or timeout rate.

  Try: “Which spec files are the slowest on average this quarter?”

  Network · currents-get-spec-files-performance

• Groups errors across a project

  Returns aggregated error metrics for a project over a date range, so you can see which errors repeat most.

  Try: “What are the most common errors in our CI tests this week?”

  Network · currents-get-errors-explorer

• Shows project-wide run and test metrics

  Returns summary numbers for a project over a date range, such as how many runs passed or failed.

  Try: “Give me a pass/fail summary for the web-app project over the last 30 days.”

  Network · currents-get-project-insights

• Lists pull requests with their test runs

  Returns one card per pull request, with the runs grouped under it.

  Try: “Which open pull requests have failing test runs?”

  Network · currents-list-pull-requests

• Lists the tags, branches and authors in a project

  Returns the values used in a project for one type of term, such as tag, branch or author name. It uses paging for long lists.

  Try: “List all branch names that have test runs in this project.”

  Network · currents-list-project-terms

• Lists the Currents projects you can see

  Returns the projects available to your API key. Most other tools need a project ID from here.

  Try: “Which Currents projects do I have?”

  Network · currents-get-projects

• Shows one project

  Returns a single project by its ID.

  Try: “Show me the settings of project 'web-app'.”

  Network · currents-get-project

• Gets screenshots, videos and traces from a CI run

  Collects the files tests produced in a CI run, such as screenshots, videos, traces and attachments, with signed download links grouped by test.

  Try: “Get the screenshots and trace for the failed login test in this run.”

  Network · currents-get-test-evidence

• Makes a shareable link to a test's trace and summary

  Creates a link built from the test's Playwright trace. It carries a written summary of what the test did and where it failed, plus a filmstrip, screencast, page snapshots and network requests. The link opens without a Currents sign-in and expires.

  Try: “Create an evidence link for the failed checkout test so I can paste it in the pull request.”

  Write · currents-create-evidence-links

• Makes a public link to test results

  Creates a link that anyone can open without signing in, until it expires. It can hold the failure details for an agent that will fix the tests, or a full report for a person. The tool is meant to be used only when you ask to hand results to someone.

  Try: “Create a share link of this run's failures I can send to my teammate.”

  Write · currents-create-share-link

• Records a browser session you drove as a Currents session

  Saves a browser session as a Currents session so its evidence can be read and shared. It returns upload links for the files you declare. Uploading the files needs a shell on your machine.

  Try: “Record this browser session against my pull request so the trace can be reviewed.”

  Write · currents-create-session

• Adds log files or other files to a session or CI run

  Declares attachments on a session or a CI run, such as logs for a spec file, a test or the run itself. It returns upload links, and the files themselves are uploaded separately.

  Try: “Attach the Docker log to this run.”

  Write · currents-add-attachments

• Lists rules that quarantine, skip or tag tests

  Lists a project's actions, the rules that quarantine, skip or tag tests, with optional filtering.

  Try: “What quarantine rules are active on the web-app project?”

  Network · currents-list-actions

• Shows one rule

  Returns a single action by its ID.

  Try: “Show me the quarantine rule with ID act_42.”

  Network · currents-get-action

• Lists tests hit by quarantine, skip or tag rules

  Lists the tests that actions applied to in a date range.

  Try: “Which tests were quarantined in the last month?”

  Network · currents-list-affected-tests

• Shows when a rule was applied to one test

  Lists the executions of one test that an action applied to, with the run, branch and commit of each.

  Try: “When was the 'applies coupon' test last skipped by a rule, and in which run?”

  Network · currents-get-affected-test-executions

• Shows every test one rule was applied to

  Lists the test executions that one action touched, across all tests, in a date range.

  Try: “Show every execution the 'quarantine flaky' rule affected this week.”

  Network · currents-get-action-executions

• Creates a quarantine, skip or tag rule

  Creates a new action for a project. The rule then changes how matching tests run in later CI runs.

  Try: “Create a rule that quarantines the 'applies coupon' test.”

  Write · currents-create-action

• Changes an existing rule

  Updates an existing action's settings.

  Try: “Change the quarantine rule so it only applies to the main branch.”

  Write · currents-update-action

• Turns a disabled rule back on

  Enables an action that was disabled.

  Try: “Turn the quarantine rule back on.”

  Write · currents-enable-action

• Turns a rule off without deleting it

  Disables an active action.

  Try: “Disable the skip rule for the payments tests.”

  Write · currents-disable-action

• Archives a rule

  Deletes (archives) an action.

  Try: “Delete the old tagging rule.”

  Delete · currents-delete-action

• Stops a run that is in progress

  Cancels a run that is still running.

  Try: “Cancel the run on the release branch.”

  Write · currents-cancel-run

• Stops a run by its GitHub Actions run

  Cancels a run using the GitHub Actions workflow run ID and attempt number.

  Try: “Cancel the Currents run for GitHub Actions run 8123456, attempt 1.”

  Write · currents-cancel-run-github-ci

• Lets failed spec files in a run run again

  Resets the failed spec files in a run so they can be executed again.

  Try: “Reset the failed specs in this run so CI retries them.”

  Write · currents-reset-run

• Deletes a run and all its data

  Deletes a run together with everything stored for it.

  Try: “Delete the run from the broken test branch.”

  Delete · currents-delete-run

• Files a Jira issue for a failed test

  Creates a Jira issue from a test in a run, using the Jira integration your organization has set up in Currents.

  Try: “Create a Jira bug for the failed checkout test in this run.”

  Write · currents-create-jira-issue

• Links an existing Jira issue to a failed test

  Links a Jira issue you already have to a test in a run.

  Try: “Link PROJ-123 to the failed login test.”

  Write · currents-link-jira-issue

• Lists Jira projects available for the integration

  Returns the Jira projects your organization's integration can reach.

  Try: “Which Jira projects can I file test failures in?”

  Network · currents-list-jira-projects

• Lists Jira issue types and fields for a project

  Returns the issue types and custom fields of a Jira project.

  Try: “What issue types does the QA Jira project have?”

  Network · currents-list-jira-issue-types

• Lists a project's webhooks

  Lists all webhooks set up for a project.

  Try: “Which webhooks does the web-app project have?”

  Network · currents-list-webhooks

• Shows one webhook

  Returns a single webhook by its ID.

  Try: “Show the settings of the Slack webhook.”

  Network · currents-get-webhook

• Adds a webhook to a project

  Creates a webhook so Currents can send run events to a URL.

  Try: “Create a webhook that posts failed runs to https://example.com/hooks/ci.”

  Write · currents-create-webhook

• Changes a webhook

  Updates an existing webhook.

  Try: “Point the Slack webhook at the new URL.”

  Write · currents-update-webhook

• Deletes a webhook

  Deletes a webhook from a project.

  Try: “Delete the old Slack webhook.”

  Delete · currents-delete-webhook

Watch out for

• It can delete runs, rules and webhooks

  Delete tools remove a run and all its data, archive a rule or delete a webhook. Ask the assistant to confirm before it calls them. github.com

• It can change how tests run

  Creating, updating, disabling or enabling a rule can quarantine or skip tests in later CI runs. Read the rule before you approve it. github.com

• It can make public links to test results

  Share and evidence links open without signing in until they expire. Create one only when you mean to hand results to someone. github.com

• Your test data goes to your AI app

  Results, errors and CI details pass through whichever assistant you connect. The README tells you to vet any AI service you give access. github.com

Security advisories