Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

FireHydrant (BYOK) — connector documentation

  • MCP endpoint: https://byok-firehydrant.connectorbay.com/mcp
  • REST API: POST https://byok-firehydrant.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-firehydrant.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own FireHydrant FireHydrant bot token (the docs say viewing incidents needs owner permissions), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-firehydrant.connectorbay.com/health · Tool schemas: https://byok-firehydrant.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-firehydrant · agent@connectorbay.com

What FireHydrant (BYOK) is for

FireHydrant (BYOK) lets an AI assistant read your own FireHydrant data through the FireHydrant API with a key you supply (FireHydrant bot token (the docs say viewing incidents needs owner permissions)). Read-only: 11 tools (list_incidents, get_incident, list_services, list_teams, list_environments, list_functionalities, list_severities, list_priorities, list_runbooks, list_alerts, list_on_call_schedules). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.firehydrant.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by FireHydrant. FireHydrant and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "What incidents are active in FireHydrant?"
  • "Show the details of FireHydrant incident 3a1b2c4d-0000-1111-2222-333344445555"
  • "What services are in the FireHydrant catalog?"
  • "What teams exist in FireHydrant?"
  • "Which environments are defined in FireHydrant?"
  • "What functionalities are tracked in FireHydrant?"

What it does

  • list_incidents: List incidents with name, number, summary, current milestone, severity, priority, services, environments, link and times. Filter by search text, severities, milestones or creation time.
  • get_incident: Get one incident by id with name, summary, milestone, severity, priority, services, environments, customer impact summary, link and times.
  • list_services: List services with name, slug, description, tier, labels and active incidents. Search by name or owner.
  • list_teams: List teams with name, slug, description and creation and update times.
  • list_environments: List environments with name, slug, description and active incidents.
  • list_functionalities: List functionalities (customer-facing features) with name, slug, description, labels, tier and active incidents.
  • list_severities: List severity levels with slug, description, color and position.
  • list_priorities: List priority levels with slug, description, position and which is the default.
  • list_runbooks: List runbooks with name, summary, type, categories, last execution time and the incident it last ran for. Search by name; sort by update, name, creation or last run.
  • list_alerts: List alerts with summary, status, priority, source integration, team, times, link and noise flag. Filter by search text, statuses or start time.
  • list_on_call_schedules: List the organization's on-call schedules with team, who is on call now and who is next. Optionally limit to some teams.

BYOK key

You bring your own FireHydrant FireHydrant bot token (the docs say viewing incidents needs owner permissions) (https://docs.firehydrant.com/reference/list_incidents). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.firehydrant.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the FireHydrant API (api.firehydrant.io) with a BYOK key; documentation: https://docs.firehydrant.com/reference/list_incidents. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by FireHydrant. FireHydrant and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your FireHydrant account.

Built for: Worldwide. Languages: English.