Memungkinkan AI coding agent untuk melakukan query pada CI test runs, spec files, dan test results dari dashboard Currents guna mendiagnosis kegagalan serta flaky tests.
Juga dikenal sebagai currents-dev/currents-mcp, currents-mcp, @currents/mcp
- Stars
- 21
- Tools
- 43
- Unduhan, 30 hari
- 321.912
- Versi terbaru
- 1.0.0
- Commit terakhir
- 13 Nov 2026
- Lisensi
- Apache-2.0
Apa itu Currents MCP?
Currents adalah MCP server. Memungkinkan AI coding agent untuk melakukan query pada CI test runs, spec files, dan test results dari dashboard Currents guna mendiagnosis kegagalan serta flaky tests. Server ini menyediakan 43 tool, seperti currents-list-actions, currents-create-action, currents-get-action.
Ringkasan dibuat dari README proyek
Tentang Currents MCP server
Currents memungkinkan developer yang menggunakan AI agent untuk mendiagnosis kegagalan CI dan flaky tests secara langsung dari coding environment Anda. Dengan menghubungkan tools seperti Claude atau Cursor ke dashboard Currents, agent Anda mendapatkan visibilitas ke data eksekusi real, sehingga dapat bekerja lebih akurat tanpa sekadar menebak-nebak saat memperbaiki kode yang rusak. Koneksi ini memerlukan CURRENTS_API_KEY agar dapat berfungsi.
Developer menggunakan server ini untuk melakukan query pada runs tertentu, spec files, dan hasil test individual. Tools yang tersedia memungkinkan agent untuk mengelola project settings, menangani quarantine rules, serta memantau tren error atau metrik performa. Agent juga dapat berinteraksi dengan Jira untuk membuat atau menghubungkan issue ke test runs tertentu. Melalui command seperti currents-get-run-details dan currents-get-project-insights, agent dapat mengambil status, informasi commit, dan metrik agregat untuk memahami kesehatan dari sebuah test suite.
Apa yang bisa Anda lakukan dengannya
- 1Diagnosa kegagalan flaky testMinta AI agent Anda untuk menyelidiki mengapa test tertentu gagal dengan melihat riwayat eksekusi terbarunya.
- 2Analisis metrik performa projectMinta ringkasan tren error dan metrik performa untuk project tertentu dalam jangka waktu yang ditentukan.
- 3Kelola aturan test quarantineInstruksikan agent untuk memperbarui atau mengelola quarantine rules dan project settings lainnya secara terprogram.
- 4Integrasi kegagalan test dengan JiraBiarkan AI agent membuat Jira issue baru secara otomatis saat ia mengidentifikasi test run yang gagal.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal Currents MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal Currents MCP di Claude Code
$ claude mcp add currents-mcp -- npx -y @currents/mcpInstal Currents MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"currents-mcp": {
"command": "npx",
"args": [
"-y",
"@currents/mcp"
]
}
}
}Instal Currents MCP di VS Code
.vscode/mcp.json
{
"servers": {
"currents-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@currents/mcp"
]
}
}
}Instal Currents MCP di VS Code CLI
$ code --add-mcp '{"name":"currents-mcp","type":"stdio","command":"npx","args":["-y","@currents/mcp"]}'Instal Currents MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"currents-mcp": {
"command": "npx",
"args": [
"-y",
"@currents/mcp"
]
}
}
}Instal Currents MCP di Codex
$ codex mcp add currents-mcp -- npx -y @currents/mcpInstal Currents MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.currents-mcp] command = "npx" args = ["-y", "@currents/mcp"]
Instal Currents MCP di Gemini CLI
$ gemini mcp add -s user currents-mcp npx -- -y @currents/mcpInstal Currents MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"currents-mcp": {
"command": "npx",
"args": [
"-y",
"@currents/mcp"
]
}
}
}Tool Currents MCP 43
Terdeteksi dari 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 | — |
Tampilkan semua 43 toolTampilkan lebih sedikit tool
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 | — |
Konfigurasi
CURRENTS_API_KEY
| Nama | Deskripsi | Tipe |
|---|---|---|
| CURRENTS_API_KEY | — |
Pengecekan otomatis
Berjalan 12 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkauLolos
- Lisensi open source (OSI)Lolos
- Ada commit atau release dalam satu tahun terakhirLolos
- Nama package tidak mirip dengan package populerLolos
- Remote endpoint menggunakan HTTPSLolos
- Tools yang bersifat destruktif telah diberi labelLolos
- Tidak ada instruksi tersembunyi untuk modelLolos
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
README
Lihat di 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"
}
}
}
}
Pertanyaan tentang Currents MCP
Bagaimana cara menambahkan Currents MCP ke Claude Code?
Jalankan claude mcp add currents-mcp -- npx -y @currents/mcp di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan Currents MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Tool apa yang disediakan Currents MCP?
Server ini menyediakan 43 tool, termasuk currents-list-actions, currents-create-action, currents-get-action, currents-update-action, currents-delete-action.
Apa yang bisa dilakukan oleh Currents MCP server bagi AI agent?
Server ini menghubungkan coding agent ke dashboard Currents sehingga mereka dapat melakukan query pada runs, spec files, dan test results, memunculkan tren error, serta mengelola quarantine rules dan project settings.
Apakah agent bisa membuat atau menghubungkan issue Jira melalui server ini?
Ya, server ini menyertakan tools untuk membuat Jira issue dari sebuah test run, menghubungkan Jira issue yang sudah ada, serta menampilkan daftar Jira projects dan issue types.
Bisakah saya mengelola aturan quarantine dan skip dengan MCP server ini?
Ya, tersedia tools yang memungkinkan agent untuk melakukan list, create, update, delete, enable, dan disable aksi seperti quarantine, skip, dan tag rules untuk sebuah project.
Apakah mendukung Cursor dan Claude?
Currents MCP Server dirancang untuk menghubungkan tools seperti Cursor dan Claude ke dashboard Currents Anda.