How do I get my Trigger.dev API key?

Log in to your Trigger.dev dashboard at **cloud.trigger.dev**. Open your project, then find the **API Keys** section in the project settings. Copy your **Secret API Key** (it starts with `tr_dev_` for development or `tr_prod_` for production). Paste it into the configuration field below. For Personal Access Tokens (used for admin operations), go to **Profile → Personal Access Tokens** tab instead.

Can my AI agent tell me why a background job failed in production?

Yes. Ask your agent to list failed runs and it returns the task name, error message, stack trace, execution duration, and retry count for each failure. You can then drill into a specific run to see the exact input payload and which step failed — cutting your debugging time from minutes to seconds.

What if I'm on-call and need to check job health at 2 AM?

Just ask your AI agent 'Are there any failed jobs in production?' and get an instant triage report — number of failures, which tasks are affected, when they started failing, and whether retries resolved them. No need to open a browser, log in, or navigate dashboards in the middle of the night.

Does it support multiple environments like dev, staging, and production?

Yes. Each API key is scoped to a specific environment (dev or prod), just like in Trigger.dev itself. You can configure separate integrations for each environment, or switch between them by updating the API key — giving you full control over which environment your AI agent queries.

Trigger.dev MCP Connector for Claude

A+

Equip your AI agent with direct access to Trigger.dev — manage background jobs, monitor task runs, and inspect workflow executions without opening the dashboard.

8 tools Official Updated Oct 1, 2026 Official Vinkius Partner

More Details Connect to Claude

Connect Trigger.dev to your AI agent and manage your background job infrastructure conversationally.

What you can do

Job Monitoring — List active, completed, and failed task runs with execution times, statuses, and error details.
Project Overview — Query projects, environments, and their associated job definitions.
Run Inspection — Drill into individual runs to view payloads, outputs, logs, and retry history.
Environment Management — Switch between dev, staging, and production environments to inspect runs across your deployment pipeline.

How it works

Subscribe to the Trigger.dev integration on the marketplace.
Generate a Secret API Key from your Trigger.dev dashboard (Project → API Keys section — keys start with tr_dev_ or tr_prod_).
Ask your AI agent to list job runs, check failures, or inspect task outputs.

Who is this for?

Backend Developers — Monitor background job health, debug failed runs, and verify task outputs without leaving your code editor.
DevOps Engineers — Track job execution across environments and identify bottlenecks in your processing pipeline.
Technical Leads — Get instant visibility into production job queues during incident response without switching to the Trigger.dev dashboard.

background-jobsworkflow-automationevent-driventask-schedulingobservabilitytypescript

Related Connectors

Flow MCP

12 tools Official

Manage projects, tasks, and team collaboration via AI agents with Flow (getflow.com).

A+ View details →

Sally MCP

12 tools Official

Keep frontline teams connected with an employee communication platform that reaches deskless workers through mobile and chat.

A+ View details →

TeamGantt MCP

12 tools Official

Plan projects with intuitive Gantt charts that show deadlines, dependencies, and team workloads in one visual timeline.

A+ View details →

BasicOps MCP

12 tools Official

Centralize team communication with task management, document sharing, and project tracking designed for small business clarity.

A+ View details →