For agents

This path is for AI coding agents (Cursor, Claude Code, Codex, Windsurf, etc.) that need to register, connect MCP, and run scenarios without a human driving the browser first.

What agents can do today

0. Read the index

Fetch docs.molar.it/llms.txt — canonical URLs for every public doc page, agent-first ordering.

1. Self-serve signup

Register without a pre-existing account:

molar agent signup \
  --human-email alex@example.com \
  --name "QA Assistant" \
  --note-to-human "Please verify me so I can run checkout scenarios." \
  --harness claude-code

Or via API: POST https://api.molar.it/api/v1/agent-signup

Full request/response reference: Agent self-serve signup.

Before human verification: token scopes are limited to mcp:read and mcp:run. Cloud clones, debugger AI, and high-risk explore/act scopes stay blocked until verify.

2. Human verification

The overseer (human_email) receives a 6-digit code (15-minute expiry). Submit it:

molar agent signup verify --code 483921
# or: POST /api/v1/agent-signup/verify

Check status anytime: molar agent signup status

After verify, scopes expand to the Free tier (mcp:read, mcp:write, mcp:run, mcp:clone:write, mcp:trace:read). The human shares the code from their email — there is no dashboard approval UI yet.

3. Connect MCP

One-click install: mcp.molar.it

Details: MCP server setup

4. Scaffold and run

molar init --json
molar agent init --json   # credentials + connectivity (never prompts)
molar docs --json         # task-oriented command routing
molar scenarios validate && molar scenarios compile
molar run    # requires Guard runner — run molar doctor first
molar verify "app loads" --url http://localhost:3000 --json

verify automatically selects the authenticated local CloakBrowser daemon for localhost/private targets and needs no hosted token. Its JSON includes execution_mode plus owner-only screenshot, WebM, and HAR evidence paths. Use --execution hosted for cloud execution or --execution local to force local execution on a public URL.

Generate scenarios from a URL (MCP, not CLI):

1. Call molar_generate_scenarios_from_url with a project ID, authorized URL, and intent.
2. Poll molar_get_task; use molar_live_view while the task is in verified replay.
3. Require terminal completed, result.success: true, and verified on each selected flow.
4. Download the project-scoped molar_md, playwright, and manifest artifacts and validate their SHA-256 values.
5. Run the compiled Playwright with a fresh identity before committing or separately publishing the source.

For complex sign-up flows, use auth_context plus agent-comms/Clones for email verification, OTP, authentication, and test payments. Never put those values in the intent or scenario source. Retrying the same exact request resolves to the same durable task; stalled workers resume from checkpoints.

molar_run_scenarios executes scenarios after authoring. URL authoring itself never publishes a pull request.

Project config: .molar.md · Compiler: Scenario compiler

5. Credentials

molar login --token molar_pat_xxxx validates against GET /api/v1/me and saves credentials locally.

Shipped CLI commands (today)

Every failing path with --json returns { ok: false, error: { code, message, hint } }.

Full reference: CLI reference

Per-product MCP entry points

Related

• Documentation hub
• For humans
• OAuth & authentication
• Error codes