MCP Server

Active

MIT

shaft-mcp MCP Server

io.github.ShaftHQ/shaft-mcp

SHAFT's MCP module for AI-driven browser automation, capture, and offline failure diagnosis.

What is the shaft-mcp MCP server?

shaft-mcp is the Model Context Protocol module of the SHAFT Java automation framework, exposing browser automation, capture, and offline deterministic failure diagnosis capabilities to AI agents. It is distributed as an OCI image (ghcr.io/shafthq/shaft-engine-mcp) and lets agentic tools like Claude or Cursor drive SHAFT-based Web, Mobile, API, CLI, and Database test workflows. It is one of several optional SHAFT modules (alongside Doctor, Heal, Capture, and AI) that add agent-assisted workflows on top of the core automation engine.

SHAFT is a Java 25, Maven-published automation framework covering Web, Mobile, API, CLI, and Database testing, with built-in driver management, synchronization, assertions, configuration, test data handling, and Allure-ready reporting. shaft-mcp packages SHAFT's browser automation, capture, and offline deterministic failure diagnosis features as an MCP server (via an OCI container image) so AI agents can interact with SHAFT-driven test automation and diagnostics directly. It is aimed at Java automation teams already using SHAFT who want to add agent-assisted workflows such as MCP, Doctor, and Heal on top of their existing test suites.

How to install shaft-mcp

Copy-paste configuration for popular MCP clients.

transport: stdio

Config generated by PluginBench — verify against the source before use.

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "shaft-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/shafthq/shaft-engine-mcp:10.2.20260628"
      ]
    }
  }
}

Cursor

~/.cursor/mcp.json

{
  "mcpServers": {
    "shaft-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/shafthq/shaft-engine-mcp:10.2.20260628"
      ]
    }
  }
}

Windsurf

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "shaft-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/shafthq/shaft-engine-mcp:10.2.20260628"
      ]
    }
  }
}

VS Code

.vscode/mcp.json

{
  "servers": {
    "shaft-mcp": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/shafthq/shaft-engine-mcp:10.2.20260628"
      ]
    }
  }
}

Claude Code

claude mcp add shaft-mcp -- docker run -i --rm ghcr.io/shafthq/shaft-engine-mcp:10.2.20260628

Use cases

Let an AI agent drive SHAFT-based browser automation for Web or Mobile test scenarios
Capture evidence/screenshots and logs during automated test runs for reporting
Perform offline deterministic diagnosis of test failures without re-running live systems
Integrate agentic workflows (MCP, Doctor, Heal) into existing SHAFT/Java test suites

shaft-mcp MCP server FAQ

What does the shaft-mcp server do?

It exposes SHAFT's browser automation, capture, and offline deterministic failure diagnosis capabilities as an MCP server so AI agents can drive and diagnose SHAFT-based test automation runs.

Is shaft-mcp free to use?

SHAFT is MIT licensed and published as an open-source Maven artifact; the MCP module is distributed as a free OCI container image on GitHub Container Registry.

How do I install shaft-mcp?

Pull and run the OCI image ghcr.io/shafthq/shaft-engine-mcp:10.2.20260628 and connect it as an MCP server in a compatible client like Claude or Cursor.

Does shaft-mcp require authentication?

The README does not describe any specific authentication requirements for the MCP server itself.

What kind of testing does SHAFT support besides browser automation?

SHAFT covers Web, Mobile, API (REST/GraphQL), CLI, and Database testing, with assertions, test data handling, and Allure-ready reporting.

What other agentic modules does SHAFT offer alongside MCP?

SHAFT also offers Doctor and Heal modules for agent-assisted diagnostics and self-healing test workflows, documented in its user guide.

README (reference)

Source of truth, from the repository.

SHAFT

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

Open the User Guide

</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

TypeScript

Apache-2.0

View repository →