Server facts
currents-mcp
Project
- Author
- currents-dev
- Repository
- github.com/currents-dev/currents-mcp
- Website
- currents.dev
- License
- Apache-2.0
- Category
- Browser Automation
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 21
- Last commit
- Data as of
Tags
- Playwright
- ai
- currents
- mcp
Overview
CI failure investigations in Currents can move from project selection to filtered runs, spec execution details, and individual test histories through coding agents such as Cursor and Claude. Developers can examine flakiness, duration, and error trends, then retrieve debugging context at the run, spec instance, or test level. Test signatures connect a project, file path, and title to historical results. An evidence tool gathers screenshots, videos, traces, and attachments from CI executions, returning temporary signed download links grouped by test.
Beyond inspection, the tools can cancel runs, reset failed specs for another execution, or permanently delete runs and their data. Action management covers rules for skipping, quarantining, or tagging matching tests, with queries showing which tests and executions those rules affected. Jira integration supports creating issues from run tests or linking existing issues, while webhook management configures notifications for run lifecycle events. The server uses Node and stdio, with a Currents API key supplied to the client configuration. Connecting an agent gives it access to that key, test results, and CI metadata, making agent selection and data handling relevant considerations.
currents-mcp setup notes
- currents-mcp records stdio only; confirm a network transport upstream before planning remote access.