Currents MCP Server
currents-dev/currents-mcp
Acesso direto a dados de CI/testes para agentes de IA diagnosticarem e corrigirem falhas
Ver no GitHubServidor MCP que conecta agentes de IA (Claude, Cursor) diretamente ao dashboard Currents para análise profunda de resultados de testes em CI/CD. Permite diagnosticar testes instáveis, identificar falhas e atuar sobre dados reais de execução sem sair do editor. Inclui gerenciamento programático de regras de quarentena, webhooks e métricas de desempenho.
Instalação
npx convez-ai currents-dev/currents-mcp1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Diagnosticar e corrigir testes flaky automaticamente com contexto real de falhas
- Analisar tendências de erros e métricas de desempenho da suite de testes
- Gerenciar regras de quarentena e webhooks via agentes de IA
- Integrar resultados de testes em workflows de CI/CD com acesso programático
Veredito

MCP bem estruturado para equipes que usam Currents e precisam de automação inteligente em CI/CD. Reduz o tempo de diagnóstico de falhas ao dar aos agentes visibilidade total de testes, mas requer conta ativa no Currents e integração já estabelecida em pipelines.
README
A tradução para o português deste README ainda está na fila.
Currents 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 | Get execution details for a specific affected test (by signature) within a date range. |
currents-get-affected-executions | List test executions where a specific action/rule was applied, 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-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 details of a specific test run. |
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 debugging data from a specific execution of a test spec file by instanceId. |
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 | 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-list-webhooks | List all webhooks for a project. |
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. |
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"
}
}
}
}
Claude
Run this command to add Currents MCP to Claude Code
claude mcp add --transport stdio currents --env CURRENTS_API_KEY=<KEY> -- npx -y @currents/mcp
Add the following to enable Currents MCP on Claude Desktop (edit claude_desktop_config.json file):
{
"mcpServers": {
"currents": {
"command": "npx",
"args": ["-y", "@currents/mcp"],
"env": {
"CURRENTS_API_KEY": "your-api-key"
}
}
}
}
⚠️ Notice
By connecting AI tools (e.g., via MCP) to Currents, you are granting them access to your API key, test results and CI metadata. It is your responsibility to vet any AI agents or services you use, and to ensure they handle your data securely.