Currents MCP Server

Currents MCP Server

Connect AI agents to test results context via Currents MCP Server.

14
Stars
6
Forks
14
Watchers
0
Issues
Currents MCP Server provides a standardized Model Context Protocol (MCP) server for integrating test results and debugging data into AI agents. It enables seamless communication between CI test data in Currents and AI-powered tools, such as Cursor Editor and Claude Desktop, facilitating actions like test optimization and failure diagnosis. The server exposes a suite of tools for retrieving detailed project, run, and performance metrics and is easily configurable via command-line for development and integration. Secure handling of API keys and support for local development are included.

Key Features

Standardized MCP server for context handling
Retrieval of project, run, and test details from Currents
Access to test debugging data and CI metadata
Historical performance metrics for test specs and tests
Test signature retrieval and result lookup
Easy integration with AI tools such as Cursor and Claude Desktop
Configurable via command-line or client configuration files
Support for local server and client development
Secure API key and environment management
Automated unit testing and CI support

Use Cases

Providing real-time test results context to AI agents
Diagnosing and fixing CI test failures with AI assistance
Querying historical test performance metrics for optimization
Debugging failed test runs through detailed data access
Integrating AI-powered code editors with CI pipelines
Automating quality assurance processes using AI tools
Enabling test prioritization based on performance data
Securing access to test results via API keys in automated workflows
Developing and testing custom AI integrations for test analysis
Centralizing test run metadata access for analytics or reporting

README

Currents MCP Server

Unit Tests

This is a MCP server that allows you to provide test results context to your AI agents by connecting them to Currents. Useful for asking AI to fix or optimize tests failing in CI.

Install MCP Server

Tools

Tool Description
currents-get-projects Retrieves a list of all projects available.
currents-get-runs Retrieves a list the latest runs for a specific project.
currents-get-run-details Retrieves details of a specific test run.
currents-get-spec-instances Retrieves debugging data a specific execution of a test spec file.
currents-get-spec-files-performance Retrieves spec file historical performance metrics for a specific project.
currents-get-tests-performance Retrieves test historical performance metrics for a specific project.
currents-get-tests-signatures Retrieves a test signature by its spec file name and test name.
currents-get-test-results Retrieves debugging data from test results of a test by its signature.

Setup

API Key

Get a Currents API key by following the instructions here.

Usage with Cursor Editor

  1. Go to Cursor Settings > MCP > Enable
  2. Add the following to your mcp.json.

NPX

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

Usage with Claude Desktop

Add the following to your claude_desktop_config.json:

NPX

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

⚠️ Notice

By connecting AI tools (e.g., via MCP) to Currents, you are granting them access to your API key, test results and CI metadata. It is your responsibility to vet any AI agents or services you use, and to ensure they handle your data securely.

How to Contribute

We welcome contributions of all kinds—bug fixes, features, and documentation updates!

Quick Start

  1. Fork this repository and clone your fork:
    bash
    git clone https://github.com/<your-username>/currents-mcp.git
    cd currents-mcp
    
  2. Install dependencies:
    bash
    cd mcp-server
    npm install
    
  3. Build the project:
    bash
    npm run build
    
  4. Run tests:
    bash
    npm test
    
    See TESTING.md for more details on testing.
  5. Run locally (stdio):
    bash
    npm start
    
    You should see: Currents MCP Server running on stdio.

Local Development with a Client (optional)

To test with a local MCP client (e.g., Cursor or Claude Desktop), point the client to your built server:

  • Command: node
  • Args: ./mcp-server/build/index.js
  • Env: set CURRENTS_API_KEY to a valid key

Example snippet for a client config:

json
{
  "mcpServers": {
    "currents": {
      "command": "node",
      "args": ["./mcp-server/build/index.js"],
      "env": {
        "CURRENTS_API_KEY": "your-api-key"
      }
    }
  }
}

Test tools locally

To test the tools locally without any LLM, you can use the following command:

bash
 npm run build

then run the tools script:

bash
 node scripts/call-tools.js

Making Changes

  • Create a feature branch:
    bash
    git checkout -b feat/short-description
    
  • Make changes under mcp-server/src/, then rebuild and re-run:
    bash
    npm run build && npm start
    
  • Write tests for your changes in *.test.ts files alongside your code
  • Run tests to ensure everything works:
    bash
    npm test
    
  • Keep changes focused and documented (add comments/types where helpful).

Commit and PR Guidelines

  • Write clear commit messages (e.g., “fix: handle missing env vars” or “feat: add get-run tool filters”).
  • Push your branch and open a Pull Request:
    bash
    git push origin feat/short-description
    
  • In your PR, describe the motivation, approach, and any trade-offs. Link related issues if applicable.

Reporting Issues

  • Before creating a new issue, please search existing issues to avoid duplicates.
  • When filing a bug report, include steps to reproduce, expected vs. actual behavior, and environment details (OS, Node.js version).

