Skip to directory

Currents MCP

Currents

Streamable HTTP; local stdio is also available39 documented tools8

About Currents MCP

Currents? MCP exposes CI test runs, test results, performance and failure evidence, and project/action/webhook management to AI clients.

What you can use it for

  • Summarize CI test runs and inspect failed tests
  • Identify flaky or slow tests and error trends
  • Retrieve screenshots, videos, traces, and other test evidence
  • Manage actions, webhooks, and Jira-linked test issues
Connection and setup
Hosting
Local; hosted remote endpoint also documented
Transport
Streamable HTTP; local stdio is also available
Endpoint
https://mcp.currents.dev/mcp
Authentication
CURRENTS_API_KEY environment variable for local server; hosted remote requests use Authorization: Bearer <Currents API key>. API keys grant organization resource access.

Requirements

  • Currents account and organization API key
  • Node.js/npm for local npx installation
  • Run/project identifiers may be required for some test-result workflows

Setup steps

  1. Create/manage an API key in Currents Dashboard under Organization > API & Record Keys.
  2. For local stdio, configure command npx with args [-y, @currents/mcp] and set CURRENTS_API_KEY in client secret environment.
  3. For remote use, configure https://mcp.currents.dev/mcp with Streamable HTTP and Authorization: Bearer <API key>.
  4. Restart/reload the client and verify by listing projects or reading a known test run.
  5. Review before allowing action, run cancellation/reset/deletion, Jira creation, or webhook mutation tools.
Tools 39

39 exact tool names match the maintained repository catalog. This batch verified against publisher documentation and repository, not by invoking the server’s tools/list endpoint.

  • currents-list-actions

    List project actions with optional filtering.

    01
  • currents-create-action

    Create a project action.

    02
  • currents-get-action

    Get an action.

    03
  • currents-update-action

    Update an action.

    04
  • currents-delete-action

    Delete/archive an action.

    05
  • currents-enable-action

    Enable an action.

    06
  • currents-disable-action

    Disable an action.

    07
  • currents-list-affected-tests

    List tests affected by project actions.

    08
  • currents-get-affected-test-executions

    Get execution details for an affected test.

    09
  • currents-get-affected-executions

    List executions where an action/rule applied.

    10
  • currents-get-projects

    List accessible projects.

    11
  • currents-get-project

    Get a project.

    12
  • currents-get-project-insights

    Get aggregated project metrics.

    13
  • currents-list-pull-requests

    List project pull-request cards.

    14
  • currents-list-project-terms

    List project terms such as tags, branches, and authors.

    15
  • currents-create-jira-issue

    Create a Jira issue from a run test.

    16
  • currents-link-jira-issue

    Link a Jira issue to a run test.

    17
  • currents-list-jira-projects

    List Jira projects for the organization integration.

    18
  • currents-list-jira-issue-types

    List issue types and custom fields.

    19
  • currents-get-runs

    List runs for a project.

    20
  • currents-get-run-details

    Get test run details.

    21
  • currents-find-run

    Find a run by query parameters.

    22
  • currents-cancel-run

    Cancel a run in progress.

    23
  • currents-reset-run

    Reset failed spec files for rerun.

    24
  • currents-delete-run

    Delete a run and associated data; destructive.

    25
  • currents-cancel-run-github-ci

    Cancel a Currents run using GitHub Actions run identifiers.

    26
  • currents-get-spec-instance

    Get debugging data for a test spec execution.

    27
  • currents-get-spec-files-performance

    Get spec file performance metrics.

    28
  • currents-get-tests-performance

    Get aggregated test performance metrics.

    29
  • currents-get-tests-signatures

    Generate a test signature.

    30
  • currents-get-test-results

    Get historical results for a test signature.

    31
  • currents-get-context

    Get failure context at run, instance, or test level.

    32
  • currents-get-errors-explorer

    Get aggregated error metrics.

    33
  • currents-get-test-evidence

    Collect CI artifacts including screenshots, videos, traces, and attachments.

    34
  • currents-list-webhooks

    List project webhooks.

    35
  • currents-create-webhook

    Create a project webhook.

    36
  • currents-get-webhook

    Get a webhook.

    37
  • currents-update-webhook

    Update a webhook.

    38
  • currents-delete-webhook

    Delete a webhook.

    39
Limitations and notes
  • The API key grants access to organization resources; protect it and do not commit it.
  • Some actions change or delete project data, cancel/reset runs, create Jira issues, or mutate webhooks.
  • Some workflows require a run ID from Currents dashboard.
Original sources
  • official documentation

    The maintained Currents repository enumerates 39 exact tools and the names match the catalog; current docs describe local and hosted Streamable HTTP operation with bearer API-key passthrough. Tool actions may read or modify test runs, webhooks, actions, Jira integration, and project data.

  • official tool reference

    The maintained Currents repository enumerates 39 exact tools and the names match the catalog; current docs describe local and hosted Streamable HTTP operation with bearer API-key passthrough. Tool actions may read or modify test runs, webhooks, actions, Jira integration, and project data.

Documentation checked 2026-10-28T13:19:36Z. Connection has not been runtime tested.