Vibe Test — Browser Testing Agent MCP Server

What the code does

We read the source, 3 d ago · rules 995398eba69f

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

    await fs.writeFile(reportPath, `${JSON.stringify(diagnostic, null, 2)}\n`, 'utf8')

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    const content = await readFile(path.join(codebasePath, filePath))

    const child = spawn(process.execPath, [cliPath, ...args], {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add vibe-testing -- npx -y vibe-testing

{
  "mcpServers": {
    "vibe-testing": {
      "command": "npx",
      "args": [
        "-y",
        "vibe-testing"
      ]
    }
  }
}

[mcp_servers.vibe-testing]
command = "npx"
args = ["-y", "vibe-testing"]

{
  "mcpServers": {
    "vibe-testing": {
      "command": "npx",
      "args": [
        "-y",
        "vibe-testing"
      ]
    }
  }
}

{
  "servers": {
    "vibe-testing": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "vibe-testing"
      ]
    }
  }
}