OLTestStack — AI Browser Testing Framework

MCP server that exposes high-level browser automation tools for AI agents. Internally drives Chromium via Puppeteer/CDP; externally presents flat, stateless MCP command payloads.

git clone https://github.com/openlearnia/OLTestStack.git
cd OLTestStack

Requirements

• Bun 1.0+ (or Node.js 20+)

• Chromium (bundled with Puppeteer, or set CHROMIUM_EXECUTABLE_PATH)

• Docker (optional, for PostgreSQL persistence)

Related MCP server: Chrome Profile MCP Server

Ports

MCP transport remains stdio (no TCP port for MCP).

Quick start (local MCP)

bun install
bun run typecheck
bun run dev

Docker + PostgreSQL quickstart

Persistence is optional. Active browser/page sessions stay in-memory for speed; recordings and test reports flush to Postgres on browser close when enabled.

# 1. Start Postgres (host port 5433)
cp .env.example .env
bun run docker:up

# 2. Apply migrations
bun run db:migrate

# 3. Enable persistence and start MCP server
export PERSIST_RECORDING=true
export DATABASE_URL=postgresql://oltest:oltest@localhost:5433/olteststack
bun run dev

Stop infrastructure:

bun run docker:down

Optional: run the app container with health endpoint on 8081:

docker compose --profile app up -d
curl http://localhost:8081/health

Run migrations inside Docker:

docker compose --profile migrate up migrate

Production warning: Default credentials in .env.example (oltest/oltest) are for local development only. Change POSTGRES_USER, POSTGRES_PASSWORD, and DATABASE_URL before deploying.

Run the MCP server

bun run dev

Or after building:

bun run build
bun run start

The server communicates over stdio — do not pipe logs to stdout (stderr only for diagnostics).

When PERSIST_RECORDING=true, the server validates DATABASE_URL at startup and writes reports/events to PostgreSQL on browser.close.

Cursor MCP configuration

Add to your Cursor MCP settings (.cursor/mcp.json or Cursor Settings → MCP):

{
  "mcpServers": {
    "olteststack": {
      "command": "bun",
      "args": ["run", "dev"],
      "cwd": "/Users/kartikbazzad/OLTestStack",
      "env": {
        "PERSIST_RECORDING": "false"
      }
    }
  }
}

Replace cwd with the absolute path to this project on your machine. Set PERSIST_RECORDING=true and DATABASE_URL if you want Postgres persistence.

Available tools (V1 partial — 19 of 22)

Planned (5): assert.exists, assert.text, assert.url, assert.network, test.run

Example flow

browser.launch  →  page.create  →  page.navigate  →  page.find  →  page.type  →  page.click  →  page.wait  →  page.screenshot  →  browser.close

Environment variables

Project structure

src/
├── core/          # Types, errors, registry, config, recording
├── cdp/           # Puppeteer CDP adapter
├── db/            # Drizzle schema, migrations runner, persistence
├── domain/        # Business logic (browser, page, elements)
├── health/        # Optional HTTP health endpoint
└── mcp/           # MCP server, tool registration

Scripts

Documentation

Agent-focused guides for MCP setup, tool reference, workflows, and Cursor skills:

• Guides index

• MCP Server Setup — install, configure Cursor/Claude, troubleshoot

• MCP Tools Reference — schemas, examples, error codes

• Agent Workflows — recommended patterns for AI agents

• Skills — Cursor Agent Skills for browser testing

Cursor setup: project skills (.cursor/skills/) and subagents (.cursor/agents/) ship with the repo; OLTestStack rules live at user level (~/.cursor/rules/olteststack-mcp-usage.mdc, olteststack-typescript.mdc) — see Guides index.

What's next

Phases 5–12 add user actions (page.click, page.type), inspection, monitoring, waiting, assertions, recording reports, and test.run orchestration. See docs/plans/v1-implementation-plan.md.