Skip to main content
Glama

SIGNL4 MCP by usefulapi

Server Details

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

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
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 tools
signl4_acknowledge_alertAcknowledge alert
DestructiveIdempotent
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
commentNoOptional comment stored with the acknowledgement.
user_idYesThe SIGNL4 user the acknowledgement is recorded for; see signl4_list_users.
alert_idYesAlert (signl) id; get it from signl4_list_alerts or the id returned by signl4_raise_alert.
signl4_annotate_alertAnnotate alert
Destructive
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
textYesThe note.
user_idYesThe SIGNL4 user the note is recorded for; see signl4_list_users.
alert_idYesAlert (signl) id; get it from signl4_list_alerts or the id returned by signl4_raise_alert.
signl4_close_alertClose alert
DestructiveIdempotent
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
commentNoOptional comment stored with the closure.
user_idYesThe SIGNL4 user the closure is recorded for; see signl4_list_users.
alert_idYesAlert (signl) id; get it from signl4_list_alerts or the id returned by signl4_raise_alert.
signl4_get_alertGet alert
Read-only
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
alert_idYesAlert (signl) id; get it from signl4_list_alerts or the id returned by signl4_raise_alert.
signl4_get_alert_reportGet alert report
Read-only
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
user_idNoReport for this user only.
team_idsNoLimit to these team ids (default: all teams the key can access).
signl4_get_alert_timelineGet alert timeline
Read-only
Inspect

The ordered timeline of an alert: creation, notifications, acknowledgements, annotations, escalations and remote actions. GET /v3/signls/{signlId}/timeline.

ParametersJSON Schema
NameRequiredDescriptionDefault
alert_idYesAlert (signl) id; get it from signl4_list_alerts or the id returned by signl4_raise_alert.
signl4_get_duty_statusGet user duty status
Read-only
Inspect

Whether a user is currently on or off duty in each of their teams (dutyMode, onDutyTime, tier). GET /v3/users/{userId}/dutyStatus.

ParametersJSON Schema
NameRequiredDescriptionDefault
user_idYesSIGNL4 user id (a GUID); get it from signl4_list_users.
team_idsNoLimit to these team ids (default: all teams the key can access).
signl4_get_duty_summaryGet duty summary
Read-only
Inspect

Duty assistant info per team: whether it is enabled and the last two (or all) duty periods. GET /v3/duties/summary.

ParametersJSON Schema
NameRequiredDescriptionDefault
team_idsNoLimit to these team ids (default: all teams the key can access).
last_two_onlyNoOnly the last two duties (default true).
signl4_get_teamGet team
Read-only
Inspect

One SIGNL4 team: name, description, time zone, member ids. GET /v3/teams/{teamId}.

ParametersJSON Schema
NameRequiredDescriptionDefault
team_idYesSIGNL4 team id (a GUID); get it from signl4_list_teams.
signl4_get_userGet user
Read-only
Inspect

One SIGNL4 user: name, e-mail, contact addresses, time zone and duty status per team. GET /v3/users/{userId}.

ParametersJSON Schema
NameRequiredDescriptionDefault
user_idYesSIGNL4 user id (a GUID); get it from signl4_list_users.
signl4_list_alertsList alerts
Read-only
Inspect

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).

ParametersJSON Schema
NameRequiredDescriptionDefault
textNoFree-text search in title and text.
statusNoOnly alerts in this state (default: all).
team_idsNoLimit to these team ids (default: all teams the key can access).
external_idNoOnly alerts raised with this external id.
max_resultsNoAlerts per page, 1-100 (default 25).
category_idsNoOnly alerts of these category ids (see signl4_list_categories).
created_afterNoISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z.
created_beforeNoISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z.
continuation_tokenNoThe continuation_token of the previous page.
signl4_list_audit_logsList audit logs
Read-only
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
toNoISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z.
fromNoISO 8601 date-time with a timezone, e.g. 2026-10-01T00:00:00Z.
team_idsNoLimit to these team ids (default: all teams the key can access).
max_resultsNoEntries per page, 1-200 (default 50).
message_containsNoOnly entries whose message contains this text.
continuation_tokenNoThe continuation_token of the previous page.
signl4_list_categoriesList alert categories
Read-only
Inspect

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}.

ParametersJSON Schema
NameRequiredDescriptionDefault
team_idYesSIGNL4 team id (a GUID); get it from signl4_list_teams.
signl4_list_duty_schedulesList duty schedules
Read-only
Inspect

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).

ParametersJSON Schema
NameRequiredDescriptionDefault
toNoEnd of the window, ISO 8601 with timezone.
fromNoStart of the window, ISO 8601 with timezone.
limitNoMaximum schedules to return, 1-500 (default 100).
user_idNoOnly this user's duties.
team_idsNoLimit to these team ids (default: all teams the key can access).
signl4_list_teamsList teams
Read-only
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
team_idsNoLimit to these team ids (default: all teams the key can access).
signl4_list_team_usersList users of teams
Read-only
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
team_idsNoLimit to these team ids (default: all teams the key can access).
signl4_list_usersList users
Read-only
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

signl4_raise_alertRaise alert
Destructive
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
textYesAlert message body.
titleYesAlert title, shown on the pager screen.
team_idYesSIGNL4 team id (a GUID); get it from signl4_list_teams.
categoryNoCategory name, see signl4_list_categories (default: automatic).
severityNoSeverity (default: SIGNL4's default for the team).
external_idNoYour 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.

  1. 18 tool updates
    • First observedsignl4_acknowledge_alert
    • First observedsignl4_annotate_alert
    • First observedsignl4_close_alert
    • First observedsignl4_get_alert
    • First observedsignl4_get_alert_report
    • First observedsignl4_get_alert_timeline
    • First observedsignl4_get_duty_status
    • First observedsignl4_get_duty_summary
    • First observedsignl4_get_team
    • First observedsignl4_get_user
    • First observedsignl4_list_alerts
    • First observedsignl4_list_audit_logs
    • First observedsignl4_list_categories
    • First observedsignl4_list_duty_schedules
    • First observedsignl4_list_team_users
    • First observedsignl4_list_teams
    • First observedsignl4_list_users
    • First observedsignl4_raise_alert

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    A
    maintenance
    Enables 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.
    28
    80 npm
    4
    Apache 2.0
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables PagerDuty incident response operations including listing incidents, acknowledging and resolving incidents, looking up on-call schedules, and listing services.
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables 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 npm
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables interaction with Prometheus Alertmanager for querying alerts, managing silences, and investigating incidents. Supports direct API connection and Kubernetes auto-discovery.
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.