Happy slice of mcp pizzaMCP.pizza

SHAFT_ENGINE

MCP.Pizza Chef: ShaftHQ

Teams use SHAFT to write automated checks for websites, mobile apps, services, and databases without rebuilding the same plumbing every time — browsers, waiting, screenshots, and reports are handled for you. The optional assistant-facing module lets a coding assistant search SHAFT's documentation and run its commands while you work, so you can ask how to write a particular test rather than hunt through the manual. It is Java and Maven first, and pairs with an IntelliJ IDEA plugin.

Coding

Use This MCP server To

Ask how to write a test for a login page Search the testing guide without leaving my editor Turn a manual test I run by hand into an automated one Look up the right command for browser checks Set my project up so an assistant knows the testing rules

README

SHAFT logo

SHAFT

Java 25 automation framework for Web, Mobile, API, CLI, and Database testing.

Maven Central PR Gate Docs

Open the User Guide

SHAFT is a Maven-published Java automation framework that keeps the common test automation plumbing in one place: drivers, synchronization, assertions, configuration, test data, reporting, evidence, and optional agent-assisted workflows.

What You Get

Area Built in
UI automation Browser and mobile driver management, synchronized actions, screenshots, and logs.
Service testing REST and GraphQL API workflows with request, response, and assertion support.
System coverage CLI and Database actions for end-to-end validation beyond the browser.
Test design Assertions, validations, test data handling, and configuration overrides.
Reporting Allure-ready evidence, attachments, execution logs, and accessibility artifacts.
Extensions Opt-in modules for cloud execution, capture, diagnostics, healing, MCP, AI, video, and visual checks, plus an IntelliJ IDEA plugin.

Java and Maven first, with TestNG, JUnit, and Cucumber integration, and configuration-first defaults for local, grid, cloud, and CI execution. The IntelliJ IDEA plugin is the front door for agent-assisted work: plan from the SHAFT tool window, reuse existing code, review generated blocks, verify locally.

Documentation

Agent Skills

SHAFT ships a first-party skill pack in shaft-skills/ that routes the full software-testing lifecycle through 30 focused skills. Start every SHAFT task with $shaft-developer; it selects one lifecycle, implementation, or MCP/CLI specialist for the immediate output.

Install as a Claude Code plugin (ships the full pack, including the shared references/ lookups):

/plugin marketplace add ShaftHQ/SHAFT_ENGINE
/plugin install shaft-skills@shafthq

From a repository checkout, the SHAFT installer copies the complete pack and shared generated catalogs to every agent-native project directory:

python scripts/mcp/install_shaft_mcp.py --install-shaft-skills --json

The skills CLI can install all 30 skill directories directly:

npx skills add https://github.com/ShaftHQ/SHAFT_ENGINE/tree/main/shaft-skills --skill '*' --agent '*' -y

Its per-skill install omits the shared generated MCP/CLI catalogs, so prefer the Claude plugin or SHAFT installer when those lookups are needed. With an installer client selector, --install-shaft-skills targets .agents/skills, .claude/skills, or .github/skills for that client. For a multi-host project, call shaft_project_init_agents(loop="all", targetDirectory=".", overwrite=false) through a connected SHAFT MCP client; it creates or updates real host instruction files while preserving user prose.

On upgrade, the SHAFT installer removes only its seven verifiably owned retired skill folders; it leaves other user skills and files in the native directories intact. It refuses linked or junctioned native skill directories using Windows reparse-point checks, so an install cannot write outside the selected project.

Use direct MCP tools for interactive stateful work, for example shaft_guide_search with {"query":"page object model","maxResults":3}. Use SHAFT CLI for repeatable one-shot work:

shaft-cli guide search query="browser assertions" maxResults=3 --json
shaft-cli tools --cached

Exact current MCP names and CLI syntax live in the generated shaft-mcp-tools.md and shaft-cli-commands.md catalogs; skills never guess tool names or parameters.

Contributing

  • CONTRIBUTING.md — local setup, validation, and pull requests.
  • CODE_OF_CONDUCT.md — community expectations.
  • SECURITY.md — report a vulnerability privately, never as a public issue.

MIT licensed. See LICENSE.

SHAFT_ENGINE FAQ

Do I need to know Java?
Yes — SHAFT is a Java and Maven framework, so it is aimed at people who write test code.
Can I use this to have an assistant help write my tests?
Yes — the skill pack lets a coding assistant plan a test, reuse existing code, and show you the result to review.
Which assistants does it support?
It ships as a Claude Code plugin and can install its skills into other agent tools; the IntelliJ IDEA plugin is the main front door.
Does it need a key of its own?
No — the framework itself asks for no key; you use whatever assistant you already have.
What can it actually test?
Websites, mobile apps, services, command-line tools, and databases, with reports and screenshots included.
How hard is setup?
Expect real setup work: a Java project, Maven, and an installer command to add the assistant pieces.