Trigger.dev background job platform — manage task runs, cancel or replay runs, and create cron schedules.
Use with AI AssistantsMCP
Connect Claude, Cursor, or any MCP-compatible client — then call tools directly
① Add This MCP Server
Paste into your AI client config — then all its tools are available instantly.
{
"mcpServers": {
"trigger-dev": {
"url": "https://mcp.aerostack.dev/s/aerostack/mcp-trigger-dev",
"headers": {
"Authorization": "Bearer YOUR_AEROSTACK_TOKEN"
}
}
}
}Replace YOUR_AEROSTACK_TOKEN with your API token from the dashboard.
② Call a Tool
Ask your AI assistant to call a specific tool, or send raw JSON-RPC:
Natural Language Prompt
“Use the _ping tool to verify trigger.dev credentials by calling a lightweight read endpoint. used internally by aerostack to validate credentials”
Using a Workspace?
Add this MCP to your Workspace — your team shares one token, secrets are stored securely, and every AI agent in the workspace can call it without per-user setup.
Trigger.dev background job platform — manage task runs, cancel or replay runs, and create cron schedules.
Live endpoint: https://mcp.aerostack.dev/s/aerostack/mcp-trigger-dev
This MCP server gives AI agents access to Trigger Dev via 7 tools. Connect it to any Aerostack workspace and your agents can interact with Trigger Dev directly.
| Tool | Description |
|---|---|
list_runs | List task runs in Trigger.dev with their status, task ID, and output. |
get_run | Get run details by ID including status, output, and timing information. |
cancel_run | Cancel a run that is currently queued or running. |
replay_run | Replay a completed or failed run with the same payload. |
list_schedules | List all scheduled tasks in Trigger.dev. |
create_schedule | Create a cron schedule for a task. |
delete_schedule | Delete a scheduled task by schedule ID. |
| Variable | Required | Description |
|---|---|---|
TRIGGER_DEV_API_KEY | Yes | Your Trigger.dev API key — found in Trigger.dev Dashboard → Account → API Keys |
Add the following secrets under Project → Secrets:
TRIGGER_DEV_API_KEYOnce added, every AI agent in your workspace can use Trigger Dev tools automatically.
curl -X POST https://mcp.aerostack.dev/s/aerostack/mcp-trigger-dev \
-H 'Content-Type: application/json' \
-H 'X-Mcp-Secret-TRIGGER-DEV-API-KEY: your-trigger-dev-api-key' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_runs","arguments":{}}}'
MIT
Live Endpoint
https://mcp.aerostack.dev/s/aerostack/mcp-trigger-dev
Sub-50ms globally · Zero cold start
@aerostack
Pre-built functions for the most common MCP tool patterns. Clone, extend, and deploy.
by @aerostack
8,000+ app integrations, trigger Zaps, run actions across Gmail, Slack, Sheets, HubSpot via Zapier's official MCP
by @aerostack
List, trigger, and manage n8n workflows — execute automations, check execution status, and manage credentials from any agent.
Yes. The Trigger Dev MCP includes a create_schedule tool that lets Claude create schedules in your Trigger Dev account from a plain-English prompt. You can also update and delete schedules — no Trigger Dev UI needed.
Yes. The Trigger Dev MCP includes tools to list and retrieve runs from your Trigger Dev account. Claude can filter, sort, and summarize runs based on your instructions.
Yes. The Trigger Dev MCP uses the open Model Context Protocol standard, so it works in Claude, Cursor, Windsurf, and any other MCP-compatible AI tool. All 7 Trigger Dev tools are available everywhere you connect it — install once on Aerostack.
Yes. Aerostack hosts the Trigger Dev MCP with encrypted credential storage and per-account authentication. Your Trigger Dev credentials are never shared with Claude's conversation — they're used server-side only.