Test Automator MCP Server

If you want an AI assistant working directly with Test Automator, the test automator mcp server is the bridge. A comprehensive, intelligent, and extensible testing automation platform powered by Large Language Models. Test Automator streamlines the process of generating, executing, and analyzing various types of software tests (unit, integration, end-to-end, API) for both web UI and backend logic.

What Test Automator does

A comprehensive, intelligent, and extensible testing automation platform powered by Large Language Models. Test Automator streamlines the process of generating, executing, and analyzing various types of software tests (unit, integration, end-to-end, API) for both web UI and backend logic.

Tools it exposes

Once connected, the assistant can call this tool directly:

• Prerequisites — The Prerequisites tool exposed by this server

Installing the test automator mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 2 environment variables: GOOGLE_API_KEY, DISPLAY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Python 3.11+ - Google API Key (for Gemini LLM) - Claude Code or Cursor with MCP support - Git

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Test Automator sits in that group, and the shape of its toolset — Prerequisites — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by iamsnh01, written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the test automator mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.