Skip to content

Commit 152f4fb

Browse files
Merge pull request #18 from currents-dev/feat/v2-new-tools
[CSR-3102] feat: new tools
2 parents 5f77173 + f505424 commit 152f4fb

File tree

16 files changed

+950
-338
lines changed

16 files changed

+950
-338
lines changed

.cursor/mcp.json

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@
44
"name": "Currents",
55
"description": "Currents MCP server",
66
"command": "npx",
7-
"args": ["-y", "@currents/mcp@0.1.1"],
8-
"env": {
9-
"CURRENTS_API_KEY": ""
7+
"args": ["node", "./mcp-server/build/index.js"],
8+
"env": {
9+
"CURRENTS_API_KEY": ""
1010
}
1111
}
1212
}

.gitignore

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,4 +3,5 @@ build
33
.git
44
.currents-debug
55
test-results
6-
playwright-report
6+
playwright-report
7+
.cursor

README.md

Lines changed: 13 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -2,22 +2,19 @@
22

33
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.
44

5-
65
[![Install MCP Server](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en/install-mcp?name=currents&config=eyJjb21tYW5kIjoibnB4IC15IEBjdXJyZW50cy9tY3AiLCJlbnYiOnsiQ1VSUkVOVFNfQVBJX0tFWSI6InlvdXItYXBpLWtleSJ9fQ%3D%3D)
76

87
## Tools
98

10-
1. `get-api-config`
11-
12-
- Get the API key and URL used to make requests to Currents API
13-
14-
2. `get-run`
15-
16-
- Get the run information by its ID
17-
18-
3. `get-spec-file-attempts-and-errors`
19-
20-
- Get the instance information about attempts and errors by its ID
9+
| Tool | Description |
10+
| ------------------------------------- | -------------------------------------------------------------------------- |
11+
| `currents-get-projects` | Retrieves a list of all projects available. |
12+
| `currents-get-run-details` | Retrieves details of a specific test run. |
13+
| `currents-get-spec-instances` | Retrieves debugging data a specific execution of a test spec file. |
14+
| `currents-get-spec-files-performance` | Retrieves spec file historical performance metrics for a specific project. |
15+
| `currents-get-tests-performance` | Retrieves test historical performance metrics for a specific project. |
16+
| `currents-get-tests-signatures` | Retrieves a test signature by its spec file name and test name. |
17+
| `currents-get-test-results` | Retrieves debugging data from test results of a test by its signature. |
2118

2219
## Setup
2320

@@ -31,6 +28,7 @@ Get a Currents API key by following the [instructions here](https://docs.current
3128
2. Add the following to your `mcp.json`.
3229

3330
### NPX
31+
3432
```
3533
{
3634
"mcpServers": {
@@ -61,6 +59,7 @@ npx -y @smithery/cli install @currents-dev/currents-mcp --client claude
6159
Add the following to your `claude_desktop_config.json`:
6260

6361
#### NPX
62+
6463
```
6564
{
6665
"mcpServers": {
@@ -78,10 +77,9 @@ Add the following to your `claude_desktop_config.json`:
7877
}
7978
```
8079

81-
8280
### ⚠️ Notice
83-
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.
8481

82+
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.
8583

8684
## How to Contribute
8785

@@ -118,6 +116,7 @@ To test with a local MCP client (e.g., Cursor or Claude Desktop), point the clie
118116
- Env: set `CURRENTS_API_KEY` to a valid key
119117

120118
Example snippet for a client config:
119+
121120
```json
122121
{
123122
"mcpServers": {

0 commit comments

Comments
 (0)