License

By contributing, you agree that your contributions will be licensed under the ISC license (as specified in the package metadata).

Star History

Star History Chart

Repository Owner

currents-dev
currents-dev

Organization

Repository Details

Language TypeScript
Default Branch main
Size 794 KB
Contributors 10
MCP Verified Nov 12, 2025

Programming Languages

TypeScript
84.53%
JavaScript
13.29%
Dockerfile
2.18%

Tags

Topics

ai currents mcp playwright

Join Our Newsletter

Stay updated with the latest AI tools, news, and offers by subscribing to our weekly newsletter.

We respect your privacy. Unsubscribe at any time.

Related MCPs

Discover similar Model Context Protocol servers

  • Exa MCP Server

    Exa MCP Server

    Fast, efficient web and code context for AI coding assistants.

    Exa MCP Server provides a Model Context Protocol (MCP) server interface that connects AI assistants to Exa AI’s powerful search capabilities, including code, documentation, and web search. It enables coding agents to retrieve precise, token-efficient context from billions of sources such as GitHub, StackOverflow, and documentation sites, reducing hallucinations in coding agents. The platform supports integration with popular tools like Cursor, Claude, and VS Code through standardized MCP configuration, offering configurable access to various research and code-related tools via HTTP.

    • 3,224
    • MCP
    • exa-labs/exa-mcp-server
  • Dappier MCP Server

    Dappier MCP Server

    Real-time web search and premium data access for AI agents via Model Context Protocol.

    Dappier MCP Server enables fast, real-time web search and access to premium data sources, including news, financial markets, sports, and weather, for AI agents using the Model Context Protocol (MCP). It integrates seamlessly with tools like Claude Desktop and Cursor, allowing users to enhance their AI workflows with up-to-date, trusted information. Simple installation and configuration are provided for multiple platforms, leveraging API keys for secure access. The solution supports deployment via Smithery and direct installation with 'uv', facilitating rapid setup for developers.

    • 35
    • MCP
    • DappierAI/dappier-mcp
  • CipherTrust Manager MCP Server

    CipherTrust Manager MCP Server

    Enables AI assistants to access CipherTrust Manager securely via the Model Context Protocol.

    CipherTrust Manager MCP Server provides an implementation of the Model Context Protocol (MCP), offering AI assistants such as Claude and Cursor a unified interface to interact with CipherTrust Manager resources. Communication is facilitated through JSON-RPC over stdin/stdout, enabling key management, CTE client management, user management, and connection management functionalities. The tool is configurable via environment variables and integrates with existing CipherTrust Manager instances using the ksctl CLI for secure resource access.

    • 7
    • MCP
    • sanyambassi/ciphertrust-manager-mcp-server
  • QA Sphere MCP Server

    QA Sphere MCP Server

    Model Context Protocol server enabling LLMs to interact with QA Sphere test cases

    QA Sphere MCP Server provides a Model Context Protocol (MCP) integration for QA Sphere, allowing Large Language Models to interact with, discover, and summarize test cases within the QA Sphere test management system. It enables AI-powered IDEs and MCP clients to reference and manipulate QA Sphere test case data within development workflows. The solution supports quick integration into clients like Claude, Cursor, and 5ire, facilitating seamless collaboration and context sharing for AI-assisted development.

    • 15
    • MCP
    • Hypersequent/qasphere-mcp
  • QuantConnect MCP Server

    QuantConnect MCP Server

    Official bridge for secure AI access to QuantConnect's algorithmic trading cloud platform

    QuantConnect MCP Server enables artificial intelligence systems such as Claude and OpenAI to interface with QuantConnect's cloud platform through an official, secure, and dockerized implementation of the Model Context Protocol (MCP). It facilitates automated project management, strategy writing, backtesting, and live deployment by exposing a comprehensive suite of API tools for users with valid access credentials. As the maintained official version, it ensures security, easy deployment, and cross-platform compatibility for advanced algorithmic trading automation.

    • 50
    • MCP
    • QuantConnect/mcp-server
  • MyMCP Server (All-in-One Model Context Protocol)

    MyMCP Server (All-in-One Model Context Protocol)

    Powerful and extensible Model Context Protocol server with developer and productivity integrations.

    MyMCP Server is a robust Model Context Protocol (MCP) server implementation that integrates with services like GitLab, Jira, Confluence, YouTube, Google Workspace, and more. It provides AI-powered search, contextual tool execution, and workflow automation for development and productivity tasks. The system supports extensive configuration and enables selective activation of grouped toolsets for various environments. Installation and deployment are streamlined, with both automated and manual setup options available.

    • 93
    • MCP
    • nguyenvanduocit/all-in-one-model-context-protocol
  • Didn't find tool you were looking for?

    Be as detailed as possible for better results