MCP server

SIGNL4 MCP by usefulapi

io.usefulapi/signl4

Checked 26 Oct 2026, 08:29 UTC · Connected to it and listed its tools

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

Website Source

At a glance

Type

MCP server

Publisher

usefulapi.io (verified by the MCP Registry)

Status

Working at last check

Tools

18

Token cost

About 3,843 tokens per request

Sets up in

Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok

Last checked

26 Oct 2026, 08:29 UTC

Connect it to your agent

Add to CursorAdd to VS CodeVS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

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

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

[mcp_servers.signl4]
url = "https://signl4.usefulapi.io/mcp"

Gemini CLI

{"mcpServers":{"signl4":{"httpUrl":"https://signl4.usefulapi.io/mcp"}}}

Cursor

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

VS Code

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

Antigravity

agy mcp add signl4 https://signl4.usefulapi.io/mcp

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"signl4","server_url":"https://signl4.usefulapi.io/mcp","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"signl4","server_url":"https://signl4.usefulapi.io/mcp"}

Tools

• signl4_acknowledge_alert ~230 tokens
  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_annotate_alert ~220 tokens
  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_close_alert ~214 tokens
  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_get_alert ~163 tokens
  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_report ~216 tokens
  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_get_alert_timeline ~144 tokens
  The ordered timeline of an alert: creation, notifications, acknowledgements, annotations, escalations and remote actions. GET /v3/signls/{signlId}/timeline.
• signl4_get_duty_status ~197 tokens
  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 ~176 tokens
  Duty assistant info per team: whether it is enabled and the last two (or all) duty periods. GET /v3/duties/summary.
• signl4_get_team ~110 tokens
  One SIGNL4 team: name, description, time zone, member ids. GET /v3/teams/{teamId}.
• signl4_get_user ~118 tokens
  One SIGNL4 user: name, e-mail, contact addresses, time zone and duty status per team. GET /v3/users/{userId}.
• signl4_list_alerts ~484 tokens
  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_list_audit_logs ~332 tokens
  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.
• signl4_list_categories ~138 tokens
  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_duty_schedules ~278 tokens
  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_list_team_users ~162 tokens
  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_teams ~167 tokens
  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_list_users ~106 tokens
  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_raise_alert ~388 tokens
  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 u

Browse

• Email
• SMS and text messages
• Phone calls
• Government and public data

Related MCP servers

• Squadcast MCP by usefulapi
  Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents.
• Shiftbase MCP by usefulapi
  Read Shiftbase rosters, timesheets, absences and availability; schedule shifts and review absences.
• Spike.sh MCP by usefulapi
  Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.
• NodePing MCP by usefulapi
  Read NodePing checks, uptime, results and events; mute checks, manage maintenance and schedules.
• Synchroteam MCP by usefulapi
  Read Synchroteam jobs, customers, sites, equipment and parts; create, schedule and complete jobs.
• Mindbody MCP by usefulapi
  Read Mindbody classes, schedules, clients, staff and sales; book clients and appointments.
• squirrelscan
  Website QA for your coding agent: audit SEO, performance, security, accessibility over MCP.
• Dutyfinch Tariff Lookup
  US import duty and HTS codes from the official USITC schedule, plus Section 301 China status. Free.

Badge for your README

[![AptLynx](https://aptlynx.net/badge/io.usefulapi/signl4.svg)](https://aptlynx.net/servers/io.usefulapi/signl4)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents