Use BrowserStack Accessibility tools with the MCP server
Use natural language prompts in your AI assistant to run accessibility scans and get expert guidance for web and mobile apps.
Use the BrowserStack MCP server to run accessibility scans and get expert guidance for web and mobile apps directly from your coding assistant (such as GitHub Copilot, Claude, or Cursor). Skip the dashboard and start testing accessibility with simple prompts.
To use Accessibility tools on the BrowserStack MCP server, you need a BrowserStack Accessibility license. Contact BrowserStack support to enable a license for your account.
Streamline accessibility testing from your IDE
Use the following tools to run accessibility scans and get expert answers about WCAG, usability, and best practices, all through natural language prompts:
1. Run accessibility scan (runAccessibilityScan)
Use the runAccessibilityScan tool to instantly start accessibility scans for any website or app. This is the primary tool for automated accessibility checks.
Example: Using MCP server with Accessibility Scan using Github Copilot agent on VS Code

2. Ask accessibility expert (accessibilityExpert)
Use the accessibilityExpert tool to get expert answers about WCAG guidelines, usability, and accessibility best practices for your web or mobile app.
Example: Using MCP server with Accessibility Expert using Github Copilot agent on VS Code

Tool reference
Use the runAccessibilityScan tool to run automated accessibility checks, and the accessibilityExpert tool to get expert guidance on accessibility standards and best practices.
| Example Prompt | Description | Input Parameters | Invoked Tool |
|---|---|---|---|
| Run accessibility scan for “www.example.com” | Start a web accessibility scan and get a result link for the tested website. | • Website URL (required) • Scan type (optional) • Device/OS (optional) |
startAccessibilityScan |
| What WCAG guidelines apply to form field error messages on mobile web? | Get expert guidance on WCAG 2.0/2.1/2.2, mobile/web usability, and accessibility best practices. | • Question (required) • Context (optional) • App/website type (optional) |
accessibilityExpert |
Need help?
- FAQs for common questions.
- Troubleshoot for common issues.
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!