PeopleInvite a teammate
Priya · Owner online
Put verification where code gets written.
Use the interface that fits: a CLI command in a terminal, MCP from a coding agent, or Playwright oriented work with structured evidence beside it.
scoped invite
Access grantedProject dashboard
Observed resultMember access scoped correctlyInvite accepted · state matches policy
CLI commands
Run a bounded goal with a URL and request JSON output for scripts and agents.
MCP tools
Connect an MCP compatible client to authorized browser, run, and trace workflows.
Playwright friendly
Keep editable browser tests and bring supported generated flows into engineering work.
A small verification loop
After changing a login form, run molar verify "login works" --url http://localhost:3000 --json. Read the result, inspect evidence, and rerun after a fix.
- Local and hosted targets
- JSON results
- Trace references
PeopleInvite a teammate
Priya · Owner online
scoped invite
Access grantedProject dashboard
Observed resultMember access scoped correctlyInvite accepted · state matches policy
Build interfaces into tools
Use CLI and MCP where a coding agent or CI job needs to start work and inspect the outcome. Availability depends on authentication and deployment.
- MCP clients
- Scoped credentials
- Quickstart documentation
billing.acme.test
Browser taskFind August invoice
Aug 2026 Paid
Downloaded
A few things
you might be wondering.
Have a specific workflow in mind?
Let’s talk it through
Which command should I start with?
Use `molar verify` for a browser claim and `molar run` for a scenario or task. Add `--json` for agent output.
Where is the hosted MCP endpoint?
The hosted endpoint is documented at https://docs.molar.it and requires configured credentials and scopes.
Can I keep Playwright?
Yes. Molar can complement Playwright workflows; export support varies by setup.
Connect your developer workflow.
Choose a concrete workflow. We’ll help you get the right setup for your application.