# SIGNL4 MCP by usefulapi

> SIGNL4 MCP by usefulapi is an MCP server. Read SIGNL4 alerts, teams, users and duty schedules; raise, acknowledge, close and annotate alerts. It runs as a hosted remote server, so there is nothing to install locally.

- **Kind:** MCP server
- **Website:** https://usefulapi.io/signl4/
- **Repository:** https://github.com/m190/usefulapi-mcp/tree/HEAD/servers/signl4
- **MCP Registry name:** io.usefulapi/signl4
- **Listing updated:** 2026-11-13

## About

Read SIGNL4 alerts, teams, users and duty schedules; raise, acknowledge, close and annotate alerts.

## Install

### Claude Code (Terminal)

```sh
claude mcp add --transport http signl4 https://signl4.usefulapi.io/mcp
```

### Claude Desktop (Settings → Connectors → Add custom connector)

```sh
https://signl4.usefulapi.io/mcp
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "signl4": {
      "url": "https://signl4.usefulapi.io/mcp"
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "signl4": {
      "type": "http",
      "url": "https://signl4.usefulapi.io/mcp"
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "signl4": {
      "serverUrl": "https://signl4.usefulapi.io/mcp"
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "signl4": {
      "type": "http",
      "url": "https://signl4.usefulapi.io/mcp"
    }
  }
}
```

## Tools

- `signl4_list_teams`: List the SIGNL4 teams the API key can access: id, name, description, time zone and member ids. Team ids are needed to raise alerts and to look up categories and duties. GET /v3/teams.
- `signl4_get_team`: One SIGNL4 team: name, description, time zone, member ids. GET /v3/teams/{teamId}.
- `signl4_list_users`: List the SIGNL4 users the key can access with name, e-mail, contact addresses, activation state and duty status per team (dutyMode, onDutyTime). User ids are needed to acknowledge/close/annotate alerts. GET /v3/users.
- `signl4_get_user`: One SIGNL4 user: name, e-mail, contact addresses, time zone and duty status per team. GET /v3/users/{userId}.
- `signl4_list_team_users`: List the users of the given teams (all accessible teams by default) with duty status. Teams that cannot be read are reported under `errors`. GET /v3/teams/users.
- `signl4_list_categories`: List the alert categories of a team (name, color, keywords used to auto-classify alerts). The category name can be passed to signl4_raise_alert. GET /v3/categories/{teamId}.
- `signl4_list_alerts`: Search SIGNL4 alerts (signls), newest first, with status, severity, category and history (created, acknowledged, closed). Filter by team, status, creation time, text or external id. Up to 100 per page; pass the returned continuation_token to get the next page. POST /v3/signls/paged (a read).
- `signl4_get_alert`: Full detail of one alert: title, text, severity, category, status and delivery status, history (who acknowledged/closed it and when), parameters, attachments and escalations with per-user delivery. GET /v3/signls/{signlId}/details.
- `signl4_get_alert_timeline`: The ordered timeline of an alert: creation, notifications, acknowledgements, annotations, escalations and remote actions. GET /v3/signls/{signlId}/timeline.
- `signl4_get_alert_report`: Alert volume and response statistics per team over several time periods: acknowledged, closed and unhandled counts, overall and per category (optionally for one user). Teams that cannot be read are reported under `errors`. GET /v3/signls/report.
- `signl4_raise_alert`: WRITE: raise a new alert in a SIGNL4 team. THIS NOTIFIES REAL PEOPLE: every team member currently on duty is paged (push, SMS and/or voice call according to their settings) and the alert escalates if nobody acknowledges it. Only use it when the user clearly asked to alert the team; never for tests unless they said so. Not idempotent: a second call pages the team again. Returns the new alert incl. 
- `signl4_acknowledge_alert`: WRITE: acknowledge an alert on behalf of a SIGNL4 user (recorded in its history under that user). Stops escalation to further tiers for that alert. POST /v3/signls/{signlId}/acknowledge.
- `signl4_close_alert`: WRITE: close (resolve) an alert on behalf of a SIGNL4 user; it leaves the open list and stops all further notifications. POST /v3/signls/{signlId}/close.
- `signl4_annotate_alert`: WRITE: add a text note to an alert's timeline on behalf of a SIGNL4 user. The note is visible to the team in the app. It does not page anyone by itself. POST /v3/signls/{signlId}/annotate.
- `signl4_list_duty_schedules`: Planned on-call duty schedules (who is on duty when): start/end, team, user, tier, stand-in and shift info. Filter by team, user and time window. POST /v3/schedules (a read).
- `signl4_get_duty_status`: Whether a user is currently on or off duty in each of their teams (dutyMode, onDutyTime, tier). GET /v3/users/{userId}/dutyStatus.
- `signl4_get_duty_summary`: Duty assistant info per team: whether it is enabled and the last two (or all) duty periods. GET /v3/duties/summary.
- `signl4_list_audit_logs`: Audit log of changes and events in the SIGNL4 subscription (who changed what, when). Filter by team, time window and message text; pass the returned continuation_token for the next page. GET /v3/audits.

## FAQ

### How do I add SIGNL4 MCP by usefulapi to Claude Code?

Run this command in your terminal: claude mcp add --transport http signl4 https://signl4.usefulapi.io/mcp

---
Source: https://ai-powered.com/mcp/signl4-mcp-by-usefulapi
