Maeris logo
Get started for free

Full Automation Setup

The setup_automation MCP tool runs a comprehensive, three-phase automation setup for your entire project in a single operation. It generates UI tests, extracts your API collection, and runs a security scan — then batches everything to the Maeris Portal.

Running Full Automation Setup

The setup automation command is invoked through your AI editor (Claude Code or Cursor) as an MCP tool call, or via the CLI:

maeris setup

You will be prompted for your base URL and asked which phases you want to include. Alternatively, you can pass options directly:

# Run all three phases maeris setup --all --url http://localhost:3000 # Skip security scan maeris setup --ui --api --url http://localhost:3000 # Run only API extraction maeris setup --api --url http://localhost:3000

The Three Phases

Phase 1: UI Test Generation

Scans your frontend source files (React, Vue, Angular, HTML) to build a code map, discovers all user flows, and generates Playwright test cases. Produces at least one positive and one negative test per flow.

Equivalent to running: maeris test generate

Phase 2: API Collection Extraction

Scans your codebase for all HTTP calls (fetch, axios, httpx, requests) and automatically creates a Maeris collection with all discovered endpoints, grouped by domain and including detected headers, request bodies, and environment variables.

Equivalent to running: maeris scan api

Phase 3: Security Scan

Runs an AI-guided static analysis of your codebase against OWASP Top 10 categories. Produces findings with severity levels and remediation guidance.

Equivalent to running: maeris scan security

Choosing What to Include

When run interactively, the setup wizard presents a checklist:

Maeris Full Automation Setup
============================

What would you like to include?

[x] Phase 1: UI Test Generation
[x] Phase 2: API Collection Extraction
[ ] Phase 3: Security Scan (takes 3-5 min)

Exclude specific test folders? (comma-separated, or press Enter to skip)
> node_modules, .next, dist

Base URL for tests: http://localhost:3000

Exclusions

Always exclude build output directories (dist, .next, build) and dependency folders (node_modules) to prevent false positives and speed up the scan.

Batch Saving to Portal

At the end of setup, all results from all phases are saved to the Maeris Portal in a single batch operation. This includes:

  • All generated UI test cases and their steps
  • The new API collection with all discovered endpoints
  • The auto-created environment with extracted variables
  • Security scan findings (if Phase 3 was included)

Syncing Scan Results

To manually push scan results to the portal after a standalone scan:

maeris scan push

This syncs the most recent API scan and security scan results to your Maeris application on the portal.

Related Guides