Which integrations are available for this server?

Automatically commits and pushes test run results to a GitHub repository.

How do I use MCP Test Automation Framework?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP Test Automation Framework run the google search test and check in the results to GitHub" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

MCP Test Automation Framework

by rabbiyamehmood

Overview Schema Related Servers Score Discussions

TypeScript

Local

🤖 MCP Test Automation Framework

SQA Test Automation powered by Claude/Deepseek AI with self-healing locators and auto GitHub checkin

🏗️ Architecture

mcp-automation/
├── src/
│   ├── mcp/                  # MCP Server (connects AI to browser)
│   │   ├── mcp-server.ts     # MCP tool definitions & handlers
│   │   └── index.ts
│   ├── core/                 # Core modules
│   │   ├── browser-manager.ts  # Playwright browser lifecycle
│   │   ├── config.ts           # Settings loader
│   │   └── logger.ts           # Logging utility
│   ├── healing/              # Self-Healing Engine
│   │   └── locator-healer.ts   # Alternative locator strategies
│   ├── scripts/              # Utility scripts
│   │   └── git-auto-checkin.ts # Auto commit & push to GitHub
│   ├── tests/                # Test definitions
│   │   ├── types.ts
│   │   └── google-search.ts
│   ├── mcp-server-entry.ts   # MCP server entry point
│   └── runner.ts             # Direct test runner
├── config/
│   └── settings.json         # Framework configuration
├── logs/                     # Run logs & screenshots
├── .github/workflows/        # CI/CD pipeline
├── package.json
├── tsconfig.json
└── README.md

Related MCP server: LocatorLabs MCP Server

🔄 How It Works

  1. AI (Claude/Deepseek) calls MCP tool
          │
          ▼
  2. Playwright executes browser action
          │
          ▼
  3. Element not found? 
          │
          ▼
  4. Self-Healing Engine kicks in
     ┌─────────────────────────────┐
     │ Tries: role → text →        │
     │ placeholder → label → testId│
     │ → CSS → XPath → aria-label  │
     └─────────────────────────────┘
          │
          ▼
  5. Found? → Logs healing action, proceeds
     Not found? → Screenshot, reports failure
          │
          ▼
  6. GitHub Auto Checkin
     ┌─────────────────────────────┐
     │ Creates branch              │
     │ test-run/<name>-<timestamp> │
     │ Stages & commits all files  │
     │ Pushes to remote            │
     └─────────────────────────────┘

🚀 Quick Start

1. Install dependencies

npm install
npx playwright install chromium

2. Configure

Edit config/settings.json:

Set AI provider and API keys (via env vars)
Configure browser options
Set GitHub remote URL

3. Set API Keys (optional — for AI features)

set ANTHROPIC_API_KEY=sk-ant-...    # For Claude
set DEEPSEEK_API_KEY=sk-...         # For Deepseek

4. Run tests directly

npm run dev

5. Start MCP Server (for AI assistant connection)

npm run mcp-server

Then connect your AI assistant (Claude/Deepseek) to this MCP server.

🛠️ MCP Tools Available to AI

Tool	Description
`navigate`	Navigate to a URL
`click`	Click an element (with self-healing)
`type` / `fill`	Type text into fields (with self-healing)
`get_text`	Get element text (with self-healing)
`wait_for_selector`	Wait for element to appear
`screenshot`	Capture page screenshot
`press_key`	Press keyboard keys
`run_test`	Execute a full test case
`auto_checkin`	Commit & push to GitHub
`get_healing_summary`	View self-healing stats

🧪 Self-Healing

When a locator fails, the engine tries these strategies in order:

getByRole — Find by ARIA role
getByText — Find by text content
getByPlaceholder — Find by placeholder attribute
getByLabel — Find by associated label
getByTestId — Find by data-testid
CSS selector — Try original selector as CSS
CSS alternatives — e.g., textarea → input, attribute variations
[aria-label] — Find by aria-label attribute

All healing actions are logged to logs/healing-log.json.

📤 GitHub Auto Checkin

After each test run, the framework automatically:

Creates a new branch: test-run/<test-name>-<timestamp>
Stages all changed files (tests, logs, screenshots)
Commits with descriptive message
Pushes to remote

🔧 Configuration

See config/settings.json for all options:

Section	Key	Description
`ai`	`provider`	`"auto"`, `"claude"`, or `"deepseek"`
`browser`	`headless`	`true`/`false` for headed mode
`selfHealing`	`enabled`	Enable/disable self-healing
`selfHealing`	`maxRetries`	Max healing attempts per locator
`github`	`autoCheckin`	Enable auto commit/push
`logging`	`level`	`"debug"`, `"info"`, `"warn"`, `"error"`

📄 License

MIT

This server cannot be installed

license - not found

quality - not tested

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

–Release cycle

–Releases (12mo)

Commit activity

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rabbiyamehmood/mcp-test'

If you have feedback or need assistance with the MCP directory API, please join our Discord server