Verified

Firehydrant MCP Server

FireHydrant API interactions, enabling incident management workflows via MCP.

Data last scanned today · Reviewed today

34★ 5TypeScriptMIT

Overview

This MCP server provides a standardized interface for interacting with the FireHydrant incident management platform. By implementing the Model Context Protocol, it allows users to bridge their AI assistant capabilities directly with FireHydrant API functionalities for streamlined operations. Installation is facilitated through various methods, including a drag-and-drop MCP bundle for desktop environments and direct CLI configuration for integration into development environments like Cursor and Claude Code.

Our verdict

This project carries a high risk level with a security score of 34/100. The repository has not been updated for 198 days and lacks official maintenance, as it is community-contributed rather than managed by the FireHydrant vendor. Additionally, critical security aspects including the authentication method and read-only mode status remain unreviewed. Users should proceed with caution and verify the codebase before connecting sensitive incident management credentials.

Built with a lean architecture of only 8 dependencies.
Provides a simple drag-and-drop bundle for desktop installation.
Includes clear installation instructions for multiple AI clients.
Released under the permissive MIT open source license.

Repository has not received updates for 198 days.
Not maintained by the official FireHydrant organization.
Authentication and read-only security controls are currently unverified.

Setup

Claude Desktop

{
  "mcpServers": {
    "firehydrant-mcp": {
      "args": [
        "-y",
        "firehydrant-mcp"
      ],
      "command": "npx"
    }
  }
}

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.

No read-only mode — running this grants full read/write access.
No built-in authentication — anyone with access to this config can invoke every tool it exposes.