Best for
- Developers building TypeScript AI workflows with Trigger.dev
- Teams needing long-running tasks, retries, queues, and run observability
- Users who want MCP assistance for Trigger.dev development and troubleshooting
T
Trigger.dev MCP Server
Official
Automate Trigger.dev projects and workflows with MCP
- Category
- Dev Tools #315 of 438
- Stars
- ★ 16.6k Very popular
- Transport
- stdio (local process)
- Runtime
- Node.js
- Credentials
- API key / credential required
- License
- Apache-2.0
- Last commit
44FMRS · D
The material identifies this as an official server maintained in the Trigger.dev repository. It is active, version 4.0.3, distributed as an npm package, and uses stdio transport. The material does not list specific tools, client compatibility, authentication, or detailed permissions.
Strongest · Maintenance 12/20 Weakest · Reliability 7/20
Why each score
- Reliability 7/20
- The manifest specifies a simple-looking startup path: run trigger.dev mcp via npx using stdio, with version 4.0.3 pinned. However, no tool list, initialization or tool-list handshake evidence, tests, CI, or error-handling details are supplied. The declared behavior therefore cannot be verified and dependency or edge-case failures remain unreviewable, so points are deducted.
- Security and permissions 8/20
- No environment variables or real credentials are declared, and the local stdio transport provides no evidence of credential theft or covert exfiltration. However, the server description includes automating projects, writing code, and debugging runs, which may create side effects. The material does not disclose permission scope, confirmation controls, data flows, external network access, or safeguards for dangerous operations. Risks are visible but controls are incomplete, so points are deducted; no red-line evidence is present.
- Maintenance 12/20
- The repository is not archived and provides an Apache-2.0 license, version 4.0.3, an official repository, and an npm distribution path, indicating identifiable ownership and an update channel. The supplied material does not include commit history, release cadence, dependency-update practice, vulnerability-response channel, or governance details, so a high score is not justified.
- Documentation 8/20
- The README covers platform capabilities, task concepts, deployment, environments, self-hosting, support, and many linked documents, with an SDK example. It does not provide MCP-specific client configuration, authentication, tool parameters, permission boundaries, limits, costs, or dedicated troubleshooting. It also does not verify the actual behavior of MCP tools, so points are deducted.
- Setup experience 9/20
- The manifest supplies a fixed npm package, npx runtime hint, mcp argument, and stdio transport, suggesting a potentially short installation path. It does not explain runtime prerequisites, configuration examples for mainstream clients, login or project authentication, platform compatibility, or common failure recovery. The path from a prepared runtime to a working connection is therefore incomplete, so points are deducted.
Static review · not runListed 2026-07-29
Read the FMRS scoring method →Fit and risk
What it can accessUses the networkChanges third-party account data
Not for
- Projects that do not use Trigger.dev
- Users seeking browser, cloud-storage, database, or collaboration capabilities
- Integration assessments that require an explicitly documented tool inventory
Required permissions
- The server's stated functions involve automating Trigger.dev projects, writing code, and debugging runs; the exact permission scope is not specified in the provided material
- Authentication methods and required credentials are not specified in the provided material
Risks and side effects
- The server may be used to modify project code or perform project automation; the actual impact depends on the Trigger.dev project access granted
- Run-related actions may affect task execution; verify the target project and environment before use
- The provided material does not specify authentication, permission isolation, or data-handling details
Setup
Before you start
Runtime：Node.js
Start the npm package through npx over stdio: npx trigger.dev mcp. The manifest specifies package version 4.0.3.
Check that it works
After connecting the server in your MCP client, ask it a question about Trigger.dev or request your project's task list; if the server's tools appear in the client's tool list and return results, the install worked.
Troubleshooting
- Confirm that npx and npm are available
- Confirm use of the trigger.dev package at version 4.0.3 with the mcp argument
- Confirm that the client is configured for stdio transport
- For project operations or run debugging, check the Trigger.dev project context and access permissions
- Authentication and credential setup are not described in the provided material; consult Trigger.dev documentation
Things to try
Once connected, you can ask your AI assistant things like:
- List the tasks in my Trigger.dev project
- Help me debug a failed Trigger.dev run
- Write a new Trigger.dev task in my project
- Answer questions about how Trigger.dev works
Use cases
Automating Trigger.dev project operations
Writing Trigger.dev task code
Assisting with task-run debugging
Answering questions about Trigger.dev
Overview
The official Trigger.dev MCP server automates Trigger.dev projects, helps write code, assists with debugging runs, and answers questions about Trigger.dev. Trigger.dev is an open-source platform for building and deploying fully managed AI agents and workflows with long-running tasks, retries, queues, observability, and elastic scaling.
Similar servers
Context7
80 · B
Upstash's official server providing up-to-date third-party library docs for AI coding assistants
NPM Sentinel MCP Server
79 · B
AI-powered NPM package analysis MCP server
MartinLoop MCP Server
79 · B
An independent control layer that gives AI coding agents budgets, brakes, and receipts
GitHub MCP Server
76 · B
GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
Source revision d5dc4842441a Data synced 2026-10-19 Read the FMRS scoring method