@browserstack/mcp-server 1.1.8 → 1.1.9

package/README.md

@@ -12,7 +12,7 @@
 
 </div>
 
-<p align="center">One Platform For All Your Testing Needs</p>
+<p align="center">Comprehensive Test Platform</p>
 
 <div align="center">
 <a href="https://glama.ai/mcp/servers/@browserstack/mcp-server">
@@ -21,26 +21,23 @@
 </div>
 
 <div>
-    <a href="https://www.youtube.com/watch?v=sLA7K9v7qZc">
+    <a href="https://www.youtube.com/watch?v=sLA7K9v7qZc&list=PL1vH6dHT3H7oy8w9CY6L_nxGxCc89VXMX&index=5">
       <img src="assets/thumbnail.webp">
     </a>
   </div>
   
-Enable every developer and tester in your team, whether they are testing manually, starting their automation journey, or scaling test automation.
-BrowserStack MCP Server allows you to use our cutting-edge [Test Platform](https://www.browserstack.com/test-platform) directly from your favourite AI tools.
-
-### Why BrowserStack ?
-
-<p align="center">
-  <img src="assets/overview.png" alt="overview">
-</p>
+Manage test cases, execute manual or automated tests, debug issues, and even fix code—directly within tools like Cursor, Claude, or any MCP-enabled client, using plain English.
+#### Test from anywhere:
+Easily connect the BrowserStack Test Platform to your favourite AI tools, such as IDEs, LLMs, or agentic workflows.
+#### Reduced context switching:
+Stay in flow—keep all project context in one place and trigger actions directly from your IDE or LLM.
 
 ## 💡 Usage Examples
 
 ### 📱 Manual App Testing
 
-Use the following prompts to use your **mobile apps** on BrowserStack's extensive cloud of real devices. Stop using emulators!
-
+Test mobile apps on real devices across the latest OS versions. Reproduce bugs and debug crashes without setup hassles.
+Below are some sample prompts to use your mobile apps on BrowserStack's extensive cloud of real devices
 ```bash
 # Open app on specific device
 "open my app on a iPhone 15 Pro Max"
@@ -49,7 +46,6 @@ Use the following prompts to use your **mobile apps** on BrowserStack's extensiv
 "My app crashed on Android 14 device, can you help me debug?"
 ```
 
-
 - Unlike emulators, test your app's real-world performance on actual devices. With advanced [App-Profiling features](https://www.browserstack.com/docs/app-live/app-performance-testing), you can debug crashes and performance issues in real-time.
 - Access all major devices and OS versions from our [device grid](https://www.browserstack.com/list-of-browsers-and-platforms/app_live), We have strict SLAs to provision our global datacenters with newly released devices on [launch day](https://www.browserstack.com/blog/browserstack-launches-iphone-15-on-day-0-behind-the-scenes/).
 
@@ -58,8 +54,9 @@ Use the following prompts to use your **mobile apps** on BrowserStack's extensiv
 Similar to the app testing, you can use the following prompts to test your **websites** on BrowserStack's extensive cloud of real browsers and devices. Don't have Edge browser installed on your machine ? We've got you covered!
 
 ```bash
-# Test your local websites
+# Test your websites
 "open my website hosted on localhost:3001 on Edge"
+"open browserstack.com on latest version of Chrome"
 ```
 
 - Test websites across different browsers and devices. We support [every major browser](https://www.browserstack.com/list-of-browsers-and-platforms/live) across every major OS.
@@ -67,27 +64,39 @@ Similar to the app testing, you can use the following prompts to test your **web
 
 ### 🧪 Automated Testing (Playwright, Selenium, A11y and more..)
 
-Use the following prompts to run/debug/fix your **automated tests** on BrowserStack's [Test Platform](https://www.browserstack.com/test-platform).
+Auto-analyze, diagnose, and even fix broken test scripts right in your IDE or LLM. Instantly fetch logs, identify root causes, and apply context-aware fixes. No more debugging loops.
+Below are few example prompts to run/debug/fix your automated tests on BrowserStack's [Test Platform](https://www.browserstack.com/test-platform).
 
 ```bash
-# Port test suite to BrowserStack
-"run my test suite on BrowserStack infra"
+#Port test suite to BrowserStack
+"Setup test suite to run on BrowserStack infra"
 
-# Debug test failures
-"My test suite failed, can you help me fix the new failures?"
+#Run tests on BrowserStack
+“Run my tests on BrowserStack”
 
-# Accessibility testing
-"check for accessibility issues on my www.mywebsite.com"
-```
+#AI powered debugging of test failures
+"My App Automate tests have failed, can you help me fix the new failures?"
 
+```
 - Fix test failures reported by your CI/CD pipeline by utilising our industry leading [Test Observability](https://www.browserstack.com/docs/test-observability) features. Find more info [here](https://www.browserstack.com/docs/test-observability/features/smart-tags).
 - Run tests written in Jest, Playwright, Selenium, and more on BrowserStack's [Test Platform](https://www.browserstack.com/test-platform)
-- **Accessibility Testing**: Ensure WCAG and ADA compliance with our [Accessibility Testing](https://www.browserstack.com/accessibility-testing) tool
 
+### 🌐 Accessibility
+
+Catch accessibility issues early with automated, local a11y scans. Get one-click, AI-suggested fixes. No docs hunting, no CI surprises. Ensure WCAG and ADA compliance with our Accessibility Testing tool
+
+```bash
+#Scan accessibility issues while development
+"Scan & help fix accessibility issues for my website running locally on localhost:3000"
+
+#Scan accessibility issues on production site
+“Run accessibility scan & identify issues on my website - www.bstackdemo.com”
+
+```
 
 ### 📋 Test Management 
 
-Use the following prompts to utilise capabilities of BrowserStack's [Test Management](https://www.browserstack.com/test-management) with MCP server.
+Create and manage test cases, create test plans and trigger test runs using natural language. Below are a few example prompts to utilise capabilities of BrowserStack's [Test Management](https://www.browserstack.com/test-management) with MCP server.
 
 ```bash
 # Create project & folder structure
@@ -106,6 +115,24 @@ Use the following prompts to utilise capabilities of BrowserStack's [Test Manage
 "update test results as passed for Login tests test run from My Demo Project"
 ```
 
+### 🧪 Access BrowserStack AI agnets 
+
+Generate test cases from PRDs, convert manual tests to low-code automation, and auto-heal flaky scripts powered by BrowserStack’s AI agents, seamlessly integrated into your workflow.  Below are few example prompts to access Browserstack AI agents
+
+```bash
+#Test case generator agent
+"With Browserstack AI, create relevant test cases for my PRD located at /usr/file/location"
+
+
+#Low code authoring agent
+“With Browserstack AI, automate my manual test case X, added in Test Management”
+
+
+#Self healing agent
+“Help fix flaky tests in my test script with Browserstack AI self healing”
+```
+
+
 ## 🛠️ Installation
 
 1. **Create a BrowserStack Account**
@@ -113,9 +140,7 @@ Use the following prompts to utilise capabilities of BrowserStack's [Test Manage
    - Sign up for [BrowserStack](https://www.browserstack.com/users/sign_up) if you don't have an account already.
 
    - ℹ️ If you have an open-source project, we'll be able to provide you with a [free plan](https://www.browserstack.com/open-source).
-   <div align="center">
-   <img src="assets/open-source-plan.png" alt="Open Source Plan">
-   </div>
+   
 
    - Once you have an account (and purchased appropriate plan), note down your `username` and `access_key` from [Account Settings](https://www.browserstack.com/accounts/profile/details).
 
@@ -175,6 +200,25 @@ Use the following prompts to utilise capabilities of BrowserStack's [Test Manage
      }
    }
    ```
+   - Cline
+     
+Click the “MCP Servers” icon in the navigation bar
+Select the “Installed” tab. Click the “Configure MCP Servers” button at the bottom of the pane.
+
+   ```json
+   {
+     "mcpServers": {
+       "browserstack": {
+         "command": "npx",
+         "args": ["-y", "@browserstack/mcp-server@latest"],
+         "env": {
+           "BROWSERSTACK_USERNAME": "<username>",
+           "BROWSERSTACK_ACCESS_KEY": "<access_key>"
+         }
+       }
+     }
+   }
+   ```
 
 ### Installing via Smithery
 
@@ -203,17 +247,9 @@ We welcome contributions! Please open an issue to discuss any changes you'd like
 
 For support, please:
 
-- Check our [documentation](https://www.browserstack.com/docs)
 - Open an issue in our [GitHub repository](https://github.com/browserstack/mcp-server) if you face any issues related to the MCP Server.
 - Contact our [support team](https://www.browserstack.com/contact) for any other queries.
 
 ## 🚀 More Features Coming Soon
 
 Stay tuned for exciting updates! Have any suggestions? Please open an issue to discuss.
-
-## 🔗 Resources
-
-- [BrowserStack Test Platform](https://www.browserstack.com/test-platform)
-- [MCP Protocol Documentation](https://modelcontextprotocol.io)
-- [Device Grid](https://www.browserstack.com/list-of-browsers-and-platforms/app_live)
-- [Accessibility Testing](https://www.browserstack.com/accessibility-testing)

package/dist/config.js

@@ -28,17 +28,23 @@ for (const key of BROWSERSTACK_LOCAL_OPTION_KEYS) {
         browserstackLocalOptions[key] = envVar;
     }
 }
+/**
+ * USE_OWN_LOCAL_BINARY_PROCESS:
+ *   If true, the system will not start a new local binary process, but will use the user's own process.
+ */
 export class Config {
     browserstackUsername;
     browserstackAccessKey;
     DEV_MODE;
     browserstackLocalOptions;
-    constructor(browserstackUsername, browserstackAccessKey, DEV_MODE, browserstackLocalOptions) {
+    USE_OWN_LOCAL_BINARY_PROCESS;
+    constructor(browserstackUsername, browserstackAccessKey, DEV_MODE, browserstackLocalOptions, USE_OWN_LOCAL_BINARY_PROCESS) {
         this.browserstackUsername = browserstackUsername;
         this.browserstackAccessKey = browserstackAccessKey;
         this.DEV_MODE = DEV_MODE;
         this.browserstackLocalOptions = browserstackLocalOptions;
+        this.USE_OWN_LOCAL_BINARY_PROCESS = USE_OWN_LOCAL_BINARY_PROCESS;
     }
 }
-const config = new Config(process.env.BROWSERSTACK_USERNAME, process.env.BROWSERSTACK_ACCESS_KEY, process.env.DEV_MODE === "true", browserstackLocalOptions);
+const config = new Config(process.env.BROWSERSTACK_USERNAME, process.env.BROWSERSTACK_ACCESS_KEY, process.env.DEV_MODE === "true", browserstackLocalOptions, process.env.USE_OWN_LOCAL_BINARY_PROCESS === "true");
 export default config;

package/dist/lib/local.js

@@ -67,6 +67,15 @@ export async function killExistingBrowserStackLocalProcesses() {
 }
 export async function ensureLocalBinarySetup(localIdentifier) {
     logger.info("Ensuring local binary setup as it is required for private URLs...");
+    if (config.USE_OWN_LOCAL_BINARY_PROCESS) {
+        logger.info("Using user's own BrowserStack Local binary process, checking if it's running...");
+        const isRunning = await isBrowserStackLocalRunning();
+        if (!isRunning) {
+            throw new Error("USE_OWN_LOCAL_BINARY_PROCESS is enabled but BrowserStack Local process is not running. Please start your BrowserStack Local binary process first.");
+        }
+        logger.info("BrowserStack Local process is running, proceeding with user's own process.");
+        return;
+    }
     const localBinary = new Local();
     await killExistingBrowserStackLocalProcesses();
     // Use a single options object from config and extend with required fields

package/dist/tools/accessiblity-utils/scanner.js

@@ -13,6 +13,9 @@ export class AccessibilityScanner {
         const localIdentifier = crypto.randomUUID();
         const localHosts = new Set(["127.0.0.1", "localhost", "0.0.0.0"]);
         const BS_LOCAL_DOMAIN = "bs-local.com";
+        if (config.USE_OWN_LOCAL_BINARY_PROCESS && hasLocal) {
+            throw new Error("Cannot start scan with local URLs when using own BrowserStack Local binary process. Please set USE_OWN_LOCAL_BINARY_PROCESS to false.");
+        }
         if (hasLocal) {
             await ensureLocalBinarySetup(localIdentifier);
         }

package/dist/tools/appautomate-utils/appautomate.js

@@ -3,6 +3,10 @@ import axios from "axios";
 import config from "../../config.js";
 import FormData from "form-data";
 import { customFuzzySearch } from "../../lib/fuzzy.js";
+const auth = {
+    username: config.browserstackUsername,
+    password: config.browserstackAccessKey,
+};
 /**
  * Finds devices that exactly match the provided display name.
  * Uses fuzzy search first, and then filters for exact case-insensitive match.
@@ -78,13 +82,8 @@ export async function uploadApp(appPath) {
     const formData = new FormData();
     formData.append("file", fs.createReadStream(filePath));
     const response = await axios.post("https://api-cloud.browserstack.com/app-automate/upload", formData, {
-        headers: {
-            ...formData.getHeaders(),
-        },
-        auth: {
-            username: config.browserstackUsername,
-            password: config.browserstackAccessKey,
-        },
+        headers: formData.getHeaders(),
+        auth,
     });
     if (response.data.app_url) {
         return response.data.app_url;
@@ -93,3 +92,65 @@ export async function uploadApp(appPath) {
         throw new Error(`Failed to upload app: ${response.data}`);
     }
 }
+// Helper to upload a file to a given BrowserStack endpoint and return a specific property from the response.
+async function uploadFileToBrowserStack(filePath, endpoint, responseKey) {
+    if (!fs.existsSync(filePath)) {
+        throw new Error(`File not found at path: ${filePath}`);
+    }
+    const formData = new FormData();
+    formData.append("file", fs.createReadStream(filePath));
+    const response = await axios.post(endpoint, formData, {
+        headers: formData.getHeaders(),
+        auth,
+    });
+    if (response.data[responseKey]) {
+        return response.data[responseKey];
+    }
+    throw new Error(`Failed to upload file: ${JSON.stringify(response.data)}`);
+}
+//Uploads an Android app (.apk or .aab) to BrowserStack Espresso endpoint and returns the app_url
+export async function uploadEspressoApp(appPath) {
+    return uploadFileToBrowserStack(appPath, "https://api-cloud.browserstack.com/app-automate/espresso/v2/app", "app_url");
+}
+//Uploads an Espresso test suite (.apk) to BrowserStack and returns the test_suite_url
+export async function uploadEspressoTestSuite(testSuitePath) {
+    return uploadFileToBrowserStack(testSuitePath, "https://api-cloud.browserstack.com/app-automate/espresso/v2/test-suite", "test_suite_url");
+}
+//Uploads an iOS app (.ipa) to BrowserStack XCUITest endpoint and returns the app_url
+export async function uploadXcuiApp(appPath) {
+    return uploadFileToBrowserStack(appPath, "https://api-cloud.browserstack.com/app-automate/xcuitest/v2/app", "app_url");
+}
+//Uploads an XCUITest test suite (.zip) to BrowserStack and returns the test_suite_url
+export async function uploadXcuiTestSuite(testSuitePath) {
+    return uploadFileToBrowserStack(testSuitePath, "https://api-cloud.browserstack.com/app-automate/xcuitest/v2/test-suite", "test_suite_url");
+}
+// Triggers an Espresso test run on BrowserStack and returns the build_id
+export async function triggerEspressoBuild(app_url, test_suite_url, devices, project) {
+    const response = await axios.post("https://api-cloud.browserstack.com/app-automate/espresso/v2/build", {
+        app: app_url,
+        testSuite: test_suite_url,
+        devices,
+        project,
+    }, {
+        auth,
+    });
+    if (response.data.build_id) {
+        return response.data.build_id;
+    }
+    throw new Error(`Failed to trigger Espresso build: ${JSON.stringify(response.data)}`);
+}
+// Triggers an XCUITest run on BrowserStack and returns the build_id
+export async function triggerXcuiBuild(app_url, test_suite_url, devices, project) {
+    const response = await axios.post("https://api-cloud.browserstack.com/app-automate/xcuitest/v2/build", {
+        app: app_url,
+        testSuite: test_suite_url,
+        devices,
+        project,
+    }, {
+        auth,
+    });
+    if (response.data.build_id) {
+        return response.data.build_id;
+    }
+    throw new Error(`Failed to trigger XCUITest build: ${JSON.stringify(response.data)}`);
+}

package/dist/tools/appautomate-utils/types.js

@@ -0,0 +1,6 @@
+export var AppTestPlatform;
+(function (AppTestPlatform) {
+    AppTestPlatform["ESPRESSO"] = "espresso";
+    AppTestPlatform["APPIUM"] = "appium";
+    AppTestPlatform["XCUITEST"] = "xcuitest";
+})(AppTestPlatform || (AppTestPlatform = {}));

package/dist/tools/appautomate.js

@@ -4,8 +4,9 @@ import config from "../config.js";
 import { trackMCP } from "../lib/instrumentation.js";
 import { maybeCompressBase64 } from "../lib/utils.js";
 import { remote } from "webdriverio";
+import { AppTestPlatform } from "./appautomate-utils/types.js";
 import { getDevicesAndBrowsers, BrowserStackProducts, } from "../lib/device-cache.js";
-import { findMatchingDevice, getDeviceVersions, resolveVersion, validateArgs, uploadApp, } from "./appautomate-utils/appautomate.js";
+import { findMatchingDevice, getDeviceVersions, resolveVersion, validateArgs, uploadApp, uploadEspressoApp, uploadEspressoTestSuite, triggerEspressoBuild, uploadXcuiApp, uploadXcuiTestSuite, triggerXcuiBuild, } from "./appautomate-utils/appautomate.js";
 var Platform;
 (function (Platform) {
     Platform["ANDROID"] = "android";
@@ -84,9 +85,52 @@ async function takeAppScreenshot(args) {
         }
     }
 }
-/**
- * Registers the `takeAppScreenshot` tool with the MCP server.
- */
+//Runs AppAutomate tests on BrowserStack by uploading app and test suite, then triggering a test run.
+async function runAppTestsOnBrowserStack(args) {
+    switch (args.detectedAutomationFramework) {
+        case AppTestPlatform.ESPRESSO: {
+            try {
+                const app_url = await uploadEspressoApp(args.appPath);
+                const test_suite_url = await uploadEspressoTestSuite(args.testSuitePath);
+                const build_id = await triggerEspressoBuild(app_url, test_suite_url, args.devices, args.project);
+                return {
+                    content: [
+                        {
+                            type: "text",
+                            text: `✅ Espresso run started successfully!\n\n🔧 Build ID: ${build_id}\n🔗 View your build: https://app-automate.browserstack.com/builds/${build_id}`,
+                        },
+                    ],
+                };
+            }
+            catch (err) {
+                logger.error("Error running App Automate test", err);
+                throw err;
+            }
+        }
+        case AppTestPlatform.XCUITEST: {
+            try {
+                const app_url = await uploadXcuiApp(args.appPath);
+                const test_suite_url = await uploadXcuiTestSuite(args.testSuitePath);
+                const build_id = await triggerXcuiBuild(app_url, test_suite_url, args.devices, args.project);
+                return {
+                    content: [
+                        {
+                            type: "text",
+                            text: `✅ XCUITest run started successfully!\n\n🔧 Build ID: ${build_id}\n🔗 View your build: https://app-automate.browserstack.com/builds/${build_id}`,
+                        },
+                    ],
+                };
+            }
+            catch (err) {
+                logger.error("Error running XCUITest App Automate test", err);
+                throw err;
+            }
+        }
+        default:
+            throw new Error(`Unsupported automation framework: ${args.detectedAutomationFramework}. If you need support for this framework, please open an issue at Github`);
+    }
+}
+// Registers automation tools with the MCP server.
 export default function addAppAutomationTools(server) {
     server.tool("takeAppScreenshot", "Use this tool to take a screenshot of an app running on a BrowserStack device. This is useful for visual testing and debugging.", {
         desiredPhone: z
@@ -119,4 +163,55 @@ export default function addAppAutomationTools(server) {
             };
         }
     });
+    server.tool("runAppTestsOnBrowserStack", "Run AppAutomate tests on BrowserStack by uploading app and test suite. If running from Android Studio or Xcode, the tool will help export app and test files automatically. For other environments, you'll need to provide the paths to your pre-built app and test files.", {
+        appPath: z
+            .string()
+            .describe("Path to your application file:\n" +
+            "If in development IDE directory:\n" +
+            "• For Android: 'gradle assembleDebug'\n" +
+            "• For iOS:\n" +
+            "  xcodebuild clean -scheme YOUR_SCHEME && \\\n" +
+            "  xcodebuild archive -scheme YOUR_SCHEME -configuration Release -archivePath build/app.xcarchive && \\\n" +
+            "  xcodebuild -exportArchive -archivePath build/app.xcarchive -exportPath build/ipa -exportOptionsPlist exportOptions.plist\n\n" +
+            "If in other directory, provide existing app path"),
+        testSuitePath: z
+            .string()
+            .describe("Path to your test suite file:\n" +
+            "If in development IDE directory:\n" +
+            "• For Android: 'gradle assembleAndroidTest'\n" +
+            "• For iOS:\n" +
+            "  xcodebuild test-without-building -scheme YOUR_SCHEME -destination 'generic/platform=iOS' && \\\n" +
+            "  cd ~/Library/Developer/Xcode/DerivedData/*/Build/Products/Debug-iphonesimulator/ && \\\n" +
+            "  zip -r Tests.zip *.xctestrun *-Runner.app\n\n" +
+            "If in other directory, provide existing test file path"),
+        devices: z
+            .array(z.string())
+            .describe("List of devices to run the test on, e.g., ['Samsung Galaxy S20-10.0', 'iPhone 12 Pro-16.0']."),
+        project: z
+            .string()
+            .optional()
+            .default("BStack-AppAutomate-Suite")
+            .describe("Project name for organizing test runs on BrowserStack."),
+        detectedAutomationFramework: z
+            .string()
+            .describe("The automation framework used in the project, such as 'espresso' (Android) or 'xcuitest' (iOS)."),
+    }, async (args) => {
+        try {
+            trackMCP("runAppTestsOnBrowserStack", server.server.getClientVersion());
+            return await runAppTestsOnBrowserStack(args);
+        }
+        catch (error) {
+            trackMCP("runAppTestsOnBrowserStack", server.server.getClientVersion(), error);
+            const errorMessage = error instanceof Error ? error.message : "Unknown error";
+            return {
+                content: [
+                    {
+                        type: "text",
+                        text: `Error running App Automate test: ${errorMessage}`,
+                    },
+                ],
+                isError: true,
+            };
+        }
+    });
 }

package/dist/tools/bstack-sdk.js

@@ -1,9 +1,9 @@
 import { z } from "zod";
-import { SDKSupportedLanguageEnum, SDKSupportedBrowserAutomationFrameworkEnum, SDKSupportedTestingFrameworkEnum, } from "./sdk-utils/types.js";
-import { generateBrowserStackYMLInstructions, getInstructionsForProjectConfiguration, } from "./sdk-utils/instructions.js";
 import { trackMCP } from "../lib/instrumentation.js";
-import { formatPercyInstructions, getPercyInstructions, } from "./sdk-utils/percy/instructions.js";
 import { getSDKPrefixCommand } from "./sdk-utils/commands.js";
+import { SDKSupportedLanguageEnum, SDKSupportedBrowserAutomationFrameworkEnum, SDKSupportedTestingFrameworkEnum, } from "./sdk-utils/types.js";
+import { generateBrowserStackYMLInstructions, getInstructionsForProjectConfiguration, formatInstructionsWithNumbers, } from "./sdk-utils/instructions.js";
+import { formatPercyInstructions, getPercyInstructions, } from "./sdk-utils/percy/instructions.js";
 /**
  * BrowserStack SDK hooks into your test framework to seamlessly run tests on BrowserStack.
  * This tool gives instructions to setup a browserstack.yml file in the project root and installs the necessary dependencies.
@@ -12,36 +12,58 @@ export async function bootstrapProjectWithSDK({ detectedBrowserAutomationFramewo
     // Handle frameworks with unique setup instructions that don't use browserstack.yml
     if (detectedBrowserAutomationFramework === "cypress" ||
         detectedTestingFramework === "webdriverio") {
-        let instructions = getInstructionsForProjectConfiguration(detectedBrowserAutomationFramework, detectedTestingFramework, detectedLanguage);
+        let combinedInstructions = getInstructionsForProjectConfiguration(detectedBrowserAutomationFramework, detectedTestingFramework, detectedLanguage);
         if (enablePercy) {
             const percyInstructions = getPercyInstructions(detectedLanguage, detectedBrowserAutomationFramework, detectedTestingFramework);
             if (percyInstructions) {
-                instructions += formatPercyInstructions(percyInstructions);
+                combinedInstructions +=
+                    "\n\n" + formatPercyInstructions(percyInstructions);
             }
             else {
                 throw new Error(`Percy is currently not supported through MCP for ${detectedLanguage} with ${detectedTestingFramework}. If you want to run the test cases without Percy, disable Percy and run it again.`);
             }
         }
-        return {
-            content: [{ type: "text", text: instructions, isError: false }],
-        };
+        // Apply consistent formatting for all configurations
+        return formatFinalInstructions(combinedInstructions);
     }
-    let fullInstructions = "";
-    // Add language-dependent prefix command
-    fullInstructions += getSDKPrefixCommand(detectedLanguage, detectedTestingFramework);
+    // Handle default flow using browserstack.yml
+    const sdkSetupCommand = getSDKPrefixCommand(detectedLanguage, detectedTestingFramework);
     const ymlInstructions = generateBrowserStackYMLInstructions(desiredPlatforms, enablePercy);
-    fullInstructions += `${ymlInstructions}`;
     const instructionsForProjectConfiguration = getInstructionsForProjectConfiguration(detectedBrowserAutomationFramework, detectedTestingFramework, detectedLanguage);
+    let combinedInstructions = "";
+    // Step 1: Add SDK setup command
+    if (sdkSetupCommand) {
+        combinedInstructions += sdkSetupCommand;
+    }
+    // Step 2: Add browserstack.yml setup
+    if (ymlInstructions) {
+        combinedInstructions += "\n\n---STEP---\n" + ymlInstructions;
+    }
+    // Step 3: Add language/framework-specific setup
+    if (instructionsForProjectConfiguration) {
+        combinedInstructions += "\n\n" + instructionsForProjectConfiguration;
+    }
+    // Step 4: Add Percy setup if applicable
     if (enablePercy) {
         const percyInstructions = getPercyInstructions(detectedLanguage, detectedBrowserAutomationFramework, detectedTestingFramework);
         if (percyInstructions) {
-            fullInstructions += formatPercyInstructions(percyInstructions);
+            combinedInstructions +=
+                "\n\n" + formatPercyInstructions(percyInstructions);
         }
         else {
             throw new Error(`Percy is currently not supported through MCP for ${detectedLanguage} with ${detectedTestingFramework}. If you want to run the test cases without Percy, disable Percy and run it again.`);
         }
     }
-    fullInstructions += `\n\nAfter setting up the files above, follow these final steps:\n${instructionsForProjectConfiguration}`;
+    // Apply consistent formatting for all configurations
+    return formatFinalInstructions(combinedInstructions);
+}
+// Helper function to apply consistent formatting to all instruction types
+function formatFinalInstructions(combinedInstructions) {
+    const fullInstructions = `⚠️ IMPORTANT: DO NOT SKIP ANY STEP
+  All the setup steps described in this file MUST be executed regardless of any existing configuration or setup.
+  This ensures proper BrowserStack SDK setup.
+
+  ${formatInstructionsWithNumbers(combinedInstructions)}`;
     return {
         content: [
             {
@@ -53,7 +75,7 @@ export async function bootstrapProjectWithSDK({ detectedBrowserAutomationFramewo
     };
 }
 export default function addSDKTools(server) {
-    server.tool("runTestsOnBrowserStack", "Use this tool to get instructions for running tests on BrowserStack and browserstack percy", {
+    server.tool("runTestsOnBrowserStack", "Use this tool to get instructions for running tests on BrowserStack and BrowserStack Percy. It sets up the BrowserStack SDK and runs your test cases on BrowserStack.", {
         detectedBrowserAutomationFramework: z
             .nativeEnum(SDKSupportedBrowserAutomationFrameworkEnum)
             .describe("The automation framework configured in the project. Example: 'playwright', 'selenium'"),

package/dist/tools/sdk-utils/commands.js

@@ -20,7 +20,18 @@ const GRADLE_SETUP_INSTRUCTIONS = `
 export function getSDKPrefixCommand(language, framework) {
     switch (language) {
         case "nodejs":
-            return `Install BrowserStack Node SDK\nusing command | npm i -D browserstack-node-sdk@latest\n| and then run following command to setup browserstack sdk:\n npx setup --username ${process.env.BROWSERSTACK_USERNAME} --key ${process.env.BROWSERSTACK_ACCESS_KEY}\n\n. This will create browserstack.yml file in the project root. Edit the file to add your desired platforms and browsers. If the file is not created :\n`;
+            return `---STEP---
+Install BrowserStack Node SDK using command:
+\`\`\`bash
+npm i -D browserstack-node-sdk@latest
+\`\`\`
+---STEP---
+Run the following command to setup browserstack sdk:
+\`\`\`bash
+npx setup --username ${process.env.BROWSERSTACK_USERNAME} --key ${process.env.BROWSERSTACK_ACCESS_KEY}
+\`\`\`
+---STEP---
+Edit the browserstack.yml file that was created in the project root to add your desired platforms and browsers.`;
         case "java": {
             const mavenFramework = getJavaFrameworkForMaven(framework);
             const isWindows = process.platform === "win32";
@@ -33,11 +44,14 @@ export function getSDKPrefixCommand(language, framework) {
 -DBROWSERSTACK_ACCESS_KEY="${process.env.BROWSERSTACK_ACCESS_KEY}" \\
 -DBROWSERSTACK_FRAMEWORK="${mavenFramework}"`;
             const platformLabel = isWindows ? "Windows" : "macOS/Linux";
-            return `Install BrowserStack Java SDK
+            return `---STEP---
+Install BrowserStack Java SDK
 
 **Maven command for ${framework} (${platformLabel}):**
 Run the command, it is required to generate the browserstack-sdk-archetype-integrate project:
 ${mavenCommand}
+
+Alternative setup for Gradle users:
 ${GRADLE_SETUP_INSTRUCTIONS}`;
         }
         // Add more languages as needed

package/dist/tools/sdk-utils/constants.js

@@ -3,33 +3,45 @@ import config from "../../config.js";
  * ---------- PYTHON INSTRUCTIONS ----------
  */
 const pythonInstructions = `
-Run the following command to install the browserstack-sdk:
+---STEP---
+
+Install the BrowserStack SDK:
 \`\`\`bash
 python3 -m pip install browserstack-sdk
 \`\`\`
 
-Run the following command to setup the browserstack-sdk:
+---STEP---
+
+Setup the BrowserStack SDK with your credentials:
 \`\`\`bash
 browserstack-sdk setup --username "${config.browserstackUsername}" --key "${config.browserstackAccessKey}"
 \`\`\`
 
-In order to run tests on BrowserStack, run the following command:
+---STEP---
+
+Run your tests on BrowserStack:
 \`\`\`bash
 browserstack-sdk python <path-to-test-file>
 \`\`\`
 `;
 const generatePythonFrameworkInstructions = (framework) => `
-Run the following command to install the browserstack-sdk:
+---STEP---
+
+Install the BrowserStack SDK:
 \`\`\`bash
 python3 -m pip install browserstack-sdk
 \`\`\`
 
-Run the following command to setup the browserstack-sdk:
+---STEP---
+
+Setup the BrowserStack SDK with framework-specific configuration:
 \`\`\`bash
 browserstack-sdk setup --framework "${framework}" --username "${config.browserstackUsername}" --key "${config.browserstackAccessKey}"
 \`\`\`
 
-In order to run tests on BrowserStack, run the following command:
+---STEP---
+
+Run your ${framework} tests on BrowserStack:
 \`\`\`bash
 browserstack-sdk ${framework} <path-to-test-files>
 \`\`\`
@@ -42,7 +54,9 @@ const pytestInstructions = generatePythonFrameworkInstructions("pytest");
  */
 const argsInstruction = '<argLine>-javaagent:"${com.browserstack:browserstack-java-sdk:jar}"</argLine>';
 const javaInstructions = `
-Strictly Add the following dependencies to your \`pom.xml\`:
+---STEP---
+
+Add the BrowserStack Java SDK dependency to your \`pom.xml\`:
 \`\`\`xml
 <dependency>
     <groupId>com.browserstack</groupId>
@@ -61,13 +75,17 @@ dependencies {
 }
 \`\`\`
 
-Inform user to export:
+---STEP---
+
+Export your BrowserStack credentials as environment variables:
 \`\`\`bash
 export BROWSERSTACK_USERNAME=${config.browserstackUsername}
 export BROWSERSTACK_ACCESS_KEY=${config.browserstackAccessKey}
 \`\`\`
 
-Run tests using:
+---STEP---
+
+Run your tests using Maven:
 \`\`\`bash
 mvn clean test 
 \`\`\`
@@ -81,141 +99,174 @@ gradle clean test
  * ---------- CSharp INSTRUCTIONS ----------
  */
 const csharpCommonInstructions = `
-1. Install BrowserStack TestAdapter NuGet package  
-   Add the package to your project:
-   \`\`\`bash
-   dotnet add package BrowserStack.TestAdapter
-   \`\`\`
-
-2. Build the project  
-   \`\`\`bash
-   dotnet build
-   \`\`\`
-
-3. Set up BrowserStack SDK  
-   Replace the placeholders with your actual BrowserStack credentials:
-   \`\`\`bash
-   dotnet browserstack-sdk setup --userName ${config.browserstackUsername} --accessKey ${config.browserstackAccessKey}
-   \`\`\`
-
-4. Detect if you are running on Apple Silicon (macOS only)  
-   Run this check to determine if Apple Silicon-specific setup is required:
-   \`\`\`bash
-   ARCH="$(uname -m)"
-   if [ "$ARCH" = "arm64" ]; then
-     echo "Detected arm64 architecture - running Apple-Silicon flow"
-   fi
-   \`\`\`
-
-5. macOS (Apple Silicon) setup (required only if arm64 detected)  
-   Install the x64 version of .NET for BrowserStack compatibility.
-
-   - Check your current .NET version:
-     \`\`\`bash
-     dotnet --version
-     \`\`\`
-
-   - Ensure the path exists strictly; if not, create it first and then run the setup.
-     \`\`\`bash
-     sudo dotnet browserstack-sdk setup-dotnet --dotnet-path "<your-chosen-path>" --dotnet-version "<your-dotnet-version>"
-     \`\`\`
-     Common paths: /usr/local/share/dotnet, ~/dotnet-x64, or /opt/dotnet-x64
-
-6. Run the tests  
-   - For macOS (Apple Silicon), use the full path:
-     \`\`\`bash
-     <your-chosen-path>/dotnet browserstack-sdk
-     \`\`\`
-   - For Windows, Intel Macs, or if dotnet alias is configured:
-     \`\`\`bash
-     dotnet test
-     \`\`\`
+---STEP---
+
+Install BrowserStack TestAdapter NuGet package:
+\`\`\`bash
+dotnet add package BrowserStack.TestAdapter
+\`\`\`
+
+---STEP---
+
+Build the project:
+\`\`\`bash
+dotnet build
+\`\`\`
+
+---STEP---
+
+Set up BrowserStack SDK with your credentials:
+\`\`\`bash
+dotnet browserstack-sdk setup --userName ${config.browserstackUsername} --accessKey ${config.browserstackAccessKey}
+\`\`\`
+
+---STEP---
+
+Detect if you are running on Apple Silicon (macOS only):
+Run this check to determine if Apple Silicon-specific setup is required:
+\`\`\`bash
+ARCH="$(uname -m)"
+if [ "$ARCH" = "arm64" ]; then
+  echo "Detected arm64 architecture - running Apple-Silicon flow"
+fi
+\`\`\`
+
+---STEP---
+
+macOS (Apple Silicon) setup (Strictly follow if arm64 detected):
+Install the x64 version of .NET for BrowserStack compatibility.
+
+- Check your current .NET version:
+  \`\`\`bash
+  dotnet --version
+  \`\`\`
+
+- Ensure the path exists strictly; if not, create it first and then run the setup:
+  This automatically installs the x64 version of .NET in the specified path. No need to install it from external sources.
+  \`\`\`bash
+  sudo dotnet browserstack-sdk setup-dotnet --dotnet-path "<your-chosen-path>" --dotnet-version "<your-dotnet-version>"
+  \`\`\`
+  Common paths: /usr/local/share/dotnet, ~/dotnet-x64, or /opt/dotnet-x64
+
+---STEP---
+
+Run the tests:
+- For macOS (Apple Silicon), use the full path where the x64 version of .NET is installed:
+  \`\`\`bash
+  <your-chosen-path>/dotnet browserstack-sdk
+  \`\`\`
+- For Windows, Intel Macs, or if dotnet alias is configured:
+  \`\`\`bash
+  dotnet test
+  \`\`\`
 `;
 const csharpPlaywrightCommonInstructions = `
-1. Install BrowserStack TestAdapter NuGet package  
-   Run the following command:
-   \`\`\`bash
-   dotnet add package BrowserStack.TestAdapter
-   \`\`\`
-
-2. Build the project  
-   \`\`\`bash
-   dotnet build
-   \`\`\`
-
-3. Set up BrowserStack SDK  
-   Replace the placeholders with your actual credentials:
-   \`\`\`bash
-   dotnet browserstack-sdk setup --userName ${config.browserstackUsername} --accessKey ${config.browserstackAccessKey}
-   \`\`\`
-
-4. Supported browsers  
-   Use exactly one of the following (case-sensitive):  
-   \`chrome\`, \`edge\`, \`playwright-chromium\`, \`playwright-webkit\`, \`playwright-firefox\`
-
-5. Detect if you are running on Apple Silicon (macOS only)  
-   Run this check to determine if Apple Silicon-specific setup is required:
-   \`\`\`bash
-   ARCH="$(uname -m)"
-   if [ "$ARCH" = "arm64" ]; then
-     echo "Detected arm64 architecture - running Apple-Silicon flow"
-   fi
-   \`\`\`
-
-6. macOS (Apple Silicon) setup (required only if arm64 detected)  
-   Install the x64 version of .NET for compatibility with BrowserStack.
-
-   - Check your .NET version:
-     \`\`\`bash
-     dotnet --version
-     \`\`\`
-
-   - Ensure the path exists strictly; if not, create it first and then run the setup.
-     \`\`\`bash
-     sudo dotnet browserstack-sdk setup-dotnet --dotnet-path "<your-chosen-path>" --dotnet-version "<your-dotnet-version>"
-     \`\`\`
-     Common paths: /usr/local/share/dotnet, ~/dotnet-x64, or /opt/dotnet-x64
-
-7. Fix for Playwright architecture (macOS only)  
-   If the folder exists:  
-   \`<project-folder>/bin/Debug/net8.0/.playwright/node/darwin-arm64\`  
-   Rename \`darwin-arm64\` to \`darwin-x64\`
-
-8. Run the tests  
-   - For macOS (Apple Silicon), use the full path:
-     \`\`\`bash
-     <your-chosen-path>/dotnet browserstack-sdk
-     \`\`\`
-   - For Windows, Intel Macs, or if dotnet alias is configured:
-     \`\`\`bash
-     dotnet test
-     \`\`\`
+---STEP---
+
+Install BrowserStack TestAdapter NuGet package:
+\`\`\`bash
+dotnet add package BrowserStack.TestAdapter
+\`\`\`
+
+---STEP---
+
+Build the project:
+\`\`\`bash
+dotnet build
+\`\`\`
+
+---STEP---
+
+Set up BrowserStack SDK with your credentials:
+\`\`\`bash
+dotnet browserstack-sdk setup --userName ${config.browserstackUsername} --accessKey ${config.browserstackAccessKey}
+\`\`\`
+
+---STEP---
+
+Choose supported browser:
+Use exactly one of the following (case-sensitive):  
+\`chrome\`, \`edge\`, \`playwright-chromium\`, \`playwright-webkit\`, \`playwright-firefox\`
+
+---STEP---
+
+Detect if you are running on Apple Silicon (macOS only):
+Run this check to determine if Apple Silicon-specific setup is required:
+\`\`\`bash
+ARCH="$(uname -m)"
+if [ "$ARCH" = "arm64" ]; then
+  echo "Detected arm64 architecture - running Apple-Silicon flow"
+fi
+\`\`\`
+
+---STEP---
+
+macOS (Apple Silicon) setup (required only if arm64 detected):
+Install the x64 version of .NET for compatibility with BrowserStack.
+
+- Check your .NET version:
+  \`\`\`bash
+  dotnet --version
+  \`\`\`
+
+- Ensure the path exists strictly; if not, create it first and then run the setup:
+  This automatically installs the x64 version of .NET in the specified path. No need to install it from external sources.
+  \`\`\`bash
+  sudo dotnet browserstack-sdk setup-dotnet --dotnet-path "<your-chosen-path>" --dotnet-version "<your-dotnet-version>"
+  \`\`\`
+  Common paths: /usr/local/share/dotnet, ~/dotnet-x64, or /opt/dotnet-x64
+
+---STEP---
+
+Fix for Playwright architecture (macOS only):
+If the folder exists:  
+\`<project-folder>/bin/Debug/net8.0/.playwright/node/darwin-arm64\`  
+Rename \`darwin-arm64\` to \`darwin-x64\`
+
+---STEP---
+
+Run the tests:
+- For macOS (Apple Silicon), use the full path:
+  \`\`\`bash
+  <your-chosen-path>/dotnet browserstack-sdk
+  \`\`\`
+- For Windows, Intel Macs, or if dotnet alias is configured:
+  \`\`\`bash
+  dotnet test
+  \`\`\`
 `;
 /**
  * ---------- NODEJS INSTRUCTIONS ----------
  */
 const nodejsInstructions = `
-- Ensure that \`browserstack-node-sdk\` is present in package.json, use the latest version.
-- Add new scripts to package.json for running tests on BrowserStack (use \`npx\` to trigger the sdk):
-  \`\`\`json
-  "scripts": {
-    "test:browserstack": "npx browserstack-node-sdk <framework-specific-test-execution-command>"
-  }
-  \`\`\`
-- Add to dependencies:
-  \`\`\`json
-  "browserstack-node-sdk": "latest"
-  \`\`\`
-- Inform user to export BROWSERSTACK_USERNAME and BROWSERSTACK_ACCESS_KEY as environment variables.
+---STEP---
+
+Ensure \`browserstack-node-sdk\` is present in package.json with the latest version:
+\`\`\`json
+"browserstack-node-sdk": "latest"
+\`\`\`
+
+---STEP---
+
+Add new scripts to package.json for running tests on BrowserStack:
+\`\`\`json
+"scripts": {
+  "test:browserstack": "npx browserstack-node-sdk <framework-specific-test-execution-command>"
+}
+\`\`\`
+
+---STEP---
+
+Export BrowserStack credentials as environment variables:
+Set the following environment variables before running tests.
 `;
 /**
  * ---------- EXPORT CONFIG ----------
  */
 const webdriverioInstructions = `
-To integrate your WebdriverIO test suite with BrowserStack, follow these steps. This process uses the @wdio/browserstack-service and does not require a browserstack.yml file.
-
-**1. Set BrowserStack Credentials**
+---STEP---
 
+Set BrowserStack Credentials:
 Export your BrowserStack username and access key as environment variables.
 
 For macOS/Linux:
@@ -230,15 +281,17 @@ $env:BROWSERSTACK_USERNAME=${config.browserstackUsername}
 $env:BROWSERSTACK_ACCESS_KEY=${config.browserstackAccessKey}
 \`\`\`
 
-**2. Install the BrowserStack WDIO Service**
+---STEP---
 
+Install the BrowserStack WDIO Service:
 Add the service to your project's dev dependencies.
 \`\`\`bash
 npm install @wdio/browserstack-service --save-dev
 \`\`\`
 
-**3. Update your WebdriverIO Config File (e.g., wdio.conf.js)**
+---STEP---
 
+Update your WebdriverIO Config File (e.g., wdio.conf.js):
 Modify your configuration file to use the BrowserStack service and define the platforms you want to test on.
 
 Here is an example configuration:
@@ -310,29 +363,31 @@ exports.config.capabilities.forEach(function (caps) {
 });
 \`\`\`
 
-**4. Run your tests**
+---STEP---
 
+Run your tests:
 You can now run your tests on BrowserStack using your standard WebdriverIO command.
 `;
 const cypressInstructions = `
-To integrate your Cypress test suite with BrowserStack, follow these steps. This process uses the BrowserStack Cypress CLI and a \`browserstack.json\` file for configuration.
-
-**1. Install the BrowserStack Cypress CLI**
+---STEP---
 
+Install the BrowserStack Cypress CLI:
 Install the CLI as a dev dependency in your project.
 \`\`\`bash
 npm install browserstack-cypress-cli --save-dev
 \`\`\`
 
-**2. Create the Configuration File**
+---STEP---
 
+Create the Configuration File:
 Generate the \`browserstack.json\` configuration file in your project's root directory by running the following command:
 \`\`\`bash
 npx browserstack-cypress init
 \`\`\`
 
-**3. Configure \`browserstack.json\`**
+---STEP---
 
+Configure \`browserstack.json\`:
 Open the generated \`browserstack.json\` file and update it with your BrowserStack credentials and desired capabilities. Below is an example configuration.
 
 * **auth**: Your BrowserStack username and access key.
@@ -372,10 +427,12 @@ Open the generated \`browserstack.json\` file and update it with your BrowserSta
   }
 }
 \`\`\`
+
 **Note:** For Cypress v9 or lower, use \`"cypress_config_file": "./cypress.json"\`. The \`testObservability: true\` flag enables the [Test Reporting & Analytics dashboard](https://www.browserstack.com/docs/test-management/test-reporting-and-analytics) for deeper insights into your test runs.
 
-**4. Run Your Tests on BrowserStack**
+---STEP---
 
+Run Your Tests on BrowserStack:
 Execute your tests on BrowserStack using the following command:
 \`\`\`bash
 npx browserstack-cypress run --sync
@@ -395,7 +452,11 @@ export const SUPPORTED_CONFIGURATIONS = {
         },
     },
     java: {
-        playwright: {},
+        playwright: {
+            junit4: { instructions: javaInstructions },
+            junit5: { instructions: javaInstructions },
+            testng: { instructions: javaInstructions },
+        },
         selenium: {
             testng: { instructions: javaInstructions },
             cucumber: { instructions: javaInstructions },
@@ -412,6 +473,8 @@ export const SUPPORTED_CONFIGURATIONS = {
             xunit: { instructions: csharpCommonInstructions },
             nunit: { instructions: csharpCommonInstructions },
             mstest: { instructions: csharpCommonInstructions },
+            specflow: { instructions: csharpCommonInstructions },
+            reqnroll: { instructions: csharpCommonInstructions },
         },
     },
     nodejs: {

package/dist/tools/sdk-utils/instructions.js

@@ -19,7 +19,7 @@ export function generateBrowserStackYMLInstructions(desiredPlatforms, enablePerc
 # BrowserStack Reporting
 # ======================
 # A single name for your project to organize all your tests. This is required for Percy.
-projectName: BrowserStack Sample
+projectName: BrowserStack SDK Tests
 # A name for the group of tests you are running
 buildName: mcp-run
 
@@ -75,3 +75,23 @@ percyCaptureMode: manual`;
       \`\`\`
       \n`;
 }
+export function formatInstructionsWithNumbers(instructionText, separator = "---STEP---") {
+    // Split the instructions by the separator
+    const steps = instructionText
+        .split(separator)
+        .map((step) => step.trim())
+        .filter((step) => step.length > 0);
+    // If no separators found, treat the entire text as one step
+    if (steps.length === 1 && !instructionText.includes(separator)) {
+        return `**Step 1:**\n${instructionText.trim()}\n\n**✅ Verification:**\nPlease verify that you have completed all the steps above to ensure proper setup.`;
+    }
+    // Format each step with numbering
+    const formattedSteps = steps
+        .map((step, index) => {
+        return `**Step ${index + 1}:**\n${step.trim()}`;
+    })
+        .join("\n\n");
+    // Add verification statement at the end
+    const verificationText = `\n\n**✅ Verification:**\nPlease verify that you have completed all ${steps.length} steps above to ensure proper setup. If you encounter any issues, double-check each step and ensure all commands executed successfully.`;
+    return formattedSteps + verificationText;
+}

package/dist/tools/sdk-utils/percy/constants.js

@@ -1,8 +1,11 @@
 const javaSeleniumInstructions = `
-To manually capture screenshots, implement the following steps in your test script:
+Import the BrowserStack Percy SDK in your test script:
+Add the Percy import to your test file.
 
-1.  **Import the BrowserStack Percy SDK** in your test script.
-2.  Add the \`PercySDK.screenshot(driver, name)\` method at required points in your test script to capture the screenshots.
+---STEP---
+
+Add screenshot capture method at required points:
+Use the \`PercySDK.screenshot(driver, name)\` method at points in your test script where you want to capture screenshots.
 
 Here's an example:
 
@@ -26,26 +29,29 @@ public class YourTestClass extends YourBaseTest {
 \`\`\`
 `;
 export const nodejsSeleniumInstructions = `
-To manually capture screenshots, implement the following steps in your test script:
-   - Import the BrowserStack Percy SDK in your test script.
-   - Add the \`percy.snapshot(driver, name)\` method at required points in your test script to capture the screenshots you want.
-
-   \`\`\`javascript
-   const { percy } = require('browserstack-node-sdk');
-   describe("sample Test", () => {
-     // ... other imports and setup
-     
-     test("my test", async () => {
-       // ....
-       await percy.screenshot(driver, "My Snapshot")
-       // ....
-     });
-   })
-   \`\`\`
+Import the BrowserStack Percy SDK in your test script:
+Add the Percy import to your test file.
+
+---STEP---
+
+Add screenshot capture method at required points:
+Use the \`percy.snapshot(driver, name)\` method at points in your test script where you want to capture screenshots.
+
+\`\`\`javascript
+const { percy } = require('browserstack-node-sdk');
+describe("sample Test", () => {
+  // ... other imports and setup
+  
+  test("my test", async () => {
+    // ....
+    await percy.snapshot(driver, "My Snapshot")
+    // ....
+  });
+})
+\`\`\`
 `;
 const webdriverioPercyInstructions = `
-**1. Enable Percy in \`wdio.conf.js\`**
-
+Enable Percy in \`wdio.conf.js\`:
 In your WebdriverIO configuration file, modify the 'browserstack' service options to enable Percy.
 
 - Set \`percy: true\`.
@@ -79,8 +85,9 @@ exports.config = {
 };
 \`\`\`
 
-**2. Manually Capturing Screenshots (Optional)**
+---STEP---
 
+Manually Capturing Screenshots (Optional):
 If you set \`percyCaptureMode: 'manual'\` or want to take extra screenshots in \`auto\` mode, you need to add screenshot commands to your tests.
 
 First, install \`browserstack-node-sdk\`:
@@ -106,10 +113,13 @@ describe("My WebdriverIO Test", () => {
 \`\`\`
 `;
 const csharpSeleniumInstructions = `
-To manually capture screenshots alongside the auto mode, implement the following steps in your test script:
+Import the BrowserStack Percy SDK in your test script:
+Add the Percy import to your test file.
+
+---STEP---
 
-1. **Import the BrowserStack Percy SDK** in your test script.
-2. Add the \`PercySDK.Screenshot(driver, name)\` method at required points in your test script to get the screenshots you want.
+Add screenshot capture method at required points:
+Use the \`PercySDK.Screenshot(driver, name)\` method at points in your test script where you want to capture screenshots.
 
 Here's an example:
 

package/dist/tools/sdk-utils/types.js

@@ -30,4 +30,6 @@ export var SDKSupportedTestingFrameworkEnum;
     SDKSupportedTestingFrameworkEnum["nunit"] = "nunit";
     SDKSupportedTestingFrameworkEnum["mstest"] = "mstest";
     SDKSupportedTestingFrameworkEnum["xunit"] = "xunit";
+    SDKSupportedTestingFrameworkEnum["specflow"] = "specflow";
+    SDKSupportedTestingFrameworkEnum["reqnroll"] = "reqnroll";
 })(SDKSupportedTestingFrameworkEnum || (SDKSupportedTestingFrameworkEnum = {}));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@browserstack/mcp-server",
-  "version": "1.1.8",
+  "version": "1.1.9",
   "description": "BrowserStack's Official MCP Server",
   "main": "dist/index.js",
   "repository": {