Bug Description

The list_deploys MCP tool fails with a Zod validation error when deployments have null values for runtime and/or runtimeVersion fields.

Error

200 Validation error: Expected string, received null at "data[0].runtime"; Expected string, received null at "data[0].runtimeVersion"; Expected string, received null at "data[1].runtime"; Expected string, received null at "data[1].runtimeVersion"

The API returns a 200 with valid data, but the MCP server's Zod schema expects string for these fields and rejects null.

Reproduction

1. Configure MCP server: npx trigger.dev@latest mcp --project-ref <ref>
2. Call list_deploys with any parameters (environment, limit, period — doesn't matter)
3. If any deployment has null for runtime or runtimeVersion, the tool errors

Context

• trigger.dev version: 4.4.1 (latest as of 2026-02-27)
• Environment: prod
• All other MCP tools work fine: list_orgs, list_projects, get_current_worker, list_runs, get_run_details, list_preview_branches, search_docs
• Deployments were created via GitHub integration, which may not populate runtime/runtimeVersion

Expected Fix

The Zod schema for the deploy list response should use .nullable() or .optional() for runtime and runtimeVersion fields, e.g.:

runtime: z.string().nullable()
runtimeVersion: z.string().nullable()