SHAFT_ENGINE

MCP Server

Java test automation framework for web, mobile, API, CLI, database, and desktop E2E testing with a fluent API and bui...

Copy the install, test the workflow, then decide if it earns a permanent slot.

391

Why nowLower urgency

The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.

DecisionWorth testing this week

Copy the install, test the workflow, then decide if it earns a permanent slot.

Trial costFast eval

You can test this quickly and remove it cleanly if it misses.

Risk43/100

GitHub health unknown. no security policy. 0 open issues make this testable, but not something to trust blind.

What You Are Adopting

AI Agent

Universal

Model

Multiple

One command inClean rollbackLow commitment

RegistryAdds a named entry to Claude config. One command to remove.

Fastest way to find out if SHAFT_ENGINE belongs in your setup.

Copy the install command, run a real test, and back it out cleanly if it slows you down.

Try now

claude mcp add shaft-engine -- npx shaft-engine

Run this first. You will know quickly if the workflow earns a permanent slot.

Back out

claude mcp remove shaft-engine

No messy cleanup loop. If it misses, remove it and keep moving.

Install Location

~/  └─ .claude.json    └─ mcp_servers/      └─ shaft-engine ← registers here

Java test automation framework for web, mobile, API, CLI, database, and desktop E2E testing with a fluent API and built-in reporting.

Submitted June 22, 2026