Currents MCP Server

What it does

Currents is a hosted dashboard that records Playwright and other test runs from CI. This server, published by Currents itself, gives a coding agent the same data: runs, spec files, single test histories, error groupings, flakiness and duration rankings, and the screenshots, videos and traces a failed test left behind. The intended loop is that the agent pulls the failure context for a run with currents-get-context, fixes the code, and can then show its work with a trace link or a share link.

It also changes things in Currents. Tools can cancel, reset or delete runs, create and toggle actions (the rules that quarantine, skip or tag tests), manage webhooks, open or link Jira issues through the organization's Jira integration, record a browser session the agent drove, and attach logs to a session or run. The server also exposes three agent skills (fix-failing-tests, collect-evidence and an experimental browser-evidence) as MCP resources.

It runs two ways. Currents hosts it at https://mcp.currents.dev/mcp, where each person signs in with their own account and role, and the docs recommend this. The @currents/mcp npm package runs the same 43 tools locally over stdio with an organization API key. The two differ in what the agent sees: the hosted endpoint lists only the tools the connection was granted, while the local server lists every tool and lets the key refuse a call it does not allow with a 403 (docs: MCP tools and permissions). The package also points at CURRENTS_API_URL, which defaults to https://api.currents.dev/v1 and is not mentioned in the README (src/lib/env.ts at v2.7.0).

What it needs

A Currents account with projects that report CI runs to it. For the local server: Node.js 20 or later (engines in package.json) and a Currents API key in CURRENTS_API_KEY; the process exits on start without it. For the hosted endpoint: a browser sign-in, or an API key sent as a Bearer header for clients that cannot do OAuth. Codex also needs `codex mcp login currents`; ChatGPT needs developer mode on a Plus, Pro, Business, Enterprise or Education account, which a workspace admin may have to allow. The Jira tools need the organization's Jira integration set up.

Limits

A connection reaches one Currents organization; to use two, connect twice. With a Read Only key, writes are refused with 403, and a Read Only key on the hosted endpoint sees only the read tools, currents-create-evidence-links and the two Jira lookups. The hosted endpoint answers POST only (stateless Streamable HTTP) and cannot be used by a client that can only register itself dynamically; such a client must send an API key. The browser-evidence skill is marked experimental. The README says the hosted endpoint does no authentication of its own and needs a Bearer key, while the current docs describe an OAuth sign-in with the key as a fallback.

Who it suits

Teams that already send CI test results to Currents and want an agent to triage flaky or failing tests, compare a pull request's runs with main, or quarantine a test without opening the dashboard. Pick the hosted endpoint when your client supports remote servers: nothing is installed and access follows each person's role. The local package fits clients that can only start stdio servers, at the cost of a shared organization key. It is of no use without a Currents account; it reads Currents' records of tests and does not run tests itself.