Skip to content
Currents logo
Developer tools

Currents API

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

Source-reviewed overview · · Methodology
From capability to workflow

What can you build?

Use-case collection

Connect your coding agent

Bring project context and tools into your development workflow.

Explore this workflow

Editorial collections show where this provider fits. Collection membership does not establish support for every workflow or compatibility with other tools.

Before you connect

Find your starting point

Your appCurrents logoCurrents API

What can I do with this?

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

What credentials do I need?

Authentication and permission requirements have not been reviewed here. Check the provider documentation for the required keys, OAuth scopes and account access before sending a request.

Check provider documentation ↗

Can I test without an account?

Account-free API calls have not been verified for this profile. You can inspect specifications and prepare requests in the explorer without running them.

Requests run only when you choose to send them. Browser access depends on the provider’s CORS policy.

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.

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
What does the official Currents MCP implementation support?

Bring Currents testing context into AI workflows. Supported operations are limited to those exposed by this implementation. Publisher evidence reviewed 2026-10-21. This review does not establish a working connection.

View publisher evidence
How do I connect to Currents MCP?

Local stdio; Streamable HTTP alternative. 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 2026-10-21; not runtime-tested.

Read connection instructions
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
Keep exploring

Related to your workflow

Matched by shared capabilities or focused collections. These are options to evaluate, not verified integrations or drop-in replacements.

Search API Tracker

Curated starting points