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
GitHub source repository ↗
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.
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.
Tools
The tool list has not been reviewed yet.
Setup
Start the npm package through npx over stdio: npx trigger.dev mcp. The manifest specifies package version 4.0.3.
Fit and risk
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
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
Use cases
Automating Trigger.dev project operations
Writing Trigger.dev task code
Assisting with task-run debugging
Answering questions about Trigger.dev
Supported clients
Supported clients have not been confirmed yet.