shaft-mcp MCP Server
io.github.ShaftHQ/shaft-mcp
Java automation framework for Web, Mobile, API, CLI, and Database testing with MCP integration.
What this kind of tool is for
- Automate a build, test, or deployment step you repeat by hand.
- Review or refactor code in an existing repository without leaving your agent.
- Bridge an internal service or CLI into the agent toolset.
How to compare servers like this
- Scope of control:
- Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
- Environment fit:
- Match the runtime it expects (Node, Python, a container) to what you actually run.
- Maintenance signal:
- Check the last-commit date — dev tooling that lags upstream breaks first.
- Config surface:
- Prefer tools whose environment-variable or config keys are documented plainly.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the shaft-mcp MCP server?
The SHAFT MCP server is a Model Context Protocol integration for SHAFT, a Java 25 automation framework that provides browser automation, test capture, and offline deterministic failure diagnosis. It enables AI agents to leverage SHAFT's unified testing capabilities across web, mobile, API, CLI, and database layers.
SHAFT is a Maven-published Java automation framework that consolidates common test automation needs—drivers, synchronization, assertions, configuration, reporting, and evidence—into a single workflow. The MCP server exposes SHAFT's capabilities to AI agents, allowing them to perform browser automation, capture test evidence, diagnose failures offline, and execute end-to-end testing scenarios across multiple platforms.
How to install shaft-mcp
Copy-paste configuration for popular MCP clients.
{
"mcpServers": {
"shaft-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/shafthq/shaft-engine-mcp:10.3.20260930"
]
}
}
}Tools & capabilities
Tools this server exposes to the agent.
Web UI Automation— Browser driver management, synchronized actions, screenshots, and logs for web testing.Mobile Automation— Mobile driver management and synchronized actions for mobile app testing.API Testing— REST and GraphQL API workflows with request, response, and assertion support.CLI Testing— Command-line interface actions for system-level validation.Database Testing— Database actions for end-to-end validation and data verification.Evidence & Reporting— Allure-ready evidence, attachments, execution logs, and accessibility artifacts.Failure Diagnosis— Offline deterministic failure diagnosis and healing capabilities.
Use cases
- Automate end-to-end web and mobile application testing with synchronized actions and comprehensive reporting.
- Execute API testing workflows with REST and GraphQL support, including request/response validation.
- Perform cross-layer testing combining UI, API, CLI, and database actions in a single test suite.
- Capture and analyze test evidence with Allure-ready artifacts and accessibility reports.
- Diagnose and heal test failures offline using SHAFT's deterministic failure analysis.
shaft-mcp MCP server FAQ
SHAFT MCP is a Model Context Protocol integration for SHAFT, a Java automation framework. It allows AI agents to access SHAFT's testing capabilities including browser automation, API testing, mobile testing, and failure diagnosis.
SHAFT supports Web, Mobile, API, CLI, and Database testing, with optional modules for cloud execution (BrowserStack), capture, diagnostics, healing, AI, video, and visual testing.
Yes, SHAFT is MIT licensed and open-source, available on Maven Central.
The SHAFT MCP server is available as a Docker image: ghcr.io/shafthq/shaft-engine-mcp:10.3.20260930. Configure it in your MCP client (Cursor, Claude) using the OCI image reference.
SHAFT integrates with TestNG, JUnit, and Cucumber, providing a unified API across all frameworks.
Yes, SHAFT is configuration-first with built-in support for local, grid, cloud, and CI execution environments.
README (reference)
Source of truth, from the repository.
SHAFT
Java 25 automation framework for Web, Mobile, API, CLI, and Database testing.
</div>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.
Why SHAFT
- Java and Maven first, with TestNG, JUnit, and Cucumber integration.
- One workflow for Web, Mobile, API, CLI, Database, accessibility, reporting, and evidence.
- Configuration-first defaults for local, grid, cloud, and CI execution.
- Optional modules for BrowserStack, Capture, Doctor, Heal, MCP, AI, video, and visual testing.
Feature Overview
| 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 | Optional modules for cloud execution, capture, diagnostics, healing, MCP, AI, video, and visual checks. |
SHAFT is built for Java teams that want consistent APIs, repeatable configuration, and useful run artifacts across the full automation suite.
User Guide
- Start: overview, installation, upgrade.
- Testing: web, mobile, API.
- Agentic workflows: MCP, Doctor, Heal.
Contributing
Read CONTRIBUTING.md for local setup, validation, and pull request guidance.
MIT licensed. See LICENSE.
Related MCP servers

Prism
Local-first repository intelligence for AI agents: understand codebase DNA, health, blast radius, and impact analysis without uploading data.

DevTime
Local-first, read-only MCP server that verifies repository claims against code evidence without execution or cloud calls.
Search instances across GCP, AWS, K8s, Consul & Proxmox
Local-first flight recorder for AI agents: sessions, costs, loop runs, and stuck-loop flags.

passwerk
Offline EU Battery Passport compiler: ingest documents, map, validate (IDTA 02035), emit AASX.

mcp-airlock
Governance proxy for MCP servers: allowlist, dry-run enforcement, human confirmation, blast-radius limits, and audit trails.
