Flashduty's official MCP Server
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"flashduty": {
"url": "https://mcp.flashcat.cloud/mcp",
"headers": {
"Authorization": "Bearer <your_flashduty_app_key>"
}
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
The Flashduty MCP Server is a Model Context Protocol (MCP) server that provides seamless integration with Flashduty APIs, enabling advanced incident management and automation capabilities for developers and tools.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops
MCP server for using the GitLab API
All-in-One Sandbox for AI Agents that combines Browser, Shell, File, MCP and VSCode Server in a single Docker container.
A Unified MCP Server Management App (MCP Manager).
MCP Server for kubernetes management commands
MCP Security Weekly
Get CVE alerts and security updates for Flashduty Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
English | 中文
The Flashduty MCP Server is a Model Context Protocol (MCP) server that provides seamless integration with Flashduty APIs, enabling advanced incident management and automation capabilities for developers and tools.
| Transport | Supported | Notes |
|---|---|---|
| stdio | ✅ | flashduty-mcp-server stdio. Use this for local hosts (Cursor, Claude Desktop, etc.). |
| Streamable HTTP | ✅ | flashduty-mcp-server http. Endpoints: /mcp (canonical) and /flashduty (legacy alias). Public instance: https://mcp.flashcat.cloud/mcp. |
| Standalone SSE (HTTP/SSE) | ❌ | The legacy SSE transport (separate GET /sse endpoint) is not supported. The server returns 405 Method Not Allowed for GET requests by design. Use Streamable HTTP — it already streams responses over POST per the MCP spec. |
If your MCP host only supports the legacy SSE transport, upgrade the host or use
stdiolocally.
The remote Flashduty MCP Server provides the easiest method for getting up and running with Flashduty integration. If your MCP host does not support remote MCP servers, you can use the local version of the Flashduty MCP Server instead.
For Cursors that support Remote MCP, use the following configuration:
{
"mcpServers": {
"flashduty": {
"url": "https://mcp.flashcat.cloud/mcp",
"headers": {
"Authorization": "Bearer <your_flashduty_app_key>"
}
}
}
}
Note: Refer to your MCP host's documentation for the correct syntax and location for remote MCP server setup.
Add the following JSON block to your Cursor MCP configuration.
{
"mcpServers": {
"flashduty": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"FLASHDUTY_APP_KEY",
"registry.flashcat.cloud/public/flashduty-mcp-server"
],
"env": {
"FLASHDUTY_APP_KEY": "your_flashduty_app_key"
}
}
}
}
Besides building from source, you can also download a pre-compiled version for your operating system directly from the project's GitHub Releases, which is a faster and more convenient option.
If you prefer to build from source, you can use go build to build the binary in the cmd/flashduty-mcp-server directory. You can provide the APP key either via environment variable or command-line argument.
You should configure your MCP host to use the built executable as its command. For example:
Via Environment Variable:
{
"mcpServers": {
"flashduty": {
"command": "/path/to/flashduty-mcp-server",
"args": ["stdio
... [View full README on GitHub](https://github.com/flashcatcloud/flashduty-mcp-server#readme)