Testastic MCP Server

A Model Context Protocol (MCP) server that exposes Testastic QA data and operations to AI assistants like Claude Desktop.

Building

cd mcp
npm install
npm run build

The compiled server is output to mcp/dist/index.js.

Claude Desktop Registration

Add the following to your Claude Desktop config file — no keys required:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "testastic": {
      "command": "node",
      "args": ["/absolute/path/to/blue-lilly/mcp/dist/index.js"]
    }
  }
}

Replace /absolute/path/to/blue-lilly with the actual path to this repository.

First-run authentication

On the first start, the server will automatically open https://blue-lilly.vercel.app/mcp/auth in your browser. Sign in with your @locastic.com Google account. The browser will redirect back to a local server on port 9876, store the session in ~/.testastic/auth.json (mode 600), and the MCP server will be ready.

Subsequent starts use the stored token and refresh it silently when needed. To re-authenticate, delete ~/.testastic/auth.json and restart Claude Desktop.

Replace `/absolute/path/to/blue-lilly` with the actual path to this repository.

After saving, restart Claude Desktop. The Testastic tools will be available in all conversations.

## Environment Variables

No environment variables are required in your Claude Desktop config. The MCP server
authenticates via the browser-based OAuth flow (stored in `~/.testastic/auth.json`) and
delegates privileged operations (such as user deletion) to the web app API.

## Available Tools

### Projects
- `list_projects` — all projects with member and case counts
- `get_project` — by id or name
- `create_project` — create a new project
- `update_project` — update name/description
- `archive_project` — soft-delete
- `restore_project` — un-archive
- `get_project_stats` — pass rate, fail count, open runs

### Test Suites
- `list_suites` — nested tree for a project
- `create_suite` — create suite (optionally nested)
- `rename_suite`
- `delete_suite`
- `move_suite`

### Test Cases
- `list_test_cases` — filter by suite, status, priority, search
- `get_test_case` — full case with steps
- `create_test_case` — with optional steps
- `update_test_case`
- `delete_test_case`
- `clone_test_case`
- `bulk_create_test_cases`
- `bulk_import_test_cases` — import from CSV

### Test Steps
- `list_steps`
- `create_step`
- `update_step`
- `delete_step`
- `reorder_steps`

### Test Runs
- `list_runs`
- `get_run`
- `create_run`
- `update_run`
- `delete_run`
- `complete_run`
- `rerun_failed`
- `get_run_summary`

### Run Cases
- `update_run_case`
- `assign_run_case`
- `bulk_update_run_cases`

### Attachments
- `list_attachments` — list attachments for a run case or test case
- `delete_attachment` — delete an attachment by ID

### Users
- `list_users`
- `get_user`
- `change_role`
- `remove_user`
- `list_invites`
- `create_invite`
- `cancel_invite`
- `resend_invite`

### Reporting
- `get_dashboard_stats`
- `get_pass_rate_trend`
- `get_failing_test_cases`
- `get_untested_cases`

### Stubs (not yet implemented)
- `add_label`, `remove_label`, `list_labels`
- `list_milestones`, `create_milestone`

## Development

Run in dev mode (no build step needed):

```bash
cd mcp
npm run dev