flashduty

The Flashduty MCP Server provides a remote MCP service integration for Flashduty APIs, enabling automated incident management, data extraction, and AI-assisted tooling. It supports configuring toolsets to enable specific groups of capabilities (such as incidents, users, channels), running in read-only mode for safer integrations, and choosing output formats (JSON or TOON) to optimize token usage with language models. You can deploy the server locally (via Docker or binary) or use a remote MCP host that supports remote MCP servers. Once configured in your MCP host, you can query and orchestrate Flashduty workflows through the MCP interface, leveraging the available toolsets to automate tasks like incident creation, user lookups, and channel interactions. The tool configuration supports both remote service configuration (via URL parameters) and local service configuration (via environment variables or command-line arguments).

Prerequisites:

• Docker installed and running (for the Docker-based deployment) or a Go toolchain if building from source.
• A Flashduty APP key for authentication.

Option A - Run via Docker (recommended for quick start):

1. Install Docker from https://www.docker.com/
2. Prepare your key: replace <your_flashduty_app_key> with your actual key.
3. Run the MCP server using the example configuration:

docker run -i --rm \
  -e FLASHDUTY_APP_KEY=<your_flashduty_app_key> \
  -e FLASHDUTY_TOOLSETS="incidents,users,channels" \
  -e FLASHDUTY_READ_ONLY=1 \
  -e TZ=Asia/Shanghai \
  registry.flashcat.cloud/public/flashduty-mcp-server

Option B - Run via binary (build from source):

1. Ensure Go is installed: https://go.dev/doc/install
2. Build the binary (from repo root):

go build ./cmd/flashduty-mcp-server

3. Run the binary with environment variables or CLI arguments, e.g.:

./flashduty-mcp-server stdio \
  --app-key <your_flashduty_app_key> \
  --toolsets incidents,users,channels \
  --read-only

Option C - Remote MCP host configuration (Cursor or other host):

1. In your MCP host, add a remote server entry pointing to the Docker-based image or a local executable as described above. 2. Provide the Flashduty APP key via environment variable or command-line option as shown in the examples.

Notes and tips:

• Ensure the FLASHDUTY_APP_KEY is kept secret and never exposed in public configs.
• When using Docker, you can set TZ to control log timestamps (e.g., TZ=Asia/Shanghai).
• The toolsets (incidents, users, channels, etc.) can be customized; if both environment variable and CLI flag are provided, the CLI flag takes precedence.
• Output format can be toggled between json (default) and toon for token-efficient responses.
• If running locally, you can use the exported server as a standalone MCP endpoint by configuring the host to point to the binary or Docker container.
• If you encounter connectivity issues, verify the MCP host's URL, headers, and that the APP key has the required permissions for the requested toolsets.