Currents MCP Server

If you want an AI assistant working directly with Currents, the currents mcp server is the bridge. Enable AI Agents to fix Playwright test failures reported to Currents.

What Currents does

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.

Tools it exposes

Once connected, the assistant can call these 14 tools directly:

• 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 — Get execution details for a specific affected test (by signature) within a date range
• currents-get-affected-executions — List test executions where a specific action/rule was applied, 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)

Installing the currents mcp server

The server is distributed via npm as @currents/mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply one environment variable: CURRENTS_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Currents sits in that group, and the shape of its toolset — currents-list-actions, currents-create-action, currents-get-action among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This is a hosted server — you point your client at an endpoint rather than running a local process, so there is nothing to keep updated on your machine.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 14 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Currents.
• Written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the currents mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.