BrowserStack's Official MCP Server
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
BROWSERSTACK_ACCESS_KEYAPI keyrequiredBrowserStack Access Key
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
accessibilityExpertNo description publishedThis tool published no description. Forge does not invent one.
startAccessibilityScanNo description publishedThis tool published no description. Forge does not invent one.
createAccessibilityAuthConfigNo description publishedThis tool published no description. Forge does not invent one.
getAccessibilityAuthConfigNo description publishedThis tool published no description. Forge does not invent one.
fetchAccessibilityIssuesNo description publishedThis tool published no description. Forge does not invent one.
takeAppScreenshotNo description publishedThis tool published no description. Forge does not invent one.
runAppTestsOnBrowserStackNo description publishedThis tool published no description. Forge does not invent one.
setupBrowserStackAppAutomateTestsNo description publishedThis tool published no description. Forge does not invent one.
runAppLiveSessionNo description publishedThis tool published no description. Forge does not invent one.
fetchAutomationScreenshotsNo description publishedThis tool published no description. Forge does not invent one.
setupBrowserStackAutomateTestsNo description publishedThis tool published no description. Forge does not invent one.
fetchBuildInsightsNo description publishedThis tool published no description. Forge does not invent one.
getFailureLogsNo description publishedThis tool published no description. Forge does not invent one.
runBrowserLiveSessionNo description publishedThis tool published no description. Forge does not invent one.
getFailuresInLastRunNo description publishedThis tool published no description. Forge does not invent one.
percyVisualTestIntegrationAgentNo description publishedThis tool published no description. Forge does not invent one.
expandPercyVisualTestingNo description publishedThis tool published no description. Forge does not invent one.
addPercySnapshotCommandsprivilegedNo description publishedThis tool published no description. Forge does not invent one.
listTestFilesNo description publishedThis tool published no description. Forge does not invent one.
runPercyScanNo description publishedThis tool published no description. Forge does not invent one.
fetchPercyChangesNo description publishedThis tool published no description. Forge does not invent one.
managePercyBuildApprovalNo description publishedThis tool published no description. Forge does not invent one.
fetchRCANo description publishedThis tool published no description. Forge does not invent one.
getBuildIdNo description publishedThis tool published no description. Forge does not invent one.
listBuildIdNo description publishedThis tool published no description. Forge does not invent one.
listTestIdsNo description publishedThis tool published no description. Forge does not invent one.
fetchSelfHealedSelectorsNo description publishedThis tool published no description. Forge does not invent one.
prepareSelfHealingPlanNo description publishedThis tool published no description. Forge does not invent one.
createProjectOrFolderNo description publishedThis tool published no description. Forge does not invent one.
createTestCaseNo description publishedThis tool published no description. Forge does not invent one.
updateTestCaseNo description publishedThis tool published no description. Forge does not invent one.
listTestCasesNo description publishedThis tool published no description. Forge does not invent one.
listFoldersNo description publishedThis tool published no description. Forge does not invent one.
listTestCaseTemplatesNo description publishedThis tool published no description. Forge does not invent one.
createTestRunNo description publishedThis tool published no description. Forge does not invent one.
listTestRunsNo description publishedThis tool published no description. Forge does not invent one.
updateTestRunNo description publishedThis tool published no description. Forge does not invent one.
addTestResultNo description publishedThis tool published no description. Forge does not invent one.
uploadProductRequirementFileNo description publishedThis tool published no description. Forge does not invent one.
createTestCasesFromFileNo description publishedThis tool published no description. Forge does not invent one.
0 of 40 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
BrowserStack's Official MCP Server
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.