For agents

Agent self-serve signup, MCP, CLI, llms.txt, API keys, and human verification — no browser OAuth on first connect.

For agents

Note:

You're an agent? Start here. Humans should use For humans and app.molar.it instead.

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

CapabilityBefore human verifiesAfter verify (claimed)
MCP read/run (scenarios, runs)✅ Limited scopes & rate caps✅ Full Free-tier scopes
molar init, scenarios validate/compile
Local clones (molar clone …)
Cloud clones via MCP✅ (within plan entitlements)
Debugger AI (mcp:debug)❌ on Free — Team+ or BYOK
High-risk explore/act scopes❌ — requires explicit OAuth consent

Note:

Agent signup availability: POST https://api.molar.it/api/v1/agent-signup returns 503 when agent signup is disabled in production. If you hit 503, ask your human to sign up at app.molar.it and mint a PAT at Settings → API Tokens instead.

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

TransportEndpointWhen
Remote HTTPhttps://mcp.molar.cloud/mcpDefault — Cursor, Claude Code, Windsurf
Local stdiomolar mcp serveAir-gapped; add --cloud-access for cloud tools via PAT

One-click install: mcp.molar.cloud/install

Details: MCP server setup

4. Scaffold and run

molar init
molar scenarios validate && molar scenarios compile
molar run    # requires Guard runner — run molar doctor first

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

  • molar_generate_scenarios_from_url
  • molar_run_scenarios

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

5. Credentials

MethodUse
Agent signup api_keyStored in ~/.config/molar/config.toml after signup
MOLAR_TOKEN env varCI and scripts
Dashboard PATHuman-minted at Settings → API Tokens — preferred for CI

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

Shipped CLI commands (today)

CommandPurpose
molar agent signupSelf-serve registration
molar agent signup verifySubmit 6-digit code
molar agent signup statusClaim status and scope restrictions
molar initScaffold .molar/ project
molar loginSave PAT to config (prompts if omitted)
molar scenarios validate / compileLint and compile .molar.md
molar runExecute compiled scenarios (via Guard runner)
molar clone <kind> --start|--stopLocal Stripe/Twilio/email/auth/S3 clones
molar trace openOpen a trace in the browser
molar mcp serveLocal stdio MCP server
molar doctorDependency health check
molar upgradeSelf-update

Full reference: CLI reference

Per-product MCP entry points

ProductStart withKey tools
CartographerCartographer MCP toolsmolar_generate_scenarios_from_url, molar_compile_scenario
GuardGuard quick startmolar_run_scenarios, molar_get_guard_status
ClonesClones quick startmolar_clone_spawn, molar_clone_seed
TraceTrace quick startmolar_replay_trace, molar_debug_run