shaft-mcp

io.github.ShaftHQPublished by GitHub account ShaftHQv10.4.20261102Updated Nov 3, 2026

SHAFT browser automation, capture, and offline deterministic failure diagnosis

VerifiedSTDIODesktop onlyBrowser AutomationDeveloper Tools

Overview

shaft's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open shaft-mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[SHAFT logo]

Write the test. SHAFT does the rest.

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

[Read the User Guide]   [Star SHAFT on GitHub]

[Maven Central] [Build] [Codecov] [SkillSpector]

[GitHub stars]

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.

[SHAFT in action: a 3-line test, mvn test passing, and the green Allure report it produces.]

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

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.

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

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

Then write the test:

java
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

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

[Star SHAFT on GitHub]


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.

Source: README.md at commit 04c6c31

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

13
  1. v10.4.20261102LatestNov 3, 2026
  2. v10.4.20261101Nov 1, 2026
  3. v10.4.20261031Oct 31, 2026
  4. v10.4.20261029Oct 29, 2026
  5. v10.4.20261024Oct 24, 2026
  6. v10.4.20261020Oct 20, 2026
  7. v10.4.20261013Oct 14, 2026
  8. v10.4.20261010Oct 10, 2026
  9. v10.4.20261009Oct 9, 2026
  10. v10.4.20261006Oct 9, 2026
  11. v10.4.20261003Oct 4, 2026
  12. v10.3.20260930Sep 30, 2026
  13. v10.3.20260911Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts