The retrospective tools are what make it worth connecting — list-retros-by-incident returns a retrospective's fields and update-retrospective-field writes one back, so a write-up drafted in conversation lands in the record instead of being retyped into it. That write takes unstyled HTML, which is the detail to settle before anything automated goes near it. Every tool takes a single `request` parameter, so what a call can filter, page or set is governed by the FireHydrant API shape rather than by anything the tool signature reveals.
A FireHydrant client covering the incident record and its retrospective: listing and creating incidents, listing alerts including Signals and third-party alerts, and reading and updating retrospective fields.
- list-incidents returns the incidents in the organization, and create-incident opens a new one.
- list-alerts retrieves alerts, including Signals alerts and alerts from third-party sources.
- list-retros-by-incident returns the retrospectives (RCAs) attached to an incident, along with their basic data and their fields.
- update-retrospective-field writes a value into a named retrospective field, with the value supplied as unstyled HTML.
A FireHydrant API key, supplied with --api-key when the server starts.
One command — npx firehydrant-mcp start --api-key ...