Currents MCP vs MCP Server
A side-by-side look at the Currents MCP and MCP Server 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 MCP Server 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 MCP Server when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
BROWSERSTACK_USERNAME, BROWSERSTACK_ACCESS_KEY. - You want tools like
accessibilityExpert, startAccessibilityScan, createAccessibilityAuthConfig.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 63/100 · Good | 65/100 · Great |
| 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 | BROWSERSTACK_USERNAMEBROWSERSTACK_ACCESS_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 21 | 155 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 43 | 52 |
| Full listing | View Currents MCP | View MCP Server |
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
MCP Server tools 52
accessibilityExpertAnswer accessibility, a11y, and WCAG questions using BrowserStack's accessibility knowledge base.startAccessibilityScanStart an accessibility scan via BrowserStack and retrieve a local CSV report path.createAccessibilityAuthConfigCreate an authentication configuration for accessibility scans. Supports both form-based and basic authentication.getAccessibilityAuthConfigRetrieve an existing authentication configuration by ID. Requires the numeric id returned by createAccessibilityAuthConfig. No tool here lists existing configurations, so if you do not have the id, create one rather than guessing.fetchAccessibilityIssuesFetch accessibility issues from a completed scan with pagination support. Use cursor parameter to get subsequent pages of results. Requires the ids of a completed scan, which are returned by startAccessibilityScan. No tool here lists past scans, so if you do not have the ids, start a new scan rather than guessing.setupBrowserStackAutomateTestsSet up and run automated web-based tests on BrowserStack using the BrowserStack SDK. Use this tool for functional or integration test setup on BrowserStack only. For any visual testing or Percy integration, use the dedicated Percy setup tool. Example prompts: run this test on browserstack; set up this project for browserstack.percyVisualTestIntegrationAgentIntegrate Percy visual testing into new projects and demonstrate visual change detection through a step-by-step simulation. This tool handles initial Percy integration, setup, and creates a working demonstration for new users. Primary tool for prompts like: "Integrate percy for this project", "Integrate percy in this project {project_name}"expandPercyVisualTestingSet up or expand Percy visual testing configuration with comprehensive coverage for existing projects that might have Percy integrated. This supports both Percy Web Standalone and Percy Automate. Example prompts: Expand percy coverage for this project {project_name}addPercySnapshotCommandsAdds Percy snapshot commands to the specified test files.listTestFilesLists all test files for a given set of directories.runPercyScanRun a Percy visual test scan. Example prompts : Run this Percy build/scan. Never run percy scan/build without this toolfetchPercyChangesRetrieves and summarizes all visual changes detected by Percy AI between the latest and previous builds, helping quickly review what has changed in your project.- +40 more on 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"
}
}
}
}
MCP Server
{
"mcpServers": {
"mcp-server-105": {
"command": "npx",
"args": [
"-y",
"@browserstack/mcp-server@latest"
],
"env": {
"BROWSERSTACK_USERNAME": "YOUR_BROWSERSTACK_USERNAME_HERE",
"BROWSERSTACK_ACCESS_KEY": "YOUR_BROWSERSTACK_ACCESS_KEY_HERE"
}
}
}
}
Frequently asked questions
Currents MCP is categorized under Browser Automation and uses a local stdio subprocess. MCP Server belongs to Browser Automation and uses a local stdio subprocess. Pick Currents MCP for browser automation work and MCP Server 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. MCP Server 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 mcp-server-105 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. MCP Server has 65/100 (Great) with 1 views, 0 installs and 155 GitHub stars.
