SIGQ Incident Lake MCP

An MCP (Model Context Protocol) server that connects Claude Desktop, Cursor, and other MCP clients to your SIGQ Incident Lake. Ask questions about your incidents in natural language — it queries the SIGQ API directly.

Package: @sigq/incidentlake-mcp-library on NPM Packages

How It Works

The server runs as a local process on your machine and communicates with the SIGQ backend over HTTP using your API token. MCP clients connect to it via stdio transport.

Claude Desktop  ──stdio──►  incidentlake-mcp  ──HTTPS──►  SIGQ API

Prerequisites

• Node.js 20+
• A SIGQ API token (starts with sigq_) — generate one from SIGQ tenant settings

Step 1 — Run the setup wizard

npx @sigq/incidentlake-mcp-library configure

This will:

• Ask for your SIGQ API URL and token
• Test the connection to make sure it works
• Save credentials to ~/.sigq/config.json
• Print the exact config block to paste into your MCP client

Welcome to Incident Lake MCP setup!

? Enter your SIGQ API URL (press Enter for default):
  [https://api.prod.incidentlake.sigq.io/incidentlake/public-api]:
? Enter your API token (starts with sigq_): sigq_xxxx

? Testing connection... ✓ Connected successfully!
✓ Config saved to ~/.sigq/config.json

Default API URL: https://api.prod.incidentlake.sigq.io/incidentlake/public-api

Step 2 — Configure your MCP client

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "incidentlake-mcp": {
      "command": "npx",
      "args": ["@sigq/incidentlake-mcp-library"]
    }
  }
}

Cursor

Add to ~/.cursor/mcp.json or your workspace .cursor/mcp.json:

{
  "mcpServers": {
    "incidentlake-mcp": {
      "command": "npx",
      "args": ["@sigq/incidentlake-mcp-library"]
    }
  }
}

No env block needed — credentials are read from ~/.sigq/config.json set up in Step 1.

Step 3 — Restart your MCP client

Restart Claude Desktop or Cursor. You should see incidentlake-mcp listed with 6 tools available.

Example Prompts

• "List the 5 most recent ongoing incidents"
• "Search for incidents related to database timeout"
• "List incidents filtered by tags client:acme and urgency:high"
• "Show me incident analytics for January 2025"
• "Get the full details of incident <uuid>"
• "Create an incident called 'Auth service degraded'"
• "What SOP steps are completed for incident <uuid>?"
• "Update incident <uuid> summary to include the latest customer impact"
• "Resolve incident <uuid>"
• "Reopen incident <uuid>"
• "Delete incident <uuid>"
• "What categorization tags are on incident <uuid>?"
• "Add tags client:acme and urgency:high to incident <uuid>"
• "Replace all tags on incident <uuid> with region:us-east and team:platform"
• "Remove tag device:legacy from incident <uuid>"
• "List all active tenant members"
• "List all knowledge articles"
• "Search knowledge for runbook checkout failure"
• "Show knowledge tags and their item counts"
• "Get the full knowledge article for <uuid>"
• "Create a knowledge article titled Weekly deploy checklist with plain-text content"
• "Update knowledge item <uuid> title to On-call handoff v2"
• "Delete knowledge item <uuid>"
• "Set tags on knowledge item <uuid> to runbook, operations"

Setup for Local Development

1. Clone and install

git clone https://github.com/sigq-io/incidentlake-mcp-library.git
cd incidentlake-mcp-library
npm install

2. Configure environment

cp .env.example .env
# Edit .env — set SIGQ_API_URL and SIGQ_API_TOKEN

3. Run

npm run dev      # run directly with tsx (no build needed)
npm run build    # compile TypeScript → dist/
npm run start    # run compiled output

4. Configure Claude Desktop (local build)

{
  "mcpServers": {
    "sigq-local": {
      "command": "node",
      "args": ["/path/to/incidentlake-mcp-library/dist/index.js"]
    }
  }
}

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT License - see LICENSE for details.