# five46 MCP server

> An AI agent that tests applications or APIs using plain English goals and generates Playwright test specifications upon success.

- Repository: https://github.com/sekharsdet/five46
- Page: https://hostedmcp.org/servers/sekharsdet/five46
- Transport: stdio
- Stars: 3
- License: MIT
- Latest version: 0.2.3

## Install

### Claude Code

```sh
claude mcp add --env 'FIVE46_LLM_API_KEY=<YOUR_FIVE46_LLM_API_KEY>' --env 'FIVE46_LLM_PROVIDER=<FIVE46_LLM_PROVIDER>' five46 -- npx -y five46
```

### Cursor (`~/.cursor/mcp.json`)

```json
{
  "mcpServers": {
    "five46": {
      "command": "npx",
      "args": [
        "-y",
        "five46"
      ],
      "env": {
        "FIVE46_LLM_API_KEY": "<YOUR_FIVE46_LLM_API_KEY>",
        "FIVE46_LLM_PROVIDER": "<FIVE46_LLM_PROVIDER>"
      }
    }
  }
}
```

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "five46": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "five46"
      ],
      "env": {
        "FIVE46_LLM_API_KEY": "<YOUR_FIVE46_LLM_API_KEY>",
        "FIVE46_LLM_PROVIDER": "<FIVE46_LLM_PROVIDER>"
      }
    }
  }
}
```

### VS Code CLI

```sh
code --add-mcp '{"name":"five46","type":"stdio","command":"npx","args":["-y","five46"],"env":{"FIVE46_LLM_API_KEY":"<YOUR_FIVE46_LLM_API_KEY>","FIVE46_LLM_PROVIDER":"<FIVE46_LLM_PROVIDER>"}}'
```

### Claude Desktop (`claude_desktop_config.json`)

```json
{
  "mcpServers": {
    "five46": {
      "command": "npx",
      "args": [
        "-y",
        "five46"
      ],
      "env": {
        "FIVE46_LLM_API_KEY": "<YOUR_FIVE46_LLM_API_KEY>",
        "FIVE46_LLM_PROVIDER": "<FIVE46_LLM_PROVIDER>"
      }
    }
  }
}
```

### Codex

```sh
codex mcp add five46 --env 'FIVE46_LLM_API_KEY=<YOUR_FIVE46_LLM_API_KEY>' --env 'FIVE46_LLM_PROVIDER=<FIVE46_LLM_PROVIDER>' -- npx -y five46
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.five46]
command = "npx"
args = ["-y", "five46"]

[mcp_servers.five46.env]
FIVE46_LLM_API_KEY = "<YOUR_FIVE46_LLM_API_KEY>"
FIVE46_LLM_PROVIDER = "<FIVE46_LLM_PROVIDER>"
```

### Gemini CLI

```sh
gemini mcp add -s user -e 'FIVE46_LLM_API_KEY=<YOUR_FIVE46_LLM_API_KEY>' -e 'FIVE46_LLM_PROVIDER=<FIVE46_LLM_PROVIDER>' five46 npx -- -y five46
```

### Gemini settings.json (`~/.gemini/settings.json`)

```json
{
  "mcpServers": {
    "five46": {
      "command": "npx",
      "args": [
        "-y",
        "five46"
      ],
      "env": {
        "FIVE46_LLM_API_KEY": "<YOUR_FIVE46_LLM_API_KEY>",
        "FIVE46_LLM_PROVIDER": "<FIVE46_LLM_PROVIDER>"
      }
    }
  }
}
```

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `FIVE46_LLM_API_KEY` | yes | yes | Your own API key for the chosen provider (for bedrock, your AWS region instead) |
| `FIVE46_LLM_PROVIDER` | yes | no | LLM provider to use: openai, anthropic, gemini, groq, or bedrock |
| `FIVE46_MCP_ALLOW_DELETES` | no | no | Set to 1 to unlock DELETE (five46_api) and destructive-looking browser clicks (five46_test) |
| `FIVE46_MCP_ALLOW_WRITES` | no | no | Set to 1 to unlock POST/PUT/PATCH for the five46_api tool (read-only by default) |
| `FIVE46_MCP_CONCURRENCY` | no | no | Max concurrent scenarios for story mode (default: 2 for five46_test, 3 for five46_api; hard-capped at 5) |

## Tools (2)

- `five46_test`: Drive a real local Playwright browser toward a stated goal, one action at a time, using your own configured LLM key (BYOK). Writes a real, standalone, re-runnable Playwright spec on success. Discloses: the page's visible text/labels/values are sent to your configured LLM provider on every step. Clicking an element that looks like it deletes/deactivates/closes an account or permanently erases data (e.g. "Delete Account") is blocked for this server — set FIVE46_MCP_ALLOW_DELETES=1 in the server environment to unlock it. Never settable via a tool call argument. This is a best-effort heuristic on the clicked element's visible text, not a guarantee. On a real assertion failure (a genuine finding about the app, not a tooling issue), one additional LLM call analyzes the failure for a root-cause hypothesis — built only from information already visible to the agent during the run (never a new disclosure), always on for this tool, and included in the returned report as a hypothesis, not a confirmed diagnosis.
- `five46_api`: Drive real HTTP requests toward a stated goal, one request/assertion at a time, using your own configured LLM key (BYOK). Writes a real, standalone node:test script on success. Read-only for this server (GET/HEAD/OPTIONS only) — set FIVE46_MCP_ALLOW_WRITES=1 in the server environment to unlock POST/PUT/PATCH, FIVE46_MCP_ALLOW_DELETES=1 to separately unlock DELETE. Neither is ever settable via a tool call argument. Requests are restricted to the target base URL's own origin — no additional host allowlist is available via this tool. Discloses: request/response data, including response bodies (which may contain a live session token or other secret), is sent to your configured LLM provider on every step. On a real assertion failure, one additional LLM call analyzes the failure for a root-cause hypothesis — built only from information already visible to the agent during the run, always on for this tool, and included in the returned report as a hypothesis, not a confirmed diagnosis.

## FAQ

### How does five46 handle API testing?

You can test an API using the command `five46 api <base-url> --goal "..."`, which is read-only by default unless you explicitly pass the `--allow-writes` flag.

### What happens if the test fails?

The tool provides a pass or fail verdict, an exit code, a report with screenshots, and a root-cause hypothesis for the failure.

### Does it work with my own LLM keys?

Yes, it uses your own LLM key from providers like OpenAI, Anthropic, Gemini, Groq, or AWS Bedrock to drive the application.

### Can I use the generated tests without five46?

Yes, successful runs are saved as standalone Playwright or node:test specifications that can be run independently.
