Skip to main content
mcpSource-backedReview first Safety Privacy

Trigger.dev MCP Server for Claude

Initialize projects, trigger task runs, deploy to environments, and monitor execution from Claude — with the official Trigger.dev MCP server for background job and AI agent workflow orchestration.

HarnessClaude CodeCodexCursorClaude Desktop
Review first review before installing

Open the source and read safety notes before installing.

Safety notes

  • The MCP server can trigger task runs and deploy code to production environments — review Claude's proposed actions before confirming.
  • The `search_docs` tool works without authentication; all other tools require CLI login.
  • Triggered runs incur usage against your Trigger.dev plan; be mindful when using bulk trigger operations.

Privacy notes

  • Project configurations, task definitions, run histories, and dashboard metrics from your Trigger.dev workspace are surfaced in Claude's context.
  • Authentication uses the Trigger.dev CLI session token stored locally — no credentials are embedded in the MCP server configuration.

Prerequisites

  • A Trigger.dev account — log in via the CLI when prompted (`npx trigger.dev@latest login`).
  • Node.js 18+ for `npx`.
  • An MCP client such as Claude Code or Claude Desktop.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
5 minutes
Difficulty
beginner
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "trigger": {
      "command": "npx",
      "args": ["trigger.dev@latest", "mcp"]
    }
  }
}

About this resource

Overview

The Trigger.dev MCP Server is the official Model Context Protocol server for Trigger.dev, the open-source platform for durable background jobs and AI agent workflows. It connects Claude directly to your Trigger.dev projects — letting you initialize new projects, trigger task runs, deploy to environments, monitor execution, and search documentation from your IDE.

Authentication uses the Trigger.dev CLI session. The documentation search tool (search_docs) works without any credentials, so you can start asking questions about the platform before logging in.

Key capabilities

  • Documentation search — search Trigger.dev docs without authentication.
  • Project initialization — scaffold new Trigger.dev projects from Claude.
  • Project management — list and manage projects and organizations.
  • Task triggering — invoke tasks by name with payloads, inspect task definitions.
  • Deployment — deploy to staging or production environments.
  • Run monitoring — filter and inspect run details, query execution history.
  • Metrics — query dashboard metrics via TRQL.

How it compares

Server Task triggering Deployment Run monitoring Docs search Auth
Trigger.dev MCP Yes Yes Yes Yes CLI login
Inngest MCP Yes (local) No Yes (local) Yes None (local)
Temporal MCP (community) Yes No Limited No API key
Modal MCP (community) Limited No Limited No API key

Trigger.dev is a managed, cloud-hosted platform with full durable execution semantics, retries, concurrency controls, and scheduling — making the MCP server well-suited for production background job management.

Installation

Claude Code (recommended)

npx trigger.dev@latest install-mcp --client claude-code

This wizard automatically configures the MCP server for Claude Code. Log in via the CLI if prompted:

npx trigger.dev@latest login

Manual configuration (Claude Code / Claude Desktop)

{
  "mcpServers": {
    "trigger": {
      "command": "npx",
      "args": ["trigger.dev@latest", "mcp"]
    }
  }
}

Requirements

  • A Trigger.dev account.
  • Node.js 18+ (for npx).
  • An MCP client (Claude Code or Claude Desktop).

Security

  • Authentication uses the Trigger.dev CLI session — credentials are stored locally in the CLI's session store, not in the MCP config.
  • Deployment and trigger tools require CLI login, preventing unauthenticated workflow execution.

Source Verification Notes

Verified on 2026-06-18:

  • Trigger.dev's MCP introduction at trigger.dev/docs/mcp-introduction confirms the npx trigger.dev@latest install-mcp install path, CLI-based authentication, and the tool surface including docs search, project init, task triggering, deployment, and run monitoring.
  • Trigger.dev's changelog at trigger.dev/changelog/official-mcp-server documents the official MCP server launch as part of Launch Week 2.
  • GitHub repo triggerdotdev/trigger.dev (Apache-2.0, 15k+ stars) is the official open-source codebase.

Source citations

Add this badge to your README

