Claudetest

io.github.fasteningcodePublished by GitHub account fasteningcodev0.0.3Updated Oct 24, 2026

Playwright & Appium test automation for Claude. Generate tests, diagnose failures, open fix PRs.

VerifiedSTDIODesktop onlyBrowser AutomationDeveloper Tools

Overview

AI-generated overview

A local MCP server that brings Playwright and Appium test automation to Claude, letting it generate tests, diagnose failures and open fix pull requests.

What you can do
Generate automated tests for web and mobile apps using Playwright and Appium workflows, as described in the registry entry (no tools are listed in the manifest). Diagnose failing test runs and help identify what went wrong. Open pull requests with proposed fixes through GitHub, using the configured token. The manifest lists no individual tools, so exact capabilities beyond these described workflows are not documented.
When to use it
Useful when you want an assistant to help write or maintain Playwright and Appium test suites, investigate failing test runs, or propose fixes as pull requests in a GitHub repository.
Requirements
Runs as a local process over stdio, installed from the npm package @fasteningcode/claudetest, so Node.js and npm are needed. Requires a GitHub personal access token supplied in the GITHUB_TOKEN environment variable, with repo and workflow scopes. Desktop only; no web-hosted version.
Before you install
The server needs a GitHub personal access token with repo and workflow scopes, which grants broad read and write access to repositories and CI workflows; keep it scoped narrowly and treat it as sensitive. It can open pull requests, so changes may be pushed to your repositories. No tools are listed, so review what it actually does before granting access.

Installation

In SourceWeft

  1. Open Claudetest in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.0.3LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.