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.
에이전트 강화
게시자의 자체 명령입니다. PlugMCP 엔드포인트가 아닙니다.
Host a copy with our keys and logs.
docker run -i --rm ghcr.io/shafthq/shaft-engine-mcp:10.4.20261112Claude Code에는 로컬 명령용 설치 링크가 없습니다. 아래 명령을 복사해 터미널에서 실행합니다.
claude mcp add io.github.shafthq-shaft-mcp -- docker run -i --rm ghcr.io/shafthq/shaft-engine-mcp:10.4.20261112터미널에서 실행합니다.
{ "mcpServers": { "io.github.shafthq-shaft-mcp": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/shafthq/shaft-engine-mcp:10.4.20261112" ] } }}claude_desktop_config.json
원격 URL인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
실행Upgrade to SHAFT_ENGINE · ▶ Watch the 26-second clip with sound and captions · 100-second overview
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
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.
$shaft-developer, then the MCP tools or CLI commands.If SHAFT saves your team time, star the repo. It helps other testers find it.
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.
SHAFT browser automation, capture, and offline deterministic failure diagnosis
{ "mcpServers": { "io.github.shafthq-shaft-mcp": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/shafthq/shaft-engine-mcp:10.4.20261112" ] } }}도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 stdio 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
이 레코드에는 필수 환경 변수가 등록되어 있지 않습니다.
Shaft은(는) stdio를 통해 로컬에서 실행됩니다.
마지막 확인: 2026-11-16. SHAFT browser automation, capture, and offline deterministic failure diagnosis