Currents MCP vs TesterArmy
A side-by-side look at the Currents MCP and TesterArmy MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Currents MCP for browser automation work as a local process; choose TesterArmy for browser automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Currents MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
CURRENTS_API_KEY. - You want tools like
currents-list-actions, currents-create-action, currents-get-action.
Choose TesterArmy when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 63/100 · Good | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | CURRENTS_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 21 | 70 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 43 | Not listed |
| Full listing | View Currents MCP | View TesterArmy |
Tools & capabilities
Currents MCP tools 43
currents-list-actionsList all actions for a project with optional filtering.currents-create-actionCreate a new action for a project.currents-get-actionGet a single action by ID.currents-update-actionUpdate an existing action.currents-delete-actionDelete (archive) an action.currents-enable-actionEnable a disabled action.currents-disable-actionDisable an active action.currents-list-affected-testsList tests affected by actions (quarantine, skip, tag) for a project within a date range.currents-get-affected-test-executionsKeyed on a test: lists the executions of one test that an action applied to, within a date range, with the run, branch and commit of each.currents-get-action-executionsKeyed on an action: lists the test executions one rule was applied to, across every test it touched, within a date range.currents-get-projectsRetrieves projects available in the Currents platform.currents-get-projectGet a single project by ID.- +31 more on the listing page
TesterArmy tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Currents MCP
{
"mcpServers": {
"currents-dev-currents-mcp": {
"command": "npx",
"args": [
"-y",
"@currents/mcp"
],
"env": {
"CURRENTS_API_KEY": "YOUR_CURRENTS_API_KEY_HERE"
}
}
}
}
TesterArmy
{
"mcpServers": {
"testerarmy": {
"command": "npx",
"args": [
"-y",
"testerarmy"
]
}
}
}
Frequently asked questions
Currents MCP is categorized under Browser Automation and uses a local stdio subprocess. TesterArmy belongs to Browser Automation and uses a local stdio subprocess. Pick Currents MCP for browser automation work and TesterArmy for browser automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Currents MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. TesterArmy has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add currents-dev-currents-mcp and testerarmy as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Currents MCP has a quality signal of 63/100 (Good) with 4 views, 0 installs and 21 GitHub stars. TesterArmy has 47/100 (Fair) with 1 views, 0 installs and 70 GitHub stars.
