Flashduty MCP Server provides a curated, task-oriented toolset; it does not mirror the full Flashduty Open API. For 1:1 coverage of every Open API operation, use the Flashduty CLI; agents with shell access can call the CLI directly.
Use cases
Automate incident workflows
Hand incident creation, acknowledgment, and closure in Flashduty over to AI orchestration, wired into your operations workflow.
Data extraction & analysis
Let an LLM retrieve incidents, alerts, and change records by time range, status, severity, and other criteria, and summarize them.
Build AI ops tools
Call Flashduty capabilities from your own AI apps to build intelligent on-call, incident retrospectives, and more.
Template validation & debugging
Validate rendering and query available variables and functions in real time while editing notification templates.
Deployment
Flashduty MCP Server offers three deployment modes; choose based on your MCP client’s capabilities and your runtime environment.- Remote service (recommended)
- Docker
- Build from source
No local installation needed — connect directly to the official remote instance With an APP Key, add the following to your MCP configuration (Cursor shown as an example):
https://mcp.flashcat.cloud/mcp; this is the fastest way to get started. The remote service accepts two credential types, based on what your client supports:- OAuth sign-in: when your client supports MCP OAuth (such as claude.ai, Claude Desktop, or ChatGPT connectors), add a custom connector with the URL
https://mcp.flashcat.cloud/mcpand no credentials at all. The client discovers the Flashduty authorization server and opens a consent page in your browser. After you authorize, the client calls the Flashduty Open API as you, with the same access as an APP key. - APP Key: when your client does not support OAuth, send your APP Key in the
Authorization: Bearerrequest header instead.
The remote service supports only Streamable HTTP transport (
POST /mcp). Check your MCP client’s documentation for the exact syntax and location of remote MCP service configuration.Authentication and transport
OAuth authorization and discovery
The remote service accepts both MCP OAuth access tokens and APP keys, and both grant the same access. Clients that support MCP OAuth discover the authorization service automatically and open the browser to authorize, so you configure nothing by hand. An access token is valid only at the Flashduty API address that issued it, sobase_url on the remote URL has no effect on OAuth tokens but still applies to APP keys.
Configuration
Flashduty MCP Server supports toolset trimming, read-only mode, output format, and other settings to suit different scenarios. Local deployments are configured through environment variables or command-line flags; the remote service is configured dynamically by appending query parameters to the URL.Environment variables
Docker example:
Command-line flags
When building from source and running the binary directly, you can use the following flags (which take precedence over the env vars of the same name):--app-key: Flashduty APP Key (equivalent toFLASHDUTY_APP_KEY).--toolsets: comma-separated list of enabled toolsets.--read-only: enable read-only mode.--output-format: tool result output format (jsonortoon).--base-url: base URL of the Flashduty API.
Remote service configuration
When using the official remote instance, append query parameters to the URL to configure toolsets, read-only mode, and the Flashduty API address dynamically:Output format (TOON)
The server supports outputting tool results in TOON (Token-Oriented Object Notation) format. For arrays of objects with uniform fields, such as member or incident lists, TOON uses fewer tokens than JSON. Modern LLMs parse it directly. SetFLASHDUTY_OUTPUT_FORMAT=toon (or --output-format toon) to enable it.
Toolsets and tools
The server provides 8 toolsets and 23 tools in total, all enabled by default. The table below summarizes each toolset:Toolset names (
incidents, status_page) are internal program identifiers; keep them in English when configuring.Pagination parameters
List-style query tools use one shared pagination contract:limit is the number of items per page, default 20, max 100; page is a 1-based page number, default 1. When more results remain, the response includes truncated: true and a hint that names the next page to request, such as page:2.
The following tools support limit / page:
The tools in each toolset are as follows:
incidents — incident lifecycle management (8 tools)
incidents — incident lifecycle management (8 tools)
query_incidents parameter referencesince / until time-window behavior- Both omitted: defaults to the last 30 days (convenient for querying current/open incidents).
- Only
sinceprovided: queries from that time through the current moment. - Only
untilprovided: not allowed — returns an error (sinceis required whenuntilis set; omit both to use the 30-day default). - Both provided: queries the specified range; the span is capped at 31 days, and a longer one returns an error.
since and until:- Relative duration:
30d,24h,168h(meaning “this far before now”) - RFC3339 with timezone:
2026-04-01T10:00:00+08:00or2026-04-01T10:00:00Z(SDK-emitted timestamps can be passed back directly as filter bounds) - Date:
2026-04-01(parsed as local midnight) - Datetime:
2026-04-01 10:00:00or2026-04-01T10:00:00(local time) - Unix timestamp:
1712000000
status_page — status page management (4 tools)
status_page — status page management (4 tools)
templates — notification templates (4 tools)
templates — notification templates (4 tools)
users — member and team queries (2 tools)
users — member and team queries (2 tools)
channels — channels and escalation rules (2 tools)
channels — channels and escalation rules (2 tools)
alerts — alert event query (1 tool)
alerts — alert event query (1 tool)
changes — change record query (1 tool)
changes — change record query (1 tool)
fields — custom fields (1 tool)
fields — custom fields (1 tool)
Related resources
go-flashduty SDK
The Go SDK that MCP Server depends on, covering the entire Flashduty Open API.
Flashduty CLI
Command-line tool covering the Flashduty Open API, useful when an agent needs complete API coverage.
GitHub repository
Browse the source, releases, and issue tracker.