SHAFT ENGINE MCP Server

<div align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="shaft-engine/src/main/resources/images/shaft_white.png"> <img src="shaft-engine/src/main/resources/images/shaft_standard.png" alt="SHAFT logo" width="240"> </picture>

Write the test. SHAFT does the rest.

One Java engine for web, mobile, API, CLI, database, and desktop.<br> Drivers, waits, and evidence are handled. Every run ends in an Allure report.

 

_{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.}

<a href="https://github.com/ShaftHQ/SHAFT_ENGINE/releases/download/shaft-hero-video-20261017/shaft-hero-16x9.mp4"> <picture> <source media="(prefers-reduced-motion: reduce) and (prefers-color-scheme: dark)" srcset=".github/assets/readme/shaft-hero-thumb-dark-1280x720.jpg"> <source media="(prefers-reduced-motion: reduce)" srcset=".github/assets/readme/shaft-hero-thumb-light-1280x720.jpg"> <img src=".github/assets/readme/shaft-hero-loop.gif" alt="SHAFT in action: a 3-line test, mvn test passing, and the green Allure report it produces." width="820"> </picture> </a>

_{Upgrade to SHAFT_ENGINE · ▶ Watch the 26-second clip with sound and captions · 100-second overview}

</div>

Why SHAFT

• 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):

<dependency>
    <groupId>io.github.shafthq</groupId>
    <artifactId>shaft-engine</artifactId>
    <version>${shaft.version}</version>
</dependency>

Then write the test:

SHAFT.GUI.WebDriver driver = new SHAFT.GUI.WebDriver();
driver.browser().navigateToURL("https://shafthq.github.io/")
      .and().element().assertThat(By.cssSelector("h1")).isVisible();
driver.quit();

Run mvn test. The Allure report opens with every step, screenshot, and log.

Where to next

• Writing tests: the User Guide has setup, the full API, and examples.
• Using IntelliJ: shaft-intellij.
• Contributing or maintaining: CONTRIBUTING.md is the entry point to the maintainers guide.
• AI agents: AGENTS.md. Start with $shaft-developer, then the MCP tools or CLI commands.
• Training: hands-on courses at automatest.org.

<div align="center">

If SHAFT saves your team time, star the repo. It helps other testers find it.

</div>

---

Open an issue · Code of Conduct · Security · Sponsor

_{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.}