Releases: currents-dev/currents-mcp
Releases · currents-dev/currents-mcp
Release list
v2.3.1
2.3.1 (2026-05-19)
- build process improvements
- define LOGO_BASE64 and VERSION in vitest config (5b4a31c)
- add missing annotations param to get-test-results, enforce integer type on githubRunAttempt (3c5c1ba)
- add nullable to webhook headers and label fields to match OpenAPI spec (1e9223a)
- add nullable() to webhook headers and label to match OpenAPI spec (4cecfe3)
- align affected-tests tools with OpenAPI spec and add missing endpoint (#110) (287cd65)
- align list-affected-tests status param with OpenAPI spec (#106) (5fc9716)
- align MCP tools with OpenAPI spec (#47) (2820c7c)
- align Zod validation constraints with OpenAPI spec (3e31002)
- correct PR existence check to handle empty results (1f435e0)
- model name (326302e)
- use admin merge or auto-merge fallback for release PRs (1c0e32a)
Features
- add errors explorer tool (#63) (4bbb123)
- add listAffectedTests and getAffectedTestExecutions MCP tools (#98) (630006c)
- add missing annotations parameter to get-tests-performance tool (#89) (28844ff)
- add package.json and package-lock.json for dependency management (e6fddba)
- added cursor cloud agent dependabot analysis workflow (1ee1522)
- docs: automate README tools table synchronization and enhance validation tests (5572e3e)
- tests: add unit tests for MCP tool registration and validation (42c11a7)
- tests: enhance MCP tool validation with combined name length check (cfb14e1)
v2.3.1-beta.0
Immutable
release. Only release title and notes can be modified.
Release 2.3.1-beta.0
v2.2.4
v2.2.3
v2.2.1
v2.2.0
v2.0.0
Immutable
release. Only release title and notes can be modified.
Summary
- Adds new tools to allow agents to access full history of testing metrics and execution logs
| Tool | Description |
|---|---|
currents-get-projects |
Retrieves a list of all projects available. |
currents-get-run-details |
Retrieves details of a specific test run. |
currents-get-spec-instances |
Retrieves debugging data a specific execution of a test spec file. |
currents-get-spec-files-performance |
Retrieves spec file historical performance metrics for a specific project. |
currents-get-tests-performance |
Retrieves test historical performance metrics for a specific project. |
currents-get-tests-signatures |
Retrieves a test signature by its spec file name and test name. |
currents-get-test-results |
Retrieves debugging data from test results of a test by its signature. |
Use cases
The new tools should support use cases such as:
- "Please fix this test?" (Agent should retrieve last execution data just by knowing the test name and spec filename)
- "What were the top flaky tests in the last 30 days?" (Agent should retrieve test metrics from all projects in the date range)
- "What were the slowest specs in the last 7 days?" (Agent should retrieve spec metrics from all projects in the date range)
- "Please fix all my flaky tests" (Agent should investigate which tests are flaky, create a plan and execute it)