mcpField
C

claudetest

Local
@fasteningcodeDeveloper Tools

About claudetest

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

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "fasteningcode-claudetest": {
      "command": "npx",
      "args": [
        "-y",
        "@fasteningcode/claudetest"
      ],
      "env": {
        "GITHUB_TOKEN": "<GITHUB_TOKEN>"
      }
    }
  }
}
Run commandnpx -y @fasteningcode/claudetest
Environment variables to set
GITHUB_TOKENSecretGitHub personal access token with repo and workflow scopes

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@fasteningcode/claudetest0.0.3

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.