Trigger Dev MCP Server — Hosted Automation Integration
MCP Server language Hosted language PublicTrigger.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.
description Overview
mcp-trigger-dev — Trigger Dev MCP Server
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
What You Can Do
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.
Available Tools
| 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. |
Configuration
| Variable | Required | Description |
|---|---|---|
TRIGGER_DEV_API_KEY |
Yes | Your Trigger.dev API key — found in Trigger.dev Dashboard → Account → API Keys |
Quick Start
Add to Aerostack Workspace
- Go to aerostack.dev → Your Project → MCPs
- Search for "Trigger Dev" and click Add to Workspace
Add the following secrets under Project → Secrets:
TRIGGER_DEV_API_KEY
Once added, every AI agent in your workspace can use Trigger Dev tools automatically.
Direct API Call
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":{}}}'
License
MIT
terminal Tools (8)
Available tools on this MCP server. Each tool can be called directly from any AI agent.
_ping #1 Verify Trigger.dev credentials by calling a lightweight read endpoint. Used internally by Aerostack to validate credentials.
list_runs #2 List task runs in Trigger.dev with their status, task ID, and output.
get_run #3 Get run details by ID including status, output, and timing information.
cancel_run #4 Cancel a run that is currently queued or running.
replay_run #5 Replay a completed or failed run with the same payload.
list_schedules #6 List all scheduled tasks in Trigger.dev.
create_schedule #7 Create a cron schedule for a task.
delete_schedule #8 Delete a scheduled task by schedule ID.
Details
language Live Endpoint
https://mcp.aerostack.dev/s/aerostack/mcp-trigger-dev
Sub-50ms globally · Zero cold start
Publisher
Pre-built functions for the most common MCP tool patterns. Clone, extend, and deploy.
More in Automation
Browse Automation MCPs →Zapier Automation
by @aerostack
8,000+ app integrations, trigger Zaps, run actions across Gmail, Slack, Sheets, HubSpot via Zapier's official MCP
N8n
by @aerostack
List, trigger, and manage n8n workflows — execute automations, check execution status, and manage credentials from any agent.
Frequently asked questions
What is the Trigger Dev MCP server and what can it do? +
The Trigger Dev MCP server is hosted on Aerostack and exposes these tools to your AI agent: `_ping`, `list_runs`, `get_run`, `cancel_run`, `replay_run`. You get one hosted URL — no self-hosting — that works from Claude, Cursor, ChatGPT, Gemini, VS Code, or any MCP-compatible client, and you can share it with your team or combine it with other MCP servers in a workspace.
Is the Trigger Dev MCP server hosted, or do I have to run it myself? +
It's hosted on Aerostack's edge infrastructure — you don't deploy or maintain anything. Add it to a workspace and you get one authenticated URL, with secrets encrypted, that any AI agent or editor can connect to. Use it solo or share the same URL across your whole team.
Which AI agents and editors can use the Trigger Dev MCP server? +
Any MCP client: Claude and Claude Code, Cursor, ChatGPT, Gemini, Windsurf, Cline, VS Code, and custom agents. Because it's one hosted URL, the same Trigger Dev MCP server works everywhere — and you can compose it with other MCP servers, skills, and functions behind a single workspace URL.
How do I install the Trigger Dev MCP server in Claude Desktop? +
Add the following to your Claude Desktop config (`claude_desktop_config.json`): ```json { "mcpServers": { "@aerostack/mcp-trigger-dev": { "command": "npx", "args": ["-y", "@aerostack/@aerostack/mcp-trigger-dev"] } } } ``` Then restart Claude Desktop and the tools will appear automatically.
How do I use the Trigger Dev MCP server in Cursor? +
In Cursor, open **Settings → MCP** and add: ```json { "name": "@aerostack/mcp-trigger-dev", "command": "npx", "args": ["-y", "@aerostack/@aerostack/mcp-trigger-dev"] } ``` Save and reload Cursor. The MCP tools will be available in Agent mode.
Does Trigger Dev MCP require authentication? +
Yes. Trigger Dev requires authentication. Check the MCP's documentation for the required credentials.