S
SHAFT MCP
SHAFT browser automation, capture, and offline deterministic failure diagnosis
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Manual Client & Custom JSON ConfigExpand JSON ▾
Install Config Generator
Choose your client
💡 Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)
Documentation Overview
SHAFT
Java 25 automation framework for Web, Mobile, API, CLI, and Database testing.
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
- Start: overview, installation, upgrade.
- Testing: web, mobile, API.
- Agentic workflows: IntelliJ IDEA plugin, MCP, Doctor, Heal.
- Modular-era feature catalog — which optional module or command to adopt, with screenshots.
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):
From a repository checkout, the SHAFT installer copies the complete pack and shared generated catalogs to every agent-native project directory:
The skills CLI can install all 30 skill directories directly:
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:
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.
Related MCP Servers
Frequently Asked Questions about SHAFT MCP
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/shaft-mcp-2)HTML Embed
<a href="https://allmcps.com/mcp/shaft-mcp-2"><img src="https://allmcps.com/api/badge/shaft-mcp-2?style=directory" alt="SHAFT MCP on AllMCPs" /></a>Technical Specs & Signals
CategoryDeveloper Tools
0/4 checks healthy over the last 6h
27Quality signal: Emerging · 27/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership8/20
Documentation & tools11/30
Adoption & activity1/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to get the verified badge.
Free dofollow backlink: after claiming, verify your product site and place a dofollow AllMCPs badge — we recheck it stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.