feat(cli,webapp): add a submit_feedback MCP tool

Adds a `submit_feedback` MCP tool. Coding agents hit confusing tool
errors, docs that disagree with actual behaviour, and missing
capabilities, then work around them silently — none of which we ever
see. The tool lets the agent report the problem itself, without the user
having to file it by hand.

`submit_feedback` takes a `message` (what was attempted, what happened,
what was expected) and an optional `toolName` and `projectRef`. The CLI
version is attached automatically. The tool description tells the agent
to describe the problem in its own words rather than pasting raw output,
to leave out secrets, credentials, environment variables and the user's
own data, to tell the user what it reported, and not to file the same
problem twice.

Reports go straight from the CLI to analytics, attributed to the
signed-in user. Reporting is off when `--skip-telemetry` is passed or
`TRIGGER_TELEMETRY_DISABLED` is set, and while it is off the tool is
hidden rather than left to fail.

Mono-RevId: 8ec525a24ad2049ec7bdb0f13c156c12c763e411

Author: isshaddad

.changeset/mcp-submit-feedback.md

@@ -0,0 +1,5 @@
+---
+"trigger.dev": patch
+---
+
+Added a `submit_feedback` MCP tool so coding agents can report a confusing tool error, a docs mismatch, or a missing capability without the user having to file it by hand. Turn it off with `--skip-telemetry` or `TRIGGER_TELEMETRY_DISABLED`; the tool is hidden while it is off.

packages/cli-v3/package.json

