Browser testing integrations

Run a browser check where you already work.

Choose the trigger you need. Each page explains the setup, where the verdict lands and the limits to account for, with links to the full guide and comparable benchmark runs.

The GitLab YAML is an example our team has not run in GitLab. Example results use illustrative values; benchmark reports are labelled separately.

Checked 2026-10-23.

CI/CD

  • GitHub Actions

    Run Monito browser tests from GitHub Actions with OIDC, wait for the verdict, and link failed checks to browser evidence on your pull request.

  • GitLab CI

    Run Monito after a GitLab deploy with an API key and the deployed URL. Includes an untested YAML example, URL handoff and protected-variable limits.

Deployments

  • Vercel

    Test Vercel previews with Monito's native webhook or a GitHub deployment_status workflow. Read the login and custom preview suffix limits first.

  • Deploy webhook

    Trigger Monito browser tests after deployment with a bearer-authenticated curl call. Queue a suite, pass a preview URL and read results in the dashboard.

    The webhook works from any pipeline that can run curl after a deploy.

Coding agents

  • Claude Code

    Connect Claude Code to Monito over MCP, check deployed or localhost changes, and follow each browser verdict to its report and screenshots.

  • Cursor

    Add Monito to Cursor's MCP configuration to test a URL, resume a browser run, and inspect failures through reports and screenshot evidence.

  • Codex

    Connect Codex to Monito's local MCP server, test deployed or localhost URLs, and resume browser runs to inspect verdicts and screenshots.

  • MCP server

    Connect an MCP client to Monito over Streamable HTTP and OAuth. Choose toolsets, run browser checks and inspect verdicts, credits and error codes.

Monitoring

  • Status pages

    Publish journey status on your-app.monito.page from eligible Monito browser runs. Learn which checks count, how failures are confirmed and the plan requirement.

Before you connect

Read the plan requirements for CI, webhooks and status pages. Inspect the benchmark method before using a report as evidence for your own application.