MCP server
by currents-dev
Connect to Currents Test Results for AI-driven analysis of test failures, suite optimization, and enhanced CI/CD trouble
Connects AI to Currents test results platform to analyze test failures and optimize test suites. Provides direct access to test execution data from CI/CD pipelines.
Currents Test Results is an official MCP server published by currents-dev that provides AI assistants with tools and capabilities via the Model Context Protocol. Connect to Currents Test Results for AI-driven analysis of test failures, suite optimization, and enhanced CI/CD trouble It is categorized under developer tools.
You can install Currents Test Results in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
Apache-2.0
Currents Test Results is released under the Apache-2.0 license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Currents Test Results is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Currents Test Results is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
We evaluated Currents Test Results against two servers with overlapping tools; this profile had the clearer scope statement.
Useful MCP listing: Currents Test Results is the kind of server we cite when onboarding engineers to host + tool permissions.
We evaluated Currents Test Results against two servers with overlapping tools; this profile had the clearer scope statement.
Useful MCP listing: Currents Test Results is the kind of server we cite when onboarding engineers to host + tool permissions.
We evaluated Currents Test Results against two servers with overlapping tools; this profile had the clearer scope statement.
According to our notes, Currents Test Results benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Currents Test Results has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Useful MCP listing: Currents Test Results is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 38
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.
| Tool | Description |
|---|---|
currents-get-projects | Retrieves projects available in the Currents platform. |
currents-get-project | Get a single project by ID. |
currents-get-project-insights | Get aggregated run and test metrics for a project within a date range. |
currents-get-runs | Retrieves a list of runs for a specific project with optional filtering. |
currents-get-run-details | Retrieves details of a specific test run. |
currents-find-run | Find a run by query parameters. |
currents-cancel-run | Cancel a run in progress. |
currents-reset-run | Reset failed spec files in a run to allow re-execution. |
currents-delete-run | Delete a run and all associated data. |
currents-cancel-run-github-ci | Cancel a run by GitHub Actions workflow run ID and attempt number. |
currents-get-spec-instance | Retrieves debugging data from a specific execution of a test spec file by instanceId. |
currents-get-spec-files-performance | Retrieves spec files performance metrics for a specific project within a date range. |
currents-get-tests-performance | Retrieves aggregated test metrics for a specific project within a date range. |
currents-get-tests-signatures | Generates a unique test signature based on project, spec file path, and test title. |
currents-get-test-results | Retrieves historical test execution results for a specific test signature. |
currents-get-errors-explorer | Get aggregated error metrics for a project within a date range with comprehensive filtering and grouping. |
currents-list-actions | List all actions for a project with optional filtering. |
currents-create-action | Create a new action for a project. |
currents-get-action | Get a single action by ID. |
currents-update-action | Update an existing action. |
currents-delete-action | Delete (archive) an action. |
currents-enable-action | Enable a disabled action. |
currents-disable-action | Disable an active action. |
currents-list-webhooks | List all webhooks for a project. |
currents-create-webhook | Create a new webhook for a project. |
currents-get-webhook | Get a single webhook by ID. |
currents-update-webhook | Update an existing webhook. |
currents-delete-webhook | Delete a webhook. |
Get a Currents API key by following the instructions here.
mcp.json.{
"mcpServers": {
"currents": {
"command": "npx",
"args": ["-y", "@currents/mcp"],
"env": {
"CURRENTS_API_KEY": "your-api-key"
}
}
}
}
Run this command to add Currents MCP to Claude Code
claude mcp add --transport stdio currents --env CURRENTS_API_KEY=<KEY> -- npx -y @currents/mcp
Add the following to enable Currents MCP on Claude Desktop (edit claude_desktop_config.json file):
{
"mcpServers": {
"currents": {
"command": "npx",
"args": ["-y", "@currents/mcp"],
"env": {
"CURRENTS_API_KEY": "your-api-key"
}
}
}
}
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.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.