Show that Trigger.dev MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/triggerdev-mcp-server.svg)](https://heyclau.de/entry/mcp/triggerdev-mcp-server)

How it compares

Trigger.dev MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldTrigger.dev MCP Server for Claude

Initialize projects, trigger task runs, deploy to environments, and monitor execution from Claude — with the official Trigger.dev MCP server for background job and AI agent workflow orchestration.

Open dossier
Inngest MCP Server for Claude

Connect Claude to your local Inngest Dev Server — list functions, send events, invoke functions, monitor run status, and search Inngest documentation — with the built-in Inngest Model Context Protocol server that ships with the Inngest dev environment.

Open dossier
Taskade MCP Server for Claude

Connect Claude to Taskade — manage workspaces, projects, tasks, and AI agents — with the official Taskade MCP server, covering 57 tools for the full Taskade platform including projects, tasks, AI agent conversations, media, and templates.

Open dossier
CueAPI MCP Server for Claude

Official CueAPI stdio MCP server for scheduling agent work, claiming executions, and reporting evidence-backed outcomes with verified handoffs across time and environments.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorTrigger.devInngestTaskadeCueAPI
Added2026-06-182026-06-182026-06-182026-06-14
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesThe MCP server can trigger task runs and deploy code to production environments — review Claude's proposed actions before confirming. The `search_docs` tool works without authentication; all other tools require CLI login. Triggered runs incur usage against your Trigger.dev plan; be mindful when using bulk trigger operations.The MCP server runs locally alongside your Inngest dev server — it has no network access and cannot affect production environments. `send_event` and `invoke_function` trigger real function executions in your local dev environment; confirm before running functions with external side effects.Tools can create, update, and delete projects, tasks, and AI agents in your Taskade account — changes affect live data. AI agent tools (`agentCreate`, `agentUpdate`, `agentDelete`) modify live agent configurations — review before executing.cueapi_delete_cue and cueapi_fire_cue are destructive or side-effecting; confirm targets before approval. Worker claim tools mutate execution state; misconfigured heartbeats can lose leases on in-flight jobs. Webhook payloads from fired cues may trigger external systems; validate callback URLs. API keys prefixed cue_sk_* grant account-level scheduling and execution access.
Privacy notesProject configurations, task definitions, run histories, and dashboard metrics from your Trigger.dev workspace are surfaced in Claude's context. Authentication uses the Trigger.dev CLI session token stored locally — no credentials are embedded in the MCP server configuration.Function definitions, event payloads, run logs, and Inngest documentation content from your local dev server are surfaced in Claude's context. No API keys or credentials are required — the MCP server runs entirely on localhost without sending data to Inngest's servers.Workspace names, project content, task details, and AI agent conversation history from your Taskade account are surfaced in Claude's context. Your `TASKADE_API_KEY` grants full account access — keep it in the MCP config env and never commit it to version control.Execution history, callback URLs, and outcome evidence may include internal system identifiers. Store CUEAPI_API_KEY in MCP env vars, not in chat, issues, or committed config files. Self-hosted deployments keep data within your infrastructure per your CueAPI core configuration.
Prerequisites
  • A Trigger.dev account — log in via the CLI when prompted (`npx trigger.dev@latest login`).
  • Node.js 18+ for `npx`.
  • An MCP client such as Claude Code or Claude Desktop.
  • Node.js installed — run `npx inngest-cli@latest dev` to start the Inngest Dev Server before connecting.
  • The Inngest Dev Server must be running at `http://localhost:8288` for the MCP endpoint to be available.
  • An MCP client such as Claude Code or Claude Desktop.
  • A Taskade account — log in at taskade.com.
  • A Taskade API key: Settings → Apps & Integrations → API → Generate API Key.
  • Node.js with `npx` available.
  • An MCP client such as Claude Code or Claude Desktop.
  • CueAPI account and API key prefixed with cue_sk_ from https://cueapi.ai.
  • Node.js 18+ with npx available for @cueapi/mcp.
  • Claude Desktop, Claude Code, Cursor, Zed, or another MCP host with stdio support.
  • Optional CUEAPI_BASE_URL when self-hosting CueAPI core instead of the hosted API.
Install
npx trigger.dev@latest install-mcp --client claude-code
claude mcp add --transport http inngest-dev http://127.0.0.1:8288/mcp
claude mcp add taskade -e TASKADE_API_KEY=<your-api-key> -- npx -y @taskade/mcp-server
claude mcp add cueapi --env CUEAPI_API_KEY=cue_sk_YOUR_KEY -- npx -y @cueapi/mcp
Config
{
  "mcpServers": {
    "trigger": {
      "command": "npx",
      "args": ["trigger.dev@latest", "mcp"]
    }
  }
}
{
  "mcpServers": {
    "inngest-dev": {
      "type": "http",
      "url": "http://127.0.0.1:8288/mcp"
    }
  }
}
{
  "mcpServers": {
    "taskade": {
      "command": "npx",
      "args": ["-y", "@taskade/mcp-server"],
      "env": {
        "TASKADE_API_KEY": "<your-api-key>"
      }
    }
  }
}
{
  "mcpServers": {
    "cueapi": {
      "command": "npx",
      "args": ["-y", "@cueapi/mcp"],
      "env": {
        "CUEAPI_API_KEY": "cue_sk_YOUR_KEY",
        "CUEAPI_BASE_URL": "https://api.cueapi.ai"
      },
      "type": "stdio"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.