Currents MCP Server
Reads CI test results from Currents so an agent can diagnose flaky specs with real execution history.
Add it to your client
Officialnpx -y @currents/mcp
{
"mcpServers": {
"currents-mcp": {
"command": "npx",
"args": [
"-y",
"@currents/mcp"
]
}
}
}- Transport
- stdio
- Runtime
- Node
- Auth
- Required
- License
- Apache-2.0
- Stars
- 19
A flaky test cannot be diagnosed from one local run, because the signal is in how often a spec fails and under which conditions across many CI runs. Currents collects Playwright, Cypress and similar results from the pipeline, and this server exposes that history: runs, spec files, individual test executions, error trends and performance metrics over a date range. It also reaches the quarantine side of the platform — listing which tests an action currently affects, creating or disabling rules, and reading the executions where a rule fired — so an agent can quarantine a spec and later argue for releasing it with numbers. An API key scopes access to the project.
Similar MCP servers
CircleCI MCP
MCP serverInspect CircleCI runs, jobs, logs and test results from an agent
Checkly MCP Server
MCP serverReads synthetic monitoring checks and their failures, including Playwright script results.
BrowserStack MCP Server
MCP serverOpens sessions on BrowserStack's real device cloud and diagnoses failing test runs from the editor.

Comments(0)
Sign in to comment