MCP.so
登录

Currents MCP Server

@currents-dev

关于 Currents MCP Server

Currents MCP Server

基本信息

分类

其他

许可证

Apache-2.0

运行时

node

传输方式

stdio

发布者

currents-dev

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "currents": {
      "command": "npx",
      "args": [
        "-y",
        "@currents/mcp"
      ],
      "env": {
        "CURRENTS_API_KEY": "your-api-key"
      }
    }
  }
}

工具

38

List all actions for a project with optional filtering.

Create a new action for a project.

Get a single action by ID.

Update an existing action.

Delete (archive) an action.

Enable a disabled action.

Disable an active action.

List tests affected by actions (quarantine, skip, tag) for a project within a date range.

Get execution details for a specific affected test (by signature) within a date range.

List test executions where a specific action/rule was applied, within a date range.

Retrieves projects available in the Currents platform.

Get a single project by ID.

Get aggregated run and test metrics for a project within a date range.

List pull-request cards for a project (runs grouped by meta.pr.id).

List cursor-paginated project terms for one type (tag, branch, authorName, etc.).

Create a Jira issue from a run test using the organization Jira integration.

Link an existing Jira issue to a run test using the organization Jira integration.

List Jira projects available for the organization integration.

List Jira issue types and custom fields for a Jira project.

Retrieves a list of runs for a specific project with optional filtering.

Retrieves details of a specific test run.

Find a run by query parameters.

Cancel a run in progress.

Reset failed spec files in a run to allow re-execution.

Delete a run and all associated data.

Cancel a run by GitHub Actions workflow run ID and attempt number.

Retrieves debugging data from a specific execution of a test spec file by instanceId.

Retrieves spec files performance metrics for a specific project within a date range.

Retrieves aggregated test metrics for a specific project within a date range.

Generates a unique test signature based on project, spec file path, and test title.

Retrieves historical test execution results for a specific test signature.

Get test failure context for AI debugging at run, instance, or test level.

Get aggregated error metrics for a project within a date range.

List all webhooks for a project.

Create a new webhook for a project.

Get a single webhook by ID.

Update an existing webhook.

Delete a webhook.

概览

What is Currents MCP Server?

The Currents MCP Server connects AI coding agents (like Cursor and Claude) directly to the Currents dashboard, giving them full visibility into CI test results so they can diagnose flaky tests, pinpoint failures, and act on real execution data without leaving the editor.

How to use Currents MCP Server?

Obtain a Currents API key, then configure the server in your MCP client. For Cursor, add the @currents/mcp command and CURRENTS_API_KEY environment variable to mcp.json. For Claude Desktop, edit claude_desktop_config.json similarly. For Claude Code, run claude mcp add with the same parameters.

Key features of Currents MCP Server

  • Query runs, spec files, and individual test results from CI.
  • Surface error trends and performance metrics across your test suite.
  • Manage quarantine rules, webhooks, and project settings programmatically.
  • Create, link, and list Jira issues using the organization Jira integration.
  • Cancel, reset, or delete runs directly from the MCP tools.
  • Get aggregated error metrics and failure context for AI debugging.

Use cases of Currents MCP Server

  • Diagnose and fix flaky tests by examining actual CI output through an AI agent.
  • Programmatically manage project configuration (webhooks, actions, rules) from the editor.
  • Automatically create Jira issues from failing tests to track technical debt.
  • Monitor test suite health by querying aggregated performance metrics.
  • Allow agents to cancel or reset stuck runs without switching to the Currents dashboard.

FAQ from Currents MCP Server

What runtime or dependencies are required?

The server runs via npx -y @currents/mcp, which requires Node.js and npm (typically bundled with Node). No additional installation beyond the MCP client setup is needed.

How is data authenticated and secured?

Authentication uses a CURRENTS_API_KEY environment variable. By connecting AI tools via MCP to Currents, you grant them access to your API key, test results, and CI metadata. It is your responsibility to vet any AI agents or services you use.

Where does test execution data live?

All test execution data resides in the Currents cloud platform. The MCP server queries the Currents API to retrieve it; no local storage of test results is described.

What transport protocol does it use?

The MCP server uses the stdio transport, as shown by the command and args configuration in all setup examples.

Can the server create or delete project resources?

Yes. Tools include creating, updating, and deleting actions and webhooks, as well as deleting runs and cancelling or resetting them.

评论

其他 分类下的更多 MCP 服务器