Automation commands

`sendmock ai install`

For each AI agent, the install command and its MCP configuration.

sendmock ai install --target <agent>

Flag	Type	Description
--target <agent>	string	Only this agent.One of: `claude-code`, `codex`, `cursor`, `gemini`, `vscode`Example: `claude-code`

sendmock ai install --target claude-code

Output with --json: AiAgentSetup[]. Exit codes: 0, 1, 2.

The SendMock agent skill as Markdown.

sendmock ai skill

sendmock ai skill

Output with --json: file (text/markdown). Exit codes: 0, 1, 2.

The latest events, newest first: the polling twin of the live stream.

sendmock events tail [flags]

Also runs as sendmock http tail, sendmock webhook tail.

Flag	Type	Description
--since <since>	string	Only events newer than this time.Example: `2026-10-26T09:30:00Z`
--type <type>	string	An event type, e.g. http.captured.Example: `http.captured`
--limit <limit>	integer	At most this many (default 50).Example: `50`
--project <project>	string	Only events about this project's emails, SMS and verifications (its key); every event when not set.Example: `shop`

sendmock events tail --since 2026-10-26T09:30:00Z --type http.captured

Output with --json: AppEvent[]. Exit codes: 0, 1, 2.

Copy-ready settings for a stack, as Settings > Connection shows them.

sendmock integrate <stack> [flags]

Argument	Type	Description
<stack>required	string	Your app's stack: a language (`laravel`, `node`, `python`, `go`, `java`, `ruby`, `dotnet`, `curl`) or a framework (`php`, `express`, `nestjs`, `django`, `flask`, `fastapi`, `spring`, `rails`, `aspnet`).Example: `laravel`

Flag	Type	Description
--channel <channel>	string	email, sms or http (default email).Example: `email`
--host <host>	string	Where the app runs: local, docker-host or compose.Example: `local`

sendmock integrate laravel --channel email --host local

Output with --json: IntegrationSnippet. Exit codes: 0, 1, 2, 3.

Run a scenario file step by step and report each step.

sendmock scenario run <file>

Argument	Type	Description
<file>required	path	A file whose text is sent as `scenario`: The scenario file's text, in TOML.Example: `otp-login.toml`

sendmock scenario run otp-login.toml

Output with --json: ScenarioReport. Exit codes: 0, 1, 2.

Check a scenario file without running it.

sendmock scenario validate <file>

Argument	Type	Description
<file>required	path	A file whose text is sent as `scenario`: The scenario file's text, in TOML.Example: `otp-login.toml`

sendmock scenario validate otp-login.toml

Output with --json: ScenarioValidation. Exit codes: 0, 1, 2.