Trigger.dev MCP server being expanded with TRQL analytics and read-only mode
AI assistants connected to the Trigger.dev MCP server are getting a major capability boost, gaining the ability to query analytics, switch profiles, and control the local dev server—all safely behind a new read-only mode.
Trigger.dev is significantly expanding its Model Context Protocol (MCP) capabilities. AI assistants can now query execution data using TRQL, manage CLI profiles, and control the local dev server directly. A new --readonly mode ensures AIs can safely analyze data without inadvertently deploying code or triggering tasks.
This turns an AI assistant into a fully-fledged, read-safe analytics and operations companion. Developers can simply ask their AI "How many runs failed in the last 7 days?" or "Start the dev server" without leaving their editor or worrying about accidental mutations.
These updates are being documented across the MCP server guides and OpenAPI specifications, reflecting the new underlying API capabilities being introduced to the platform.
View Original GitHub DescriptionFact Check
Depends on #3224