The scheduling layer your stack is missing.

Schedule, trigger, and run any endpoint with retries, secrets, execution history, CLI, and MCP support.

Start Scheduling Quickstart

No credit card requiredFirst 500 calls free

System Card v2.04

GET /api/v1/sync_users

Frequency

0 0 * * *

Status

Active

Dashboard

CLI

MCP

Launch-ready access

Meet users where they already work.

The fastest path to conversion is lowering setup friction. TrigRun works from the app, terminal, and agent tools on day one.

robot_2

For agents

Hosted MCP server

Connect Cursor, Claude, or any MCP client to TrigRun so agents can create jobs, inspect executions, and manage secrets through tool calls.

Remote Streamable HTTP endpointView MCP setup

terminal

For builders

CLI for scripts and CI

Use the TrigRun CLI in your terminal, CI jobs, and deployment flows to create, pause, resume, and replay scheduled jobs without leaving code.

Install with npm and automate fastExplore the CLI

description

For copilots

AI-ready docs

Give coding agents clean context with OpenAPI, llms.txt, and focused docs so they can integrate TrigRun correctly on the first pass.

OpenAPI, llms.txt, and guidesRead AI docs

Why teams switch

flash_on

Ship faster

Create a production-ready scheduled endpoint in minutes from the dashboard, CLI, or MCP tools.

Dashboard, CLI, MCP

shield_locked

Run safely

Protect secrets, keep private networks blocked, and avoid flaky retries with guardrails built in.

Secrets, SSRF guards

query_stats

Debug clearly

Inspect every execution, replay failures, and understand what happened without stitching logs together.

Logs, retries, replays

Step 01

Create with ease

Define your endpoint, headers, and payload. The dashboard handles signing, secrets, and request configuration without forcing you into a custom queue.

check_circleCustom HTTP headers
check_circleJSON payload support
check_circleEncrypted secret management

Step 02

Schedule precisely

Use the visual builder, drop in a raw crontab string, or automate through the CLI and API. Timezone support is built in so jobs run when you expect.

"0 12 * * MON"// Every Monday at noon

Step 03

Inspect and refine

Review every execution with response codes, latencies, logs, and replay controls. When something fails, you can see it fast and recover without guesswork.