Squadcast MCP by usefulapi
Server Details
Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents.
- Status
- Healthy
- Uptime
- 80.2% over 55 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
TDQS
Scored across 16 tools
Each tool targets a clear combination of resource and action: get/list pairs for teams, users, services separate individual-from-collection lookups, and incident tools cover state actions (acknowledge, resolve) vs. informational reads (get, list, events, notes) with no overlap. The only close pairs (get_incident vs list_incidents, add/list_incident_notes) are explicitly distinguished by singular vs plural scope.
All 16 tools follow the identical `squadcast_<verb>_<noun>` pattern, with verbs restricted to `get`, `list`, `add`, `acknowledge`, and `resolve`. The naming is uniform, predictable, and self-documenting—even `get_incident_events` and `list_incident_notes` remain consistent as `get_<composite>` and `list_<composite>`.
At 16 tools, the set is slightly above the typical 3–15 range, but every tool covers a distinct, needed operation for an incident/on-call domain. The count is justified by the breadth of entities (incidents, teams, users, services, escalation policies, schedules, squads); it's a bit heavy but not bloated.
The incident lifecycle is well covered: get/list events/notes, acknowledge, resolve, and add notes. The main gaps are that only get/list pairs exist for teams, users, and services, and no `get` tools for escalation policies, schedules, or squads—only `list`. Missing `create`/`update` for incidents is defensible since incidents are typically externally triggered, but the absent single-item details for three entity types create minor dead ends.
Available Tools
16 toolssquadcast_acknowledge_incidentAcknowledge incidentDestructiveInspect
Acknowledge a triggered incident on the LIVE account (stops escalation/paging for it). Squadcast: POST /v3/incidents/{incidentID}/acknowledge.
| Name | Required | Description | Default |
|---|---|---|---|
| incidentId | Yes | The incident id to acknowledge (required). |
squadcast_add_incident_noteAdd incident noteDestructiveInspect
Add a war-room note to a LIVE incident (optionally with attachment URLs). Squadcast: POST /v3/incidents/{IncidentId}/warroom.
| Name | Required | Description | Default |
|---|---|---|---|
| message | Yes | The note message (required). | |
| incidentId | Yes | The incident id to add a note to (required). | |
| attachments | No | Attachment URLs (defaults to none). |
squadcast_get_incidentGet incidentRead-onlyInspect
Get a single incident by its id. Squadcast: GET /v3/incidents/{incidentID}.
| Name | Required | Description | Default |
|---|---|---|---|
| incidentId | Yes | The incident id (required). |
squadcast_get_incident_eventsGet incident eventsRead-onlyInspect
Get the timeline of events for a single incident (state changes, notifications, actions). Squadcast: GET /v3/incidents/{incidentID}/events.
| Name | Required | Description | Default |
|---|---|---|---|
| incidentId | Yes | The incident id (required). |
squadcast_get_serviceGet serviceRead-onlyInspect
Get a single service by its id. Squadcast: GET /v3/services/{serviceID}.
| Name | Required | Description | Default |
|---|---|---|---|
| serviceId | Yes | The service id (required). |
squadcast_get_teamGet teamRead-onlyInspect
Get a single team by its id. Squadcast: GET /v3/teams/{teamId}.
| Name | Required | Description | Default |
|---|---|---|---|
| teamId | Yes | The team id (required). |
squadcast_get_userGet userRead-onlyInspect
Get a single user by their id. Squadcast: GET /v3/users/{userID}.
| Name | Required | Description | Default |
|---|---|---|---|
| userId | Yes | The user id (required). |
squadcast_list_escalation_policiesList escalation policiesRead-onlyInspect
List escalation policies for a team. owner_id (a TEAM id — use squadcast_list_teams to find it) is REQUIRED. Squadcast: GET /v3/escalation-policies.
| Name | Required | Description | Default |
|---|---|---|---|
| ownerId | Yes | Team id that owns the escalation policies (required) → owner_id. | |
| pageSize | No | Page size → page_size. | |
| pageNumber | No | Page number → page_number. |
squadcast_list_incident_notesList incident notesRead-onlyInspect
List the war-room notes on a single incident. Squadcast: GET /v3/incidents/{IncidentId}/warroom.
| Name | Required | Description | Default |
|---|---|---|---|
| incidentId | Yes | The incident id (required). |
squadcast_list_incidentsList incidentsRead-onlyInspect
Search/list incidents over a time window with filters (status, service, priority, assignee, tags, sources, starred, SLO-affecting) and sorting. start_time, end_time (both ISO8601) and owner_id (a TEAM id — use squadcast_list_teams to find it) are REQUIRED. Squadcast: GET /v3/incidents/export.
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Filter by tag(s) → tags. | |
| sortBy | No | Sort field → sort_by. | |
| status | No | Filter by incident status(es) → status. | |
| endTime | Yes | ISO8601 end of the window (required) → end_time. | |
| ownerId | Yes | Team id that owns the incidents (required) → owner_id. Use squadcast_list_teams to find it. | |
| sources | No | Filter by alert source(s) → sources. | |
| priority | No | Filter by priority (e.g. P1..P5) → priority. | |
| services | No | Filter by service id(s) → services. | |
| isStarred | No | Filter to starred incidents → is_starred. | |
| startTime | Yes | ISO8601 start of the window (required) → start_time. | |
| assignedTo | No | Filter by assignee id(s) → assigned_to. | |
| textFilter | No | Free-text filter → textFilter. | |
| sloAffecting | No | Filter by SLO-affecting → slo_affecting. |
squadcast_list_schedulesList schedules (on-call)Read-onlyInspect
List on-call schedules for a team. teamID is REQUIRED (use squadcast_list_teams to find it). Set myOnCall to filter to schedules where the token's own user is currently on call — the 'who's on call' lens. Squadcast: GET /v4/schedules.
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | No | Pagination cursor → cursor. | |
| search | No | Free-text search → search. | |
| teamId | Yes | Team id whose schedules to list (required) → teamID. | |
| myOnCall | No | Only schedules where the token's user is on call now → myOnCall (the 'who's on call' lens). | |
| pageSize | No | Page size → pageSize. | |
| participants | No | Filter by participant user id(s) → participants. | |
| scheduleName | No | Filter by schedule name → scheduleName. |
squadcast_list_servicesList servicesRead-onlyInspect
List services for a team. owner_id (a TEAM id — use squadcast_list_teams to find it) is REQUIRED. Squadcast: GET /v3/services.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Filter by service name → name. | |
| ownerId | Yes | Team id that owns the services (required) → owner_id. | |
| entityOwner | No | Filter by entity owner → entity_owner. |
squadcast_list_squadsList squadsRead-onlyInspect
List squads for a team. owner_id (a TEAM id — use squadcast_list_teams to find it) is REQUIRED. Squadcast: GET /v4/squads.
| Name | Required | Description | Default |
|---|---|---|---|
| ownerId | Yes | Team id that owns the squads (required) → owner_id. |
squadcast_list_teamsList teamsRead-onlyInspect
List all teams in the organization. A team id is the owner_id/teamID several other tools require. Squadcast: GET /v3/teams.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
squadcast_list_usersList usersRead-onlyInspect
List all users in the organization. Squadcast: GET /v3/users.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
squadcast_resolve_incidentResolve incidentDestructiveInspect
Resolve an incident on the LIVE account, recording a resolution message. Squadcast: POST /v3/incidents/{incidentID}/resolve.
| Name | Required | Description | Default |
|---|---|---|---|
| message | Yes | Resolution reason/message (required). | |
| incidentId | Yes | The incident id to resolve (required). |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
16 tool updates
- Changed
squadcast_acknowledge_incident1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
squadcast_add_incident_note1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
squadcast_get_incident1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
squadcast_get_incident_events1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
squadcast_get_service1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
squadcast_get_team1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
squadcast_get_user1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
squadcast_list_escalation_policies1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
squadcast_list_incident_notes1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
squadcast_list_incidents1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
squadcast_list_schedules1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
squadcast_list_services1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
squadcast_list_squads1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
squadcast_list_teams1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
squadcast_list_users1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
squadcast_resolve_incident1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
16 tool updates
- First observed
squadcast_acknowledge_incident - First observed
squadcast_add_incident_note - First observed
squadcast_get_incident - First observed
squadcast_get_incident_events - First observed
squadcast_get_service - First observed
squadcast_get_team - First observed
squadcast_get_user - First observed
squadcast_list_escalation_policies - First observed
squadcast_list_incident_notes - First observed
squadcast_list_incidents - First observed
squadcast_list_schedules - First observed
squadcast_list_services - First observed
squadcast_list_squads - First observed
squadcast_list_teams - First observed
squadcast_list_users - First observed
squadcast_resolve_incident
Related MCP Connectors
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.
Manage incidents and on-call: list/create/update incidents, who is on call, on-call overrides.
Read status-page status, services, incidents and metrics; create, update and publish incidents.
Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables PagerDuty incident response operations including listing incidents, acknowledging and resolving incidents, looking up on-call schedules, and listing services.MIT

StackWitnessofficial
FlicenseNot gradedqualityCmaintenanceLet agents read and manage your org’s independent monitors, incidents, status pages, and alerts (honest measured state, no false greens).-- 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
- AlicenseAqualityBmaintenanceEnables incident management and on-call operations for the All Quiet platform, allowing MCP clients to triage incidents, check who is on call, and access the full public API through generic tools.10MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.