@@ -76,6 +76,7 @@
     "mcp:smoke": "tsx src/mcp/smoke.test.ts"
   },
   "dependencies": {
+    "@babel/parser": "^7.29.7",
     "@clack/prompts": "0.11.0",
     "@depot/cli": "0.0.1-cli.2.80.0",
     "@modelcontextprotocol/sdk": "^1.25.2",
@@ -107,7 +108,6 @@
     "ini": "^5.0.0",
     "json-stable-stringify": "^1.3.0",
     "jsonc-parser": "3.2.1",
-    "@babel/parser": "^7.29.7",
     "magicast": "^0.3.4",
     "minimatch": "^10.0.1",
     "mlly": "^1.7.1",
@@ -116,6 +116,7 @@
     "p-limit": "^6.2.0",
     "p-retry": "^6.1.0",
     "pkg-types": "^1.1.3",
+    "posthog-node": "5.35.6",
     "resolve": "^1.22.8",
     "semver": "^7.5.0",
     "signal-exit": "^4.1.0",

packages/cli-v3/src/consts.ts

@@ -1,3 +1,7 @@
 export const COMMAND_NAME = "trigger.dev";
 export const CLOUD_WEB_URL = "https://cloud.trigger.dev";
 export const CLOUD_API_URL = "https://api.trigger.dev";
+
+// Write-only project key, the same one the dashboard already ships to every browser.
+export const POSTHOG_PROJECT_KEY = "phc_LFH7kJiGhdIlnO22hTAKgHpaKhpM8gkzWAFvHmf5vfS";
+export const POSTHOG_INGEST_HOST = "https://eu.i.posthog.com";

packages/cli-v3/src/mcp/config.ts

@@ -16,6 +16,12 @@ export const toolsMetadata = {
     description:
       "Search across the Trigger.dev documentation to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Trigger.dev, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages",
   },
+  submit_feedback: {
+    name: "submit_feedback",
+    title: "Submit Feedback",
+    description:
+      "Report a problem with the Trigger.dev MCP server, SDK, or documentation. Use this when a tool returned a confusing error, the docs disagreed with the actual behaviour, a capability you needed was missing, or you had to work around something to finish the user's task. Describe what you were trying to do, what happened, and what you expected instead, in your own words. Never include secrets, credentials, environment variables, tokens or the user's own data - summarise and redact instead of pasting raw output. Tell the user what you reported. Do not call this more than once for the same problem.",
+  },
   list_projects: {
     name: "list_projects",
     title: "List Projects",

packages/cli-v3/src/mcp/context.ts

@@ -46,6 +46,7 @@ export type McpContextOptions = {
   profile?: string;
   devOnly?: boolean;
   readonly?: boolean;
+  skipTelemetry?: boolean;
 };
 
 export class McpContext {

packages/cli-v3/src/mcp/contextOptions.ts

@@ -22,5 +22,6 @@ export function toMcpContextOptions(
     profile: options.profile,
     readonly: options.readonly,
     devOnly: options.devOnly,
+    skipTelemetry: options.skipTelemetry,
   };
 }

packages/cli-v3/src/mcp/telemetry.ts

@@ -0,0 +1,65 @@
+import { PostHog } from "posthog-node";
+import { env } from "std-env";
+import { POSTHOG_INGEST_HOST, POSTHOG_PROJECT_KEY } from "../consts.js";
+import type { McpContextOptions } from "./context.js";
+
+/**
+ * Analytics for the MCP server, sent straight from the CLI.
+ *
+ * Off when the user says so, by `--skip-telemetry` or TRIGGER_TELEMETRY_DISABLED (the same
+ * variable the webapp honours). Tools that report anywhere are hidden while it is off, rather
+ * than left to fail at call time.
+ */
+export function isTelemetryEnabled(options: McpContextOptions): boolean {
+  if (options.skipTelemetry) {
+    return false;
+  }
+
+  return env.TRIGGER_TELEMETRY_DISABLED === undefined;
+}
+
+export type FeedbackEvent = {
+  userId: string;
+  message: string;
+  toolName?: string;
+  projectRef?: string;
+  cliVersion: string;
+};
+
+/**
+ * Captures a feedback report and waits for it to leave the machine. A stdio MCP server dies
+ * whenever its client closes it, so an unflushed report would be lost while the agent had
+ * already been told it was sent.
+ */
+export async function captureFeedback(event: FeedbackEvent): Promise<void> {
+  // A client per report, shut down straight after. flush() resolves without delivering
+  // anything - only shutdown() drains the queue - and reports are rare enough that the
+  // extra client costs nothing next to reporting success for something never sent.
+  const posthog = new PostHog(POSTHOG_PROJECT_KEY, { host: POSTHOG_INGEST_HOST });
+
+  // shutdown() swallows fetch failures - it logs them and resolves - so without this the tool
+  // would report a delivery that never happened. The error event is the only signal.
+  let deliveryError: Error | undefined;
+  posthog.on("error", (error: unknown) => {
+    deliveryError ??= error instanceof Error ? error : new Error(String(error));
+  });
+
+  posthog.capture({
+    distinctId: event.userId,
+    event: "mcp_feedback_submitted",
+    properties: {
+      message: event.message,
+      toolName: event.toolName,
+      projectRef: event.projectRef,
+      cliVersion: event.cliVersion,
+      source: "mcp",
+    },
+    groups: event.projectRef ? { project: event.projectRef } : undefined,
+  });
+
+  await posthog.shutdown();
+
+  if (deliveryError) {
+    throw deliveryError;
+  }
+}

packages/cli-v3/src/mcp/tools.ts

@@ -1,6 +1,7 @@
 import type { McpContext } from "./context.js";
 import { deployTool, listDeploysTool } from "./tools/deploys.js";
 import { searchDocsTool } from "./tools/docs.js";
+import { submitFeedbackTool } from "./tools/feedback.js";
 import {
   createProjectInOrgTool,
   initializeProjectTool,
@@ -34,6 +35,7 @@ import { listAgentsTool } from "./tools/agents.js";
 import { startAgentChatTool, sendAgentMessageTool, closeAgentChatTool } from "./tools/agentChat.js";
 import { readSessionChannelTool, writeSessionChannelTool } from "./tools/sessionChannels.js";
 import { respondWithError } from "./utils.js";
+import { isTelemetryEnabled } from "./telemetry.js";
 
 /** Tool names that perform write/mutating operations. */
 const WRITE_TOOLS = new Set([
@@ -51,11 +53,13 @@ const WRITE_TOOLS = new Set([
   sendAgentMessageTool.name,
   closeAgentChatTool.name,
   writeSessionChannelTool.name,
+  submitFeedbackTool.name,
 ]);
 
 export function registerTools(context: McpContext) {
   const tools = [
     searchDocsTool,
+    submitFeedbackTool,
     listOrgsTool,
     listProjectsTool,
     createProjectInOrgTool,
@@ -103,6 +107,11 @@ export function registerTools(context: McpContext) {
       continue;
     }
 
+    // Nothing to report to, so don't show the model a tool that can only fail.
+    if (tool.name === submitFeedbackTool.name && !isTelemetryEnabled(context.options)) {
+      continue;
+    }
+
     const isWrite = WRITE_TOOLS.has(tool.name);
 
     context.server.registerTool(

packages/cli-v3/src/mcp/tools/feedback.ts

@@ -0,0 +1,74 @@
+import { z } from "zod";
+import { toolsMetadata } from "../config.js";
+import { respondWithError, toolHandler } from "../utils.js";
+import { captureFeedback } from "../telemetry.js";
+import { VERSION } from "../../version.js";
+
+const MAX_MESSAGE_LENGTH = 4000;
+const MAX_TOOL_NAME_LENGTH = 100;
+// Bounded because it is sent as an analytics group key, where junk values persist.
+const MAX_PROJECT_REF_LENGTH = 100;
+
+const SubmitFeedbackInput = {
+  message: z
+    .string()
+    .min(1)
+    .max(MAX_MESSAGE_LENGTH)
+    .describe(
+      "What you were trying to do, what actually happened, and what you expected instead, in your own words. Summarise the failing call and error rather than pasting raw output, and leave out secrets, credentials, environment variables and the user's own data."
+    ),
+  toolName: z
+    .string()
+    .max(MAX_TOOL_NAME_LENGTH)
+    .optional()
+    .describe("The MCP tool the problem happened in, if it was one tool in particular."),
+  projectRef: z
+    .string()
+    .max(MAX_PROJECT_REF_LENGTH)
+    .startsWith("proj_")
+    .optional()
+    .describe(
+      "The trigger.dev project ref, starts with proj_. Optional: a report without one is still useful."
+    ),
+};
+
+export const submitFeedbackTool = {
+  name: toolsMetadata.submit_feedback.name,
+  title: toolsMetadata.submit_feedback.title,
+  description: toolsMetadata.submit_feedback.description,
+  inputSchema: SubmitFeedbackInput,
+  handler: toolHandler(SubmitFeedbackInput, async (input, { ctx }) => {
+    ctx.logger?.log("calling submit_feedback", {
+      toolName: input.toolName,
+      messageLength: input.message.length,
+    });
+
+    const auth = await ctx.getAuth();
+
+    try {
+      await captureFeedback({
+        userId: auth.userId,
+        message: input.message,
+        toolName: input.toolName,
+        projectRef: input.projectRef,
+        cliVersion: VERSION,
+      });
+    } catch (error) {
+      // Only this tool is affected - nothing else here reports anywhere.
+      return respondWithError(
+        `Your feedback was not recorded - ${
+          error instanceof Error ? error.message : String(error)
+        }. Tell the user the report could not be filed; every other tool still works.`
+      );
+    }
+
+    return {
+      content: [
+        {
+          type: "text" as const,
+          text: "Thanks — your feedback was sent to the Trigger.dev team. Tell the user you reported it, and carry on with the task.",
+        },
+      ],
+    };
+  }),
+};