Skip to content
Submit API / MCP
Currents logo

Currents API

Inspect CI test runs, failures and flaky tests using Currents execution data.

Source-reviewed overview · · Methodology

MCP implementations

  • Currents MCP · Official

    Bring Currents testing context into AI workflows.

    Currents: connection requirements
    Transport
    Local stdio; Streamable HTTP alternative
    Authentication
    CURRENTS_API_KEY locally; the HTTP documentation specifies a Bearer API key.

    Run the @currents/mcp package with a Currents API key. Follow the client-specific hosted instructions for browser sign-in where available.

    Documentation reviewed · Connection not runtime-tested.

Publisher evidence applies to the linked implementation. It does not establish endpoint health or access to every API operation.

What can you build?

Testing · CI/CD. Explore these collections for related tools and evaluation criteria.

Integration details

This profile contains a reviewed summary. Pricing, rate limits, authentication requirements, and SDK availability should be checked in the provider documentation before implementation. The linked provider documentation describes MCP support.

QUICK ANSWERS

Frequently asked questions

What is Currents?

Inspect CI test runs, failures and flaky tests using Currents execution data.

Where can I find Currents provider documentation?

Use the linked Currents provider documentation to check setup and supported capabilities.

Read documentation
Does Currents support MCP?

The reviewed provider documentation describes MCP support for Currents. Follow that documentation for setup and supported tools.

Read MCP documentation
How current is this Currents profile?

API Tracker summarizes available catalog information. Missing fields mean we have not established those details; they do not mean a feature is unsupported. Confirm current requirements with the provider.

Read our methodology

Search API Tracker

Curated starting points