SIGNL4 MCP by usefulapi
Server Details
Read SIGNL4 alerts, teams, users and duty schedules; raise, acknowledge, close and annotate alerts.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP ยท MCP 2025-06-18
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
TDQS
Score is being calculated.
Available Tools
18 toolssignl4_acknowledge_alertAcknowledge alertDestructiveIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| comment | No | Optional comment stored with the acknowledgement. | |
| user_id | Yes | The SIGNL4 user the acknowledgement is recorded for; see signl4_list_users. | |
| alert_id | Yes | Alert (signl) id; get it from signl4_list_alerts or the id returned by signl4_raise_alert. |
signl4_annotate_alertAnnotate alertDestructiveInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | The note. | |
| user_id | Yes | The SIGNL4 user the note is recorded for; see signl4_list_users. | |
| alert_id | Yes | Alert (signl) id; get it from signl4_list_alerts or the id returned by signl4_raise_alert. |
signl4_close_alertClose alertDestructiveIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| comment | No | Optional comment stored with the closure. | |
| user_id | Yes | The SIGNL4 user the closure is recorded for; see signl4_list_users. | |
| alert_id | Yes | Alert (signl) id; get it from signl4_list_alerts or the id returned by signl4_raise_alert. |
signl4_get_alertGet alertRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| alert_id | Yes | Alert (signl) id; get it from signl4_list_alerts or the id returned by signl4_raise_alert. |
signl4_get_alert_reportGet alert reportRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| user_id | No | Report for this user only. | |
| team_ids | No | Limit to these team ids (default: all teams the key can access). |
signl4_get_alert_timelineGet alert timelineRead-onlyInspect
The ordered timeline of an alert: creation, notifications, acknowledgements, annotations, escalations and remote actions. GET /v3/signls/{signlId}/timeline.
| Name | Required | Description | Default |
|---|---|---|---|
| alert_id | Yes | Alert (signl) id; get it from signl4_list_alerts or the id returned by signl4_raise_alert. |
signl4_get_duty_statusGet user duty statusRead-onlyInspect
Whether a user is currently on or off duty in each of their teams (dutyMode, onDutyTime, tier). GET /v3/users/{userId}/dutyStatus.
| Name | Required | Description | Default |
|---|---|---|---|
| user_id | Yes | SIGNL4 user id (a GUID); get it from signl4_list_users. | |
| team_ids | No | Limit to these team ids (default: all teams the key can access). |
signl4_get_duty_summaryGet duty summaryRead-onlyInspect
Duty assistant info per team: whether it is enabled and the last two (or all) duty periods. GET /v3/duties/summary.
| Name | Required | Description | Default |
|---|---|---|---|
| team_ids | No | Limit to these team ids (default: all teams the key can access). | |
| last_two_only | No | Only the last two duties (default true). |
signl4_get_teamGet teamRead-onlyInspect
One SIGNL4 team: name, description, time zone, member ids. GET /v3/teams/{teamId}.
| Name | Required | Description | Default |
|---|---|---|---|
| team_id | Yes | SIGNL4 team id (a GUID); get it from signl4_list_teams. |
signl4_get_userGet userRead-onlyInspect
One SIGNL4 user: name, e-mail, contact addresses, time zone and duty status per team. GET /v3/users/{userId}.
| Name | Required | Description | Default |
|---|---|---|---|
| user_id | Yes | SIGNL4 user id (a GUID); get it from signl4_list_users. |
signl4_list_alertsList alertsRead-onlyInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| text | No | Free-text search in title and text. | |
| status | No | Only alerts in this state (default: all). | |
| team_ids | No | Limit to these team ids (default: all teams the key can access). | |
| external_id | No | Only alerts raised with this external id. | |
| max_results | No | Alerts per page, 1-100 (default 25). | |
| category_ids | No | Only alerts of these category ids (see signl4_list_categories). | |
| created_after | No | ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. | |
| created_before | No | ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. | |
| continuation_token | No | The continuation_token of the previous page. |
signl4_list_audit_logsList audit logsRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. | |
| from | No | ISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z. | |
| team_ids | No | Limit to these team ids (default: all teams the key can access). | |
| max_results | No | Entries per page, 1-200 (default 50). | |
| message_contains | No | Only entries whose message contains this text. | |
| continuation_token | No | The continuation_token of the previous page. |
signl4_list_categoriesList alert categoriesRead-onlyInspect
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}.
| Name | Required | Description | Default |
|---|---|---|---|
| team_id | Yes | SIGNL4 team id (a GUID); get it from signl4_list_teams. |
signl4_list_duty_schedulesList duty schedulesRead-onlyInspect
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).
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | End of the window, ISO 8601 with timezone. | |
| from | No | Start of the window, ISO 8601 with timezone. | |
| limit | No | Maximum schedules to return, 1-500 (default 100). | |
| user_id | No | Only this user's duties. | |
| team_ids | No | Limit to these team ids (default: all teams the key can access). |
signl4_list_teamsList teamsRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| team_ids | No | Limit to these team ids (default: all teams the key can access). |
signl4_list_team_usersList users of teamsRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| team_ids | No | Limit to these team ids (default: all teams the key can access). |
signl4_list_usersList usersRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
signl4_raise_alertRaise alertDestructiveInspect
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. its id. POST /v3/signls.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | Alert message body. | |
| title | Yes | Alert title, shown on the pager screen. | |
| team_id | Yes | SIGNL4 team id (a GUID); get it from signl4_list_teams. | |
| category | No | Category name, see signl4_list_categories (default: automatic). | |
| severity | No | Severity (default: SIGNL4's default for the team). | |
| external_id | No | Your own reference for this alert, for later look-up (and for SIGNL4 to group follow-ups). |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
18 tool updates
- First observed
signl4_acknowledge_alert - First observed
signl4_annotate_alert - First observed
signl4_close_alert - First observed
signl4_get_alert - First observed
signl4_get_alert_report - First observed
signl4_get_alert_timeline - First observed
signl4_get_duty_status - First observed
signl4_get_duty_summary - First observed
signl4_get_team - First observed
signl4_get_user - First observed
signl4_list_alerts - First observed
signl4_list_audit_logs - First observed
signl4_list_categories - First observed
signl4_list_duty_schedules - First observed
signl4_list_team_users - First observed
signl4_list_teams - First observed
signl4_list_users - First observed
signl4_raise_alert
Related MCP Connectors
Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents.
Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.
Manage incidents and on-call: list/create/update incidents, who is on call, on-call overrides.
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.
Related MCP Servers
- AlicenseAqualityAmaintenanceEnables interaction with Jira Service Management Operations alerts and on-call schedules, including searching alerts, reading notes and activity logs, acknowledging, closing, annotating, adding responders, and querying current and next on-call rotations.2880 npm4Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables PagerDuty incident response operations including listing incidents, acknowledging and resolving incidents, looking up on-call schedules, and listing services.MIT
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive Opsgenie alert management including listing, creating, acknowledging, and closing alerts, as well as managing alert notes, logs, and custom properties through natural language.276 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with Prometheus Alertmanager for querying alerts, managing silences, and investigating incidents. Supports direct API connection and Kubernetes auto-discovery.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.