SHAFT MCP
Drive SHAFT Engine Selenium-based web automation and UI tests from your agent through an MCP server packaged for container or local stdio use.
Overview
SHAFT MCP is a MCP server for the Ship phase that provides Selenium-based web automation and testing through the SHAFT Engine.
What is this MCP server?
- SHAFT Engine (Selenium-based) web automation exposed as MCP tools
- OCI package ghcr.io/shafthq/shaft-mcp:9.4.20251116 with stdio transport
- Version aligned with SHAFT release 9.4.20251116
- Suited for agent-directed UI testing and browser workflows
- Package: ghcr.io/shafthq/shaft-mcp:9.4.20251116 (OCI, stdio)
- Engine: SHAFT (Selenium-based) web automation
- Server version: 9.4.20251116
Community signal: 8 GitHub stars.
What problem does it solve?
UI validation stays manual or fragmented when your agent cannot invoke a consistent Selenium test stack on demand.
Who is it for?
Developers already on SHAFT/Selenium who want agent-orchestrated UI automation in Docker or local stdio setups.
Skip if: Mobile-native-only apps, teams wanting zero browser dependencies, or pure API integration testing without a UI.
What do I get? / Deliverables
You can trigger SHAFT browser automation from MCP-aware agents so shipping checkpoints include repeatable web tests.
- Agent-invoked browser automation sessions using SHAFT Engine
- Repeatable UI test flows executable from MCP tool calls
Recommended MCP Servers
Journey fit
Canonical shelf in Ship because browser automation and regression testing happen when you harden the app before release, not during initial ideation. Testing subphase matches Selenium-oriented web automation, functional checks, and agent-triggered test flows via SHAFT MCP.
How it compares
Selenium test-engine MCP, not a lightweight curl or API mock skill.
Common Questions / FAQ
Who is SHAFT MCP for?
Solo and small-team web developers using SHAFT Engine who want Claude Code, Cursor, or similar agents to run browser automation via MCP.
When should I use SHAFT MCP?
Use it in the Ship phase when you need agent-driven UI regression, exploratory browser flows, or automated checks before release.
How do I add SHAFT MCP to my agent?
Configure the OCI image ghcr.io/shafthq/shaft-mcp:9.4.20251116 with stdio transport in your MCP settings, ensuring Docker or your runtime can pull and run the container.