currents-dev/currents-mcp

Give your AI coding agents full visibility into your CI test results. The Currents MCP Server connects tools like Cursor and Claude directly to your Currents dashboard, so agents can diagnose flaky tests, pinpoint failures, and act on real execution data -- without leaving your editor.
- Query runs, spec files, and individual test results from CI
- Surface error trends and performance metrics across your test suite
- Manage quarantine rules, webhooks, and project settings programmatically
- Let agents fix what's broken using actual test output, not guesswork
Tools
| Tool | Description |
| --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| currents-list-actions | List all actions for a project with optional filtering. |
| currents-create-action | Create a new action for a project. |
| currents-get-action | Get a single action by ID. |
| currents-update-action | Update an existing action. |
| currents-delete-action | Delete (archive) an action. |
| currents-enable-action | Enable a disabled action. |
| currents-disable-action | Disable an active action. |
| currents-list-affected-tests | List tests affected by actions (quarantine, skip, tag) for a project within a date range. |
| currents-get-affected-test-executions | Keyed on a test: lists the executions of one test that an action applied to, within a date range, with the run, branch and commit of each. |
| currents-get-action-executions | Keyed on an action: lists the test executions one rule was applied to, across every test it touched, within a date range. |
| currents-get-projects | Retrieves projects available in the Currents platform. |
| currents-get-project | Get a single project by ID. |
| currents-get-project-insights | Get aggregated run and test metrics for a project within a date range. |
| currents-list-pull-requests | List pull-request cards for a project (runs grouped by meta.pr.id). |
| currents-list-project-terms | List cursor-paginated project terms for one type (tag, branch, authorName, etc.). |
| currents-create-jira-issue | Create a Jira issue from a run test using the organization Jira integration. |
| currents-link-jira-issue | Link an existing Jira issue to a run test using the organization Jira integration. |
| currents-list-jira-projects | List Jira projects available for the organization integration. |
| currents-list-jira-issue-types | List Jira issue types and custom fields for a Jira project. |
| currents-get-runs | Retrieves a list of runs for a specific project with optional filtering. |
| currents-get-run-details | Retrieves a run: its status, commit, branch, groups and spec files, each with its instanceId, and how many files the run has by level, type and source (attachmentCounts). |
| currents-find-run | Find a run by query parameters. |
| currents-cancel-run | Cancel a run in progress. |
| currents-reset-run | Reset failed spec files in a run to allow re-execution. |
| currents-delete-run | Delete a run and all associated data. |
| currents-cancel-run-github-ci | Cancel a run by GitHub Actions workflow run ID and attempt number. |
| currents-get-spec-instance | Retrieves the raw result of one spec file execution by instanceId: each test's state and attempts, and the artifact URLs. |