Permite que los agentes de codificación con IA consulten ejecuciones de pruebas de CI, archivos de especificaciones y resultados de pruebas desde el dashboard de Currents para diagnosticar fallos y tests inestables.
También conocido como currents-dev/currents-mcp, currents-mcp, @currents/mcp
- Stars
- 21
- Herramientas
- 43
- Descargas, 30 días
- 321.912
- Última versión
- 1.0.0
- Último commit
- 13 nov 2026
- Licencia
- Apache-2.0
¿Qué es Currents MCP?
Currents es un MCP server. Permite que los agentes de codificación con IA consulten ejecuciones de pruebas de CI, archivos de especificaciones y resultados de pruebas desde el dashboard de Currents para diagnosticar fallos y tests inestables. Expone 43 herramientas, como currents-list-actions, currents-create-action, currents-get-action.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Currents
Currents permite a los desarrolladores que utilizan agentes de IA diagnosticar fallos de CI y tests inestables directamente desde su entorno de codificación. Al conectar herramientas como Claude o Cursor con tu dashboard de Currents, tu agente obtiene visibilidad sobre datos de ejecución reales, lo que le permite ir más allá de las conjeturas al corregir código roto. Esta conexión requiere una CURRENTS_API_KEY para funcionar.
Los desarrolladores utilizan este servidor para consultar ejecuciones específicas, archivos de especificaciones y resultados de pruebas individuales. Las herramientas disponibles permiten a un agente gestionar la configuración del proyecto, manejar reglas de cuarentena y monitorear tendencias de errores o métricas de rendimiento. También puede interactuar con Jira para crear o vincular incidencias a ejecuciones de prueba específicas. Mediante comandos como currents-get-run-details y currents-get-project-insights, un agente puede recuperar el estado, la información de los commits y métricas agregadas para entender la salud de una suite de pruebas.
Qué puedes hacer con él
- 1Diagnosticar fallos en tests inestablesPide a tu agente de IA que investigue por qué un test específico está fallando consultando su historial de ejecuciones recientes.
- 2Analizar métricas de rendimiento del proyectoSolicita un resumen de las tendencias de errores y las métricas de rendimiento de un proyecto específico durante un periodo de tiempo determinado.
- 3Gestionar reglas de cuarentena de testsInstruye a un agente para que actualice o gestione programáticamente las reglas de cuarentena y otras configuraciones del proyecto.
- 4Integrar fallos de tests con JiraHaz que un agente de IA cree automáticamente una nueva incidencia de Jira cuando identifique una ejecución de prueba fallida.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar Currents MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar Currents MCP en Claude Code
$ claude mcp add currents-mcp -- npx -y @currents/mcpInstalar Currents MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"currents-mcp": {
"command": "npx",
"args": [
"-y",
"@currents/mcp"
]
}
}
}Instalar Currents MCP en VS Code
.vscode/mcp.json
{
"servers": {
"currents-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@currents/mcp"
]
}
}
}Instalar Currents MCP en VS Code CLI
$ code --add-mcp '{"name":"currents-mcp","type":"stdio","command":"npx","args":["-y","@currents/mcp"]}'Instalar Currents MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"currents-mcp": {
"command": "npx",
"args": [
"-y",
"@currents/mcp"
]
}
}
}Instalar Currents MCP en Codex
$ codex mcp add currents-mcp -- npx -y @currents/mcpInstalar Currents MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.currents-mcp] command = "npx" args = ["-y", "@currents/mcp"]
Instalar Currents MCP en Gemini CLI
$ gemini mcp add -s user currents-mcp npx -- -y @currents/mcpInstalar Currents MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"currents-mcp": {
"command": "npx",
"args": [
"-y",
"@currents/mcp"
]
}
}
}Herramientas de Currents MCP 43
Detectado desde el READMEcurrents-list-actionscurrents-create-actioncurrents-get-actioncurrents-update-actioncurrents-delete-actioncurrents-enable-actioncurrents-disable-actioncurrents-list-affected-testscurrents-get-affected-test-executionscurrents-get-action-executionscurrents-get-projectscurrents-get-project
| 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 | — |
Mostrar las 43 herramientasMostrar menos herramientas
currents-get-project-insightscurrents-list-pull-requestscurrents-list-project-termscurrents-create-jira-issuecurrents-link-jira-issuecurrents-list-jira-projectscurrents-list-jira-issue-typescurrents-get-runscurrents-get-run-detailscurrents-find-runcurrents-cancel-runcurrents-reset-runcurrents-delete-runcurrents-cancel-run-github-cicurrents-get-spec-instancecurrents-get-spec-files-performancecurrents-get-tests-performancecurrents-get-tests-signaturescurrents-get-test-resultscurrents-get-contextcurrents-get-errors-explorercurrents-get-test-evidencecurrents-create-evidence-linkscurrents-create-sessioncurrents-add-attachmentscurrents-list-webhookscurrents-create-share-linkcurrents-create-webhookcurrents-get-webhookcurrents-update-webhookcurrents-delete-webhook
| 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 | — | |
| currents-get-run-details | — | |
| currents-find-run | — | |
| currents-cancel-run | — | |
| currents-reset-run | — | |
| currents-delete-run | — | |
| currents-cancel-run-github-ci | — | |
| currents-get-spec-instance | — | |
| currents-get-spec-files-performance | — | |
| currents-get-tests-performance | — | |
| currents-get-tests-signatures | — | |
| currents-get-test-results | — | |
| currents-get-context | — | |
| currents-get-errors-explorer | — | |
| currents-get-test-evidence | — | |
| currents-create-evidence-links | — | |
| currents-create-session | — | |
| currents-add-attachments | — | |
| currents-list-webhooks | — | |
| currents-create-share-link | — | |
| currents-create-webhook | — | |
| currents-get-webhook | — | |
| currents-update-webhook | — | |
| currents-delete-webhook | — |
Configuración
CURRENTS_API_KEY
| Nombre | Descripción | Tipo |
|---|---|---|
| CURRENTS_API_KEY | — |
Verificaciones automáticas
Ejecutado 12 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesibleAprobado
- Licencia de código abierto (OSI)Aprobado
- Commit o lanzamiento en el último añoAprobado
- El nombre del paquete no es similar a un paquete popularAprobado
- El endpoint remoto usa HTTPSAprobado
- Las herramientas destructivas están etiquetadasAprobado
- Sin instrucciones ocultas para el modeloAprobado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
README
Ver en GitHubCurrents MCP Server
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. |
currents-get-spec-files-performance |
Retrieves spec files performance metrics for a specific project within a date range. |
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-test-results |
Retrieves historical test execution results for a specific test signature. |
currents-get-context |
Call this first to find out why tests failed in CI, or to fix them: returns the errors, steps and files of the failed tests of a run, a spec file (instance) or one test — the same content as Fix in the Currents dashboard. |
currents-get-errors-explorer |
Get aggregated error metrics for a project within a date range. |
currents-get-test-evidence |
Collect evidence artifacts (screenshots, videos, traces, attachments) produced by tests in a CI run, with signed download URLs grouped per test. |
currents-create-evidence-links |
Create a shareable trace API link to a test attempt's evidence, served from its Playwright trace, and the URLs onto it: a markdown trace summary (the digest URL) of what the attempt did and what failed, a filmstrip, an animated screencast, DOM snapshots, network requests and attachments. |
currents-create-session |
Record a browser session you drove as a Currents session, so its evidence can be read and shared. |
currents-add-attachments |
Add attachments to a session from currents-create-session (send sessionId), or to a CI run (send runId): logs for a spec file, a test, or the run itself. |
currents-list-webhooks |
List all webhooks for a project. |
currents-create-share-link |
Create a public link to test results that anyone can open without signing in, until it expires. purpose "fix" is the failure context, for an agent that will fix the tests — the same content as currents-get-context, with flaky tests included and marked flaky. purpose "report" lists every test with its attempts and files, for a person; for a session it is the session page: status, error, attachments and trace. |
currents-create-webhook |
Create a new webhook for a project. |
currents-get-webhook |
Get a single webhook by ID. |
currents-update-webhook |
Update an existing webhook. |
currents-delete-webhook |
Delete a webhook. |
Skills
Agent skills that teach AI agents multi-step Currents workflows.
| Skill | Description |
|---|---|
browser-evidence |
Experimental: prove a change works in a browser you drove yourself, when there is no test to run. |
collect-evidence |
Show that work you implemented actually works, or demo it, from tests that ran in CI via Currents — a trace API link whose trace summary, filmstrip and accessibility snapshots read inside a comment, plus screenshots, attachments and videos. |
fix-failing-tests |
Fix tests that failed in CI, using the results Currents recorded — errors, steps, traces, screenshots and console output. |
The server publishes every skill as an MCP resource, so a connected agent can list and read them without a local copy:
skill://currents/collect-evidence/SKILL.md
skill://currents/collect-evidence/references/instrumentation.md
Agents that load skills only from disk still need a copy — put the skill
directory in the agent's skills location (e.g. .claude/skills/ for Claude
Code).
Setup
API Key
Get a Currents API key by following the instructions here.
Usage with Cursor
- Go to Cursor Settings > MCP > Enable
- Add the following to your
mcp.json.
{
"mcpServers": {
"currents": {
"command": "npx",
"args": ["-y", "@currents/mcp"],
"env": {
"CURRENTS_API_KEY": "your-api-key"
}
}
}
}
Preguntas sobre Currents MCP
¿Cómo agrego Currents MCP a Claude Code?
Ejecuta claude mcp add currents-mcp -- npx -y @currents/mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego Currents MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Qué herramientas proporciona Currents MCP?
Expone 43 herramientas, incluidas currents-list-actions, currents-create-action, currents-get-action, currents-update-action, currents-delete-action.
¿Qué permite hacer el MCP server de Currents a los agentes de IA?
Conecta a los agentes de codificación con el dashboard de Currents para que puedan consultar ejecuciones, archivos de especificaciones y resultados de pruebas, identificar tendencias de errores y gestionar reglas de cuarentena y configuraciones de proyectos.
¿Pueden los agentes crear o vincular incidencias de Jira a través de este servidor?
Sí, el servidor incluye herramientas para crear una incidencia de Jira a partir de una ejecución de prueba, vincular una incidencia de Jira existente y listar proyectos e tipos de incidencias de Jira.
¿Puedo gestionar las reglas de cuarentena y de omisión con este MCP server?
Sí, las herramientas permiten a los agentes listar, crear, actualizar, eliminar, habilitar y deshabilitar acciones como reglas de cuarentena, de omisión (skip) y de etiquetado para un proyecto.
¿Es compatible con Cursor y Claude?
El Currents MCP Server está diseñado para conectar herramientas como Cursor y Claude con tu dashboard de Currents.