Skip to content
mcp/harbor

Gemini CLI Trigger.dev MCP by usefulapi Prompt/find_failed_runs_and_read_their_errors

How to: Gemini CLI Trigger.dev MCP by usefulapi find_failed_runs_and_read_their_errors

client:Gemini CLI transport:streamable-http prompt:find_failed_runs_and_read_their_errors

Add Trigger.dev MCP by usefulapi to Gemini CLI

  1. 01

    Open ~/.gemini/settings.json and merge this in. Keep any servers already there. 

{
  "mcpServers": {
    "trigger-dev": {
      "httpUrl": "https://trigger-dev.usefulapi.io/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

    find_failed_runs_and_read_their_errors is surfaced in the client's prompt or command menu. Unlike a tool, you invoke it deliberately — Gemini CLI will not call it for you.

  3. 04

    If it does not appear, check that Trigger.dev MCP by usefulapi is connected and that you are looking at its prompts rather than its tools.

Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs

Same prompt, other clients

Read from the server itself, by connecting to it and calling prompts/list on 14 November 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.

Trigger.dev MCP by usefulapi MCP server