Skip to content
↑↓navigate↵openescclose
Claude+372Whisper+228LangChain+168Codex+223NotebookLM+276DALL-E 3+192DeepL+249n8n+208Topaz Video AI+153LlamaIndex+161
Currents MCP Server logo
#30 · of 445 · by weekly downloadsMCP server

Currents MCP Server

Reads CI test results from Currents so an agent can diagnose flaky specs with real execution history.

0
SaveVisit website ↗
Rank
#30
of 445 · by weekly downloads
Weekly downloads
49K
npm + PyPI, last 7 days
GitHub stars
19
Repository on GitHub

Add it to your client

Official
Install
npx -y @currents/mcp
mcpServers
{
  "mcpServers": {
    "currents-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@currents/mcp"
      ]
    }
  }
}
Transport
stdio
Runtime
Node
Auth
Required
License
Apache-2.0
Stars
19
Tools
currents-get-projectscurrents-get-project-insightscurrents-list-affected-testscurrents-create-actioncurrents-list-pull-requests

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.

Comments(0)

Sign in to comment

No comments yet — be the first.

Similar MCP servers

Report this comment

Why are you reporting this?