MCP: BrowserStack
by BrowserStack
Official BrowserStack MCP server: run manual and automated tests on real browsers and devices, then debug and fix failing tests from your IDE in plain English.
Qase test management over MCP: 36 task-oriented tools for cases, runs, results, defects and QQL search, hosted at mcp.qase.io or self-run with your own API token.
Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.
Qase is a test management platform, and its official MCP server is a good example of a second-generation integration — it was rebuilt rather than extended. Version 2 consolidates v1's 83 tools down to 36 task-oriented ones (37 counting qase_discover_tools), explicitly to cut token usage and improve the accuracy with which a model picks the right call.
The consolidation shows up as composite tools that collapse a multi-step workflow into one call: qase_ci_report posts a batch of CI results, qase_triage_defect turns a failure into a defect, and there are equivalents for setting up a regression run. qase_project_context bootstraps an agent in a single call, returning a project's suites, milestones, environments, users and custom fields. Search runs through QQL, Qase's own query language, across cases, runs, results, defects and plans. Secondary tools stay hidden behind tool discovery so the default list stays short, and qase_api is an escape hatch to any REST endpoint the typed tools do not cover.
Test case review is supported — an agent can propose new cases or changes, assign reviewers and track status — with approving and merging deliberately left to the UI.
Two ways to run it. The hosted server at https://mcp.qase.io/mcp needs only a Qase login, but requires the Enterprise plan and a workspace on Qase's main cloud; on any other plan or a dedicated instance you run it yourself with npm install -g @qase/mcp-server and your own QASE_API_TOKEN, which works everywhere. Operationally it carries a two-tier tenant-safe cache (in-memory plus optional Redis), connection pooling and retry with backoff. MIT licensed, developed at qase-tms/qase-mcp-server.
by BrowserStack
Official BrowserStack MCP server: run manual and automated tests on real browsers and devices, then debug and fix failing tests from your IDE in plain English.
by MCPJam
Testing and evaluation workbench for MCP server authors — inspect tools and prompts, debug OAuth step by step, and score behaviour across 16 client configurations before shipping.
by CircleCI
CircleCI's official MCP server: pull build failure logs, hunt flaky tests, validate config, trigger and rerun pipelines, and roll back - in natural language from your IDE.
Expo's official remote MCP server — searches Expo docs, installs compatible SDK packages, triggers and monitors EAS builds, and drives iOS/Android simulators.