FireHydrant MCP server

What the model can do

FireHydrant incident management: incidents with severity, milestone, services, responders and the latest note, one incident in full with its tasks, services and their owners, teams, incident roles, and Signals alerts. Can declare, update, resolve, close and archive incidents, add or edit a private note, add or update a task, assign a role and attach a link.

Reads

• firehydrant_incidentsFireHydrant incidents, with number, name, current milestone, severity, priority, services, responders and the latest note.
• firehydrant_incidentOne FireHydrant incident in full: summary, description, customer impact, AI summary, milestones with times, responders, teams, services…
• firehydrant_servicesServices in the FireHydrant catalogue: tier, owner team, responding teams, how many active incidents, description and links.
• firehydrant_teamsTeams in FireHydrant with the services they own or respond to and their members' names.
• firehydrant_alertsFireHydrant Signals alerts: summary, status, priority, source integration, start and end, team, services and any incidents opened from them.
• firehydrant_incident_rolesIncident roles defined in FireHydrant (Commander, Communications lead and so on), with their ids…

Acts, when you ask

These change something in FireHydrant. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• firehydrant_add_incident_noteAdds a note to a FireHydrant incident's timeline.
• firehydrant_create_incident_taskAdds a task to a FireHydrant incident's task list.
• firehydrant_create_incidentDeclares a new incident in FireHydrant.
• firehydrant_update_incidentChanges a FireHydrant incident's name, summary, description, customer impact, severity, priority or tags.
• firehydrant_resolve_incidentResolves an active FireHydrant incident, optionally setting a post-incident or closed-phase milestone slug configured for it.
• firehydrant_close_incidentCloses a FireHydrant incident (the final milestone, after resolution and any retrospective).
• firehydrant_archive_incidentArchives a FireHydrant incident, which hides it from lists and metrics.
• firehydrant_update_incident_taskChanges a task on a FireHydrant incident: title, description, state (open, in_progress, cancelled, done), assignee or due date.
• firehydrant_update_incident_noteReplaces the text of a note on a FireHydrant incident's timeline.
• firehydrant_assign_incident_roleAssigns an incident role (from firehydrant_incident_roles) to a FireHydrant user on an incident.
• firehydrant_add_incident_linkAttaches a link (a dashboard, ticket or document) to a FireHydrant incident.

Connect it

First connect FireHydrant on Dashboard → Connections, then add Memtro to your client once. The FireHydrant tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared FireHydrant connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › What is happening with the current incident?
• › Which services owned by the payments team have active incidents?
• › Which Signals alerts fired overnight, and did any open an incident?
• › Add a note to the current incident saying the database failover is complete
• › Resolve the checkout incident now the fix is deployed

Questions

Is this an official FireHydrant MCP server?

No. It is Memtro's MCP server with Memtro's FireHydrant connector behind it: the connector reads FireHydrant through its API with the credentials you connect on Dashboard → Connections, and FireHydrant publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in FireHydrant?

Only when you ask, and only what it has been granted: add a note to an incident, private to the organisation; add a task to an incident; declare an incident (your runbook automation may open a channel and page responders); update an incident's name, summary, description, impact, severity, priority or tags; resolve an incident; close an incident; archive an incident (hidden from lists and metrics); update an incident task's title, state, assignee or due date; edit the text of a note on an incident; assign an incident role to a user; attach a link to an incident. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server