Flashduty MCP server

The Flashduty MCP Server enables integration with Flashduty APIs through the Model Context Protocol (MCP), allowing you to automate incident management workflows, extract data, and build AI-powered applications that interact with Flashduty.

Installation Options

Remote Server Setup

The remote Flashduty MCP Server is the easiest way to get started.

Prerequisites

• An MCP host supporting the latest MCP specification and remote servers
• A Flashduty APP key from your account

Configuration with Cursor

{
  "mcpServers": {
    "flashduty": {
      "url": "https://mcp.flashcat.cloud/flashduty",
      "authorization_token": "Bearer <your_flashduty_app_key>"
    }
  }
}

Local Server Setup

Prerequisites

• Docker installed and running
• A Flashduty APP key from your account

Using Docker

Add this configuration to your Cursor MCP settings:

{
  "mcpServers": {
    "flashduty": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "FLASHDUTY_APP_KEY",
        "flashcat.tencentcloudcr.com/flashduty/flashduty-mcp-server"
      ],
      "env": {
        "FLASHDUTY_APP_KEY": "your_flashduty_app_key"
      }
    }
  }
}

Using Binary

You can download pre-compiled binaries from GitHub Releases.

Configure your MCP host to use the executable:

Via Environment Variable:

{
  "mcpServers": {
    "flashduty": {
      "command": "/path/to/flashduty-mcp-server",
      "args": ["stdio"],
      "env": {
        "FLASHDUTY_APP_KEY": "your_app_key_here"
      }
    }
  }
}

Via Command-line Argument:

{
  "mcpServers": {
    "flashduty": {
      "command": "/path/to/flashduty-mcp-server",
      "args": ["stdio", "--app-key", "your_app_key_here"]
    }
  }
}

Configuration Options

Remote Server Configuration

When using the remote service, configure it by adding query parameters to the URL:

{
  "mcpServers": {
    "flashduty": {
      "url": "https://mcp.flashcat.cloud/flashduty?toolsets=flashduty_incidents,flashduty_teams&read_only=true",
      "authorization_token": "Bearer <your_flashduty_app_key>"
    }
  }
}

Local Server Configuration

Via Environment Variables

docker run -i --rm \
  -e FLASHDUTY_APP_KEY=<your-app-key> \
  -e FLASHDUTY_TOOLSETS="flashduty_incidents,flashduty_teams" \
  -e FLASHDUTY_READ_ONLY=1 \
  flashcat.tencentcloudcr.com/flashduty/flashduty-mcp-server

Key environment variables:

• FLASHDUTY_APP_KEY: Flashduty APP key (required)
• FLASHDUTY_TOOLSETS: Toolsets to enable (comma-separated)
• FLASHDUTY_READ_ONLY: Restrict to read-only operations (set to 1 or true)
• FLASHDUTY_BASE_URL: Flashduty API base URL
• FLASHDUTY_LOG_FILE: Log file path
• FLASHDUTY_ENABLE_COMMAND_LOGGING: Enable command logging

Via Command-Line Arguments

./flashduty-mcp-server stdio \
  --app-key your_app_key_here \
  --toolsets flashduty_incidents,flashduty_teams \
  --read-only

Customizing Tool Descriptions (Local-Only)

Create a flashduty-mcp-server-config.json file in the same directory as the binary:

{
  "TOOL_CREATE_INCIDENT_DESCRIPTION": "an alternative description",
  "TOOL_LIST_TEAMS_DESCRIPTION": "List all teams in Flashduty account"
}

Or use environment variables:

export FLASHDUTY_MCP_TOOL_CREATE_INCIDENT_DESCRIPTION="an alternative description"

Available Toolsets

All toolsets are enabled by default, but you can specify which ones to use:

• flashduty_incidents: Incident management tools
• flashduty_members: Member management tools
• flashduty_teams: Team management tools
• flashduty_channels: Channel management tools

Available Tools

Member Management Tools

• flashduty_member_infos: Get member information by person IDs

Team Management Tools

• flashduty_teams_infos: Get team information by team IDs

Channel Management Tools

• flashduty_channels_infos: Get collaboration space information by channel IDs

Incident Management Tools

• flashduty_incidents_infos: Get incident information by incident IDs
• flashduty_list_incidents: List incidents with comprehensive filters
• flashduty_list_past_incidents: List similar historical incidents
• flashduty_get_incident_timeline: Get incident timeline and feed
• flashduty_get_incident_alerts: Get alerts associated with incidents
• flashduty_create_incident: Create a new incident
• flashduty_ack_incident: Acknowledge incidents
• flashduty_resolve_incident: Resolve incidents
• flashduty_assign_incident: Assign incidents to people or escalation rules
• flashduty_add_responder: Add responders to incidents
• flashduty_snooze_incident: Snooze incidents for a period
• flashduty_merge_incident: Merge multiple incidents into one
• flashduty_comment_incident: Add comments to incidents
• flashduty_update_incident_title: Update incident title
• flashduty_update_incident_description: Update incident description
• flashduty_update_incident_impact: Update incident impact
• flashduty_update_incident_root_cause: Update incident root cause
• flashduty_update_incident_resolution: Update incident resolution
• flashduty_update_incident_severity: Update incident severity
• flashduty_update_incident_fields: Update custom fields

How to install this MCP server

For Claude Code

To add this MCP server to Claude Code, run this command in your terminal:

claude mcp add-json "flashduty" '{"url":"https://mcp.flashcat.cloud/flashduty","authorization_token":"Bearer <your_flashduty_app_key>"}'

See the official Claude Code MCP documentation for more details.

For Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "flashduty": {
            "url": "https://mcp.flashcat.cloud/flashduty",
            "authorization_token": "Bearer <your_flashduty_app_key>"
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.

For Claude Desktop

To add this MCP server to Claude Desktop:

1. Find your configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

2. Add this to your configuration file:

{
    "mcpServers": {
        "flashduty": {
            "url": "https://mcp.flashcat.cloud/flashduty",
            "authorization_token": "Bearer <your_flashduty_app_key>"
        }
    }
}

3. Restart Claude Desktop for the changes to take effect