How do I connect Currents MCP Server to Claude?

The listing records `claude mcp add --transport stdio currents --env CURRENTS_API_KEY= -- npx -y @currents/mcp` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Desktop, Claude Code, Cursor as compatible clients.

Is Currents MCP Server free?

The listed licence is Apache-2.0. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.

What can Currents MCP Server do?

Currents MCP Server documents 38 tools to the agent, including currents-cancel-run, currents-cancel-run-github-ci, currents-create-action. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.

Currents MCP

Unclaimed

by currents-dev

Currents MCP Server

Install

$claude mcp add --transport stdio currents --env CURRENTS_API_KEY=<KEY> -- npx -y @currents/mcp

Set up this server

Compare servers My Stack

This server needs project-specific setup. Follow the project instructions; no reusable public launch command is available yet.

Project instructions

aicurrentsmcpplaywright

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

38 of 38 tools

Documented tools (38)

From project documentation. A server handshake does not verify each tool’s description or behavior.

currents-cancel-run

Cancel a run in progress.

currents-cancel-run-github-ci

Cancel a run by GitHub Actions workflow run ID and attempt number.

currents-create-action

Create a new action for a project.

currents-create-jira-issue

Create a Jira issue from a run test using the organization Jira integration.

currents-create-webhook

Create a new webhook for a project.

currents-delete-action

Delete (archive) an action.

currents-delete-run

Delete a run and all associated data.

currents-delete-webhook

Delete a webhook.

currents-disable-action

Disable an active action.

currents-enable-action

Enable a disabled action.

currents-find-run

Find a run by query parameters.

currents-get-action

Get a single action by ID.

currents-get-affected-executions

List test executions where a specific action/rule was applied, within a date range.

currents-get-affected-test-executions

Get execution details for a specific affected test (by signature) within a date range.

currents-get-context

Get test failure context for AI debugging at run, instance, or test level.

currents-get-errors-explorer

Get aggregated error metrics for a project within a date range.

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-get-projects

Retrieves projects available in the Currents platform.

currents-get-run-details

Retrieves details of a specific test run.

currents-get-runs

Retrieves a list of runs for a specific project with optional filtering.

currents-get-spec-files-performance

Retrieves spec files performance metrics for a specific project within a date range.

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.

currents-get-tests-performance

Retrieves aggregated test metrics for a specific project within a date range.

currents-get-tests-signatures

Generates a unique test signature based on project, spec file path, and test title.

currents-get-webhook

Get a single webhook by ID.

currents-link-jira-issue

Link an existing Jira issue to a run test using the organization Jira integration.

currents-list-actions

List all actions for a project with optional filtering.

currents-list-affected-tests

List tests affected by actions (quarantine, skip, tag) for a project within a date range.

currents-list-jira-issue-types

List Jira issue types and custom fields for a Jira project.

currents-list-jira-projects

List Jira projects available for the organization integration.

currents-list-project-terms

List cursor-paginated project terms for one type (tag, branch, authorName, etc.).

currents-list-pull-requests

List pull-request cards for a project (runs grouped by meta.pr.id).

currents-list-webhooks

List all webhooks for a project.

currents-reset-run

Reset failed spec files in a run to allow re-execution.

currents-update-action

Update an existing action.

currents-update-webhook

Update an existing webhook.

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about Currents MCP Server

How do I connect Currents MCP Server to Claude?: The listing records `claude mcp add --transport stdio currents --env CURRENTS_API_KEY=<KEY> -- npx -y @currents/mcp` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Desktop, Claude Code, Cursor as compatible clients.
Is Currents MCP Server free?: The listed licence is Apache-2.0. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can Currents MCP Server do?: Currents MCP Server documents 38 tools to the agent, including currents-cancel-run, currents-cancel-run-github-ci, currents-create-action. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.