TTrigger.dev MCP (official)

Tested npm trigger.dev 4.8.3 (Trigger.dev CLI), started as `trigger mcp` (the docs use `npx trigger.dev@latest mcp`; repo triggerdotdev/trigger.dev). Its 55 tools listed without credentials. Real tool calls (no LLM, no credentials): search_docs returned Trigger.dev docs on schedules and list_profiles reported no profiles. whoami tried to start a sign-in and timed out after 60 s; every project, run, deploy and dashboard tool needs a Trigger.dev login and was not called.
Tool-call test (2026-11-03, direct MCP stdio client, no LLM): pass. 2 of 3 calls passed: search_docs and list_profiles. whoami needs a login and timed out. No account; project and run tools not tested. Evidence: local test run, Nov 3, 2026.

Transport (tested 2026-11-03): stdio

Tested version: 4.8.3 · tested 2026-11-03

Score 90/100 · Tools 55 · Token cost approx. 17,869 tokens · Compare · Last tested 2026-11-03 · Version tested 4.8.3 · Package trigger.dev · Repo triggerdotdev/trigger.dev

Summary: Trigger.dev MCP (official) completed an MCP handshake without credentials and exposed 55 tools.

Evidence summary

Handshake

pass

Tools listed

55

Context cost

approx. 17869 tokens, cl100k estimate (55 tools, measured 2026-11-11, version 4.8.3; an estimate) ranking · add up your servers' context cost

API key

No key needed for the tools we called

Tested

2026-11-03

Test results

Local-model readiness

Token cost (estimate): approx. 17869 tokens, cl100k estimate for 55 tools · about 218% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): unknown.

What we tested and what we didn't

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

{
  "name": "trigger.dev",
  "version": "4.8.3",
  "registry": "npm",
  "status": "working",
  "tested": "2026-11-03",
  "tools_count": 55,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "`npm install trigger.dev` (Node 20, Linux) succeeded in 7s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 55 tools listed in 11.7s."
    ],
    "maintenance": [
      "pass",
      25,
      "Repo pushed 2 days before test; 16,700 GitHub stars."
    ],
    "docs": [
      "partial",
      5,
      "README over 3,000 chars. Check of the package's own README (README shipped in npm package)."
    ],
    "license": [
      "pass",
      10,
      "MIT (OSI-approved)."
    ]
  }
}

Install

npx -y trigger.dev mcpCopy

Pin the version we tested

npx -y trigger.dev@4.8.3 mcpCopy

tested 2026-11-03. Newer versions may differ and were not tested by us.

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

Tools listed

cancel_run, close_agent_chat, create_alert, create_dashboard, create_project_in_org, create_prompt_override, deploy, dev_server_status, generate_webhook_secret, get_current_worker, get_prompt_versions, get_query_schema, get_report, get_run_details, get_span_details, get_task_schema, get_webhook_delivery, get_webhook_endpoint_details, initialize_project, list_agents, list_alert_capabilities, list_alerts, list_dashboards, list_deploys, list_orgs, list_preview_branches, list_profiles, list_projects, list_prompts, list_runs, list_webhook_deliveries, list_webhook_endpoints, promote_prompt_version, query, reactivate_prompt_override, read_session_channel, remove_prompt_override, replay_run, replay_webhook_delivery, resolve_alert

Tool history: captured Nov 11, 2026. All tool history.

Quick config

{
  "mcpServers": {
    "trigger-dev-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "trigger.dev",
        "mcp"
      ]
    }
  }
}

Add to config Opens the config generator with this server selected.

{
  "mcpServers": {
    "trigger-dev-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "trigger.dev",
        "mcp"
      ]
    }
  }
}

Related: Best DevOps MCP servers

FAQ

Is Trigger.dev MCP deprecated?

No. trigger.dev was not deprecated or archived when we last tested it on 2026-11-03.

What replaces Trigger.dev MCP?

Nothing; Trigger.dev MCP (official) is not deprecated as of 2026-11-03.

Does Trigger.dev MCP need an API key?

No key for docs search: search_docs and list_profiles worked without one. Its project, run and deploy tools need a Trigger.dev login, which we did not test. It completed an MCP handshake with no credentials and listed 55 tools.

Embed the badge

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Copy HTML

Copy Markdown Claim this listing · Report an issue