@testledger/mcp 0.0.2 → 0.0.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -10
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -25,7 +25,7 @@ Add this to your Claude Code MCP config:
|
|
|
25
25
|
"command": "npx",
|
|
26
26
|
"args": ["-y", "@testledger/mcp"],
|
|
27
27
|
"env": {
|
|
28
|
-
"
|
|
28
|
+
"TEST_LEDGER_API_KEY": "your-api-key-here"
|
|
29
29
|
}
|
|
30
30
|
}
|
|
31
31
|
}
|
|
@@ -42,7 +42,7 @@ Once configured, you can ask Claude Code things like:
|
|
|
42
42
|
|
|
43
43
|
- "Why is `checkout.spec.js` flaky?"
|
|
44
44
|
- "What tests have been failing the most this week?"
|
|
45
|
-
- "
|
|
45
|
+
- "Show me recent test failures"
|
|
46
46
|
- "Are there any tests that always fail together?"
|
|
47
47
|
|
|
48
48
|
### With the /fix-flaky-test command
|
|
@@ -71,21 +71,19 @@ The MCP server provides these tools to Claude:
|
|
|
71
71
|
| Tool | Description |
|
|
72
72
|
|------|-------------|
|
|
73
73
|
| `get_test_history` | Pass/fail/flaky statistics for a test |
|
|
74
|
-
| `get_test_errors` | Error messages and stacktraces, grouped by frequency |
|
|
75
74
|
| `get_failure_patterns` | Time-of-day, browser, and version patterns |
|
|
76
75
|
| `get_correlated_failures` | Tests that fail together (shared setup issues) |
|
|
77
76
|
| `get_flaky_tests` | Project-wide flaky test leaderboard |
|
|
78
77
|
| `get_recent_failures` | Recent failures for quick triage |
|
|
79
78
|
| `get_test_trend` | Failure rate over time |
|
|
80
|
-
| `search_errors` | Full-text search across all errors |
|
|
81
79
|
|
|
82
80
|
## Configuration Options
|
|
83
81
|
|
|
84
82
|
| Environment Variable | Required | Description |
|
|
85
|
-
|
|
86
|
-
| `
|
|
87
|
-
| `
|
|
88
|
-
| `
|
|
83
|
+
|--------------------------|-----|------------------------------------------------------------|
|
|
84
|
+
| `TEST_LEDGER_API_KEY` | Yes | Your API key from the dashboard |
|
|
85
|
+
| `TEST_LEDGER_API_URL` | No | Custom API URL (default: `https://app-api.testledger.dev`) |
|
|
86
|
+
| `TEST_LEDGER_PROJECT_ID` | No | Default project ID to use for queries |
|
|
89
87
|
|
|
90
88
|
### Example with all options
|
|
91
89
|
|
|
@@ -96,8 +94,8 @@ The MCP server provides these tools to Claude:
|
|
|
96
94
|
"command": "npx",
|
|
97
95
|
"args": ["-y", "@testledger/mcp"],
|
|
98
96
|
"env": {
|
|
99
|
-
"
|
|
100
|
-
"
|
|
97
|
+
"TEST_LEDGER_API_KEY": "tr_live_abc123",
|
|
98
|
+
"TEST_LEDGER_PROJECT_ID": "42"
|
|
101
99
|
}
|
|
102
100
|
}
|
|
103
101
|
}
|