Zed Trigger.dev MCP by usefulapi Prompt/find_failed_runs_and_read_their_errors
How to: Zed Trigger.dev MCP by usefulapi find_failed_runs_and_read_their_errors
Add Trigger.dev MCP by usefulapi to Zed
-
01
Open ~/.config/zed/settings.json and merge this in. Keep any servers already there.
{
"context_servers": {
"trigger-dev": {
"url": "https://trigger-dev.usefulapi.io/mcp"
}
}
}-
02
Save the file and restart Zed.
-
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 — Zed will not call it for you.
-
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.
Merge this into your existing settings object — do not replace the file. Zed 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.