Enterprise DNAEnterprise DNA

MCP Servers

currents-dev/currents-mcp

Currents MCP Server

Our verdict

Not reviewed yet

We have not reviewed currents-dev/currents-mcp yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About currents-dev/currents-mcp

Currents MCP Server is a TypeScript-based tool that provides a Model Context Protocol interface for interacting with Currents, a cloud platform for Cypress test execution. It enables AI agents to query test results, manage runs, and access dashboard data through standardized MCP endpoints.

Best for

Developers using Currents for Cypress testing who want AI agents to access test data

Use cases

  • Query test run status and results from Currents via an AI agent
  • Automate test result retrieval and analysis in CI/CD pipelines
  • Integrate Currents test data into AI-driven debugging workflows

Notes

17 stars on GitHub. Last updated 2026-05-29. Licensed Apache-2.0.

Pros

  • Lightweight and focused on a specific use case
  • Leverages the MCP standard for agent interoperability
  • Open source with TypeScript for easy customization

Cons

  • Very early stage with only 17 GitHub stars
  • Limited to Currents platform users
  • Requires understanding of MCP for effective use

Key facts

What we have checked

Days since the last commit
1
Checked GitHub
GitHub forks
15
Checked GitHub
GitHub stars
21
Checked GitHub
Days to a first reply on issues
73.8
Checked GitHub
Open issues
0
Checked GitHub
Releases in the last 90 days
4
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

How to use

How to set it up

As the listing publishes it. We have not run this install.

Install

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

Tools exposed

  • currents-list-actions
  • currents-create-action
  • currents-get-action
  • currents-update-action
  • currents-delete-action
  • currents-enable-action
  • currents-disable-action
  • currents-list-affected-tests
  • currents-get-affected-test-executions
  • currents-get-action-executions
  • currents-get-projects
  • currents-get-project
  • currents-get-project-insights
  • currents-list-pull-requests
  • currents-list-project-terms
  • currents-create-jira-issue
  • currents-link-jira-issue
  • currents-list-jira-projects
  • currents-list-jira-issue-types
  • currents-get-runs

Clients the listing names (not checked here)

Claude Desktop, Claude Code, Cursor, VS Code

Example client config

{
  "mcpServers": {
    "currents": {
      "command": "npx",
      "args": [
        "-y",
        "@currents/mcp"
      ],
      "env": {
        "CURRENTS_API_KEY": "your-api-key"
      }
    }
  }
}

Install

Add currents-dev/currents-mcp to your client

Not verified yet

Our lab has not run this server yet. "Config checked" on a client means the recipe matches that client's documented config format; it does not mean we ran it.

Claude Code

Config checked

Run in your terminal (remote server)

claude mcp add --transport http currents-dev-currents-mcp https://mcp.currents.dev/mcp

Version 1.0.0 · From the Official MCP registry, read · Format checked against Claude Code's config docs

Cursor

Config checked

Add to .cursor/mcp.json (remote server)

{
  "mcpServers": {
    "currents-dev-currents-mcp": {
      "url": "https://mcp.currents.dev/mcp"
    }
  }
}

Version 1.0.0 · From the Official MCP registry, read · Format checked against Cursor's config docs

VS Code

Config checked

Add to .vscode/mcp.json (remote server)

{
  "servers": {
    "currents-dev-currents-mcp": {
      "type": "http",
      "url": "https://mcp.currents.dev/mcp"
    }
  }
}

Version 1.0.0 · From the Official MCP registry, read · Format checked against VS Code's config docs

Codex

Config checked

Add to ~/.codex/config.toml (remote server)

[mcp_servers.currents-dev-currents-mcp]
url = "https://mcp.currents.dev/mcp"

Version 1.0.0 · From the Official MCP registry, read · Format checked against Codex's config docs

ChatGPT

Config checked

Fill in the Add custom MCP server form (remote server)

Where
ChatGPT Plugins > + > Add custom MCP server
Name
Currents
Description
Self-healing CI tests and proof of work for AI agents
Connection
Public endpoint
MCP server URL
https://mcp.currents.dev/mcp

Version 1.0.0 · From the Official MCP registry, read · Format checked against ChatGPT's config docs

  • Claude Desktop: Its config file takes local servers only; a remote server is added in the app as a connector.

Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.

Works with

What currents-dev/currents-mcp connects to

5 clients, each with how we know and when we checked.

Works withTypeHow we knowChecked
Claude CodeClientInstall recipe matches the client's documented formatRemote server, version 1.0.0Config checkedClaude Code docs
CursorClientInstall recipe matches the client's documented formatRemote server, version 1.0.0Config checkedCursor docs
VS CodeClientInstall recipe matches the client's documented formatRemote server, version 1.0.0Config checkedVS Code docs
CodexClientInstall recipe matches the client's documented formatRemote server, version 1.0.0Config checkedCodex docs
ChatGPTClientInstall recipe matches the client's documented formatRemote server, version 1.0.0Config checkedChatGPT docs

Stars and usage

How currents-dev/currents-mcp is growing

GitHub stars

21 to 21

stars. 28 Oct 2026 to 15 Nov 2026, 4 readings.

Source: GitHub. Checked .

Health and security

Is currents-dev/currents-mcp looked after, and what do its setup files show

Health score

80 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity30 of 30Last push 1 days ago
Releases15 of 154 releases in 90 days
Issue replies0 of 20First reply in 73.8 days (median)
Maintainer15 of 15Owned by an organisation
Official source20 of 20Official server

Security check static checks

100 out of 100

Reads what is published about the server: package advisories, licence, secrets in the documented setup and tool permissions. Nothing is installed or run, so this is not a security assessment. Checked by edna-static-v1 npm:@currents/mcp@2.7.0. What it checks

Licence: Apache-2.0

  • Note Asks for CURRENTS_API_KEY through environment variables.
  • Note The lab has not recorded this server's tool list yet, so tool permissions were not checked.
Tool permissions (1)
  • CURRENTS_API_KEY, environment variable it asks for (a secret)

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Days to a first reply on issues, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.