SHAFT browser automation, capture, and offline deterministic failure diagnosis
io.github.ShaftHQ/shaft-mcp Model Context Protocol (MCP) Server
The io.github.ShaftHQ/shaft-mcp MCP server provides an interface for SHAFT centered on browser automation, capture, and offline deterministic failure diagnosis. It is associated with Java testing and supports automation-focused workflows suitable for evidence-based test execution.
🛠️ Key Features
SHAFT browser automation
Capture capabilities
Offline deterministic failure diagnosis
🚀 Use Cases
Test automation within a Java ecosystem
End-to-end (E2E) and automation-engine workflows
Use in testing frameworks covering automation scenarios (e.g., web-driven testing)
⚡ Developer Benefits
Focus on deterministic failure diagnosis when running offline
Emphasis on automation and maintainable testing framework concepts (as described in the project excerpt)
⚠️ Limitations
Server capabilities beyond browser automation, capture, and offline diagnosis are not specified in the provided source data.
Usage (GA4 Engine property + GitHub API, as of 2026-10-29): 4,885,097 tests run and 53,062 active users in 30 days (2026-09-29 to 2026-10-28); 154,202 active users in 12 months (2025-10-29 to 2026-10-28); 36 countries (12-month window). The stars badge above is live.
No plumbing. Managed Selenium and Appium drivers, synchronized actions, and smart waits.
One fluent API. Web, mobile, REST/GraphQL, database, CLI, and desktop in the same test.
Evidence by default. Steps, screenshots, and logs land in an Allure report on every run.
Scale by configuration. Local, Grid, BrowserStack, or LambdaTest; TestNG, JUnit, or Cucumber.
Open and trusted. MIT licensed, on Maven Central, with public coverage.
How it works
Test intent and configuration enter SHAFT's orchestration layer, fan out across the execution surfaces you need, and come back as unified evidence.
flowchart LR
accTitle: SHAFT execution and evidence workflow
accDescr: Test intent and configuration enter SHAFT orchestration, run across Web, Mobile, API, and Native execution surfaces, and produce unified evidence.
I[Test intent] --> S[SHAFT orchestration]
C[Configuration] --> S
S --> W[Web]
S --> M[Mobile]
S --> A[API]
S --> N[Native, CLI, and Database]
W --> E[Unified evidence]
M --> E
A --> E
N --> E
Quickstart
Generate your first project and run mvn test. Already on Maven? Add io.github.shafthq:shaft-engine (version from the Maven Central badge):
BrowserStack, LambdaTest, Applitools, and JetBrains have provided tooling or open-source program support. This is support for the project, not a claim of financial sponsorship, customer status, or endorsement.