Deutsch English
Integrations

MCP Server

The FireStatus Management API documentation is also available as a Model Context Protocol server named FireStatus API Docs. MCP-capable clients — such as Claude Desktop, Claude Code or Cursor — can search endpoints, inspect parameters and fetch example responses without you having to switch between your IDE and the browser.

Available tools

Name Input Description
search_endpoints query: string · limit?: int Typo-tolerant full-text search across names, paths, descriptions, parameters and enum values.
get_endpoint path: string oder id: int Full documentation of an endpoint including parameters, response examples and enum references.
list_categories include_endpoints?: bool Hierarchical overview of all categories, feature groups and endpoints.
get_enum key: string Returns the permitted values of an enum (e.g. incident.status, component.impact).

Setup

  1. In Claude Desktop, click Customize in the left sidebar.
  2. In the Connectors section, click Add custom connector at the very bottom.
  3. Enter https://docs.firestatus.de/mcp as the URL and confirm with Add.

The server requires no authentication and is ready to use immediately. A tools icon with the four available tools appears in the input field.

Alternative: configuration file with the mcp-remote bridge

For plans without the Connectors feature, the server can also be connected via a STDIO bridge. This requires an installed Node.js environment (npx) on your system.

Under Settings → Developer → Edit Config, open claude_desktop_config.json and add: 

{
  "mcpServers": {
    "firestatus-docs": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://docs.firestatus.de/mcp"
      ]
    }
  }
}
macOS
~/Library/Application Support/Claude/claude_desktop_config.json
Windows
%APPDATA%\Claude\claude_desktop_config.json

Then fully quit and restart Claude Desktop.

In an active Claude Code session:

claude mcp add --transport http firestatus-docs https://docs.firestatus.de/mcp

Check the connection status with the /mcp command.

In Cursor, go to Settings → Tools & Integrations → MCP and click Add new MCP server – the global mcp.json opens. Add the following entry there: 

{
  "mcpServers": {
    "firestatus-docs": {
      "url": "https://docs.firestatus.de/mcp"
    }
  }
}

File path (alternatively edit directly)

macOS/Linux
~/.cursor/mcp.json
Windows
%USERPROFILE%\.cursor\mcp.json

If the server should only be active in a single project, create .cursor/mcp.json in the project root instead.

As soon as the file is saved, the server appears in the MCP list with a green status.

Direct integration with the official @modelcontextprotocol/sdk in TypeScript: 

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport }
  from "@modelcontextprotocol/sdk/client/streamableHttp.js";

const client = new Client({ name: "firestatus-app", version: "1.0.0" });
await client.connect(new StreamableHTTPClientTransport(
  new URL("https://docs.firestatus.de/mcp")
));

const { tools } = await client.listTools();

const result = await client.callTool({
  name: "search_endpoints",
  arguments: { query: "incident veröffentlichen" }
});

SDKs are also available for Python, Java, Kotlin, Go and C#.

Example prompts

„Which endpoints are there for publishing an incident?"
„Show me the parameters for updating a component and which values are allowed for component.impact."
„Generate a TypeScript wrapper for the scheduled maintenance endpoints, including all enum values."
„How do I list the subscribers of my status page, and which fields does the response return?"