mcp-oncall-retainer
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
mcp-oncall-retainer
MCP server for the Agent Incident On-Call Retainer - the staffed escalation layer. When an SLA-breaching event fires, a named responder owns triage, mitigation, and post-mortem. Distinct from the SLA contract service: this is the people.
Pricing in the V3 catalogue: $49-199/mo base; $199-500/mo guaranteed-response tiers; desks indicated willingness above $400 when bundled with SLA terms. The "can a small operator truly staff 24/7?" objection is answered with published staffing transparency, follow-the-sun coverage and credits.
Tools
get_oncall_status
Resolve who is on call at a given moment from the follow-the-sun rotation schedule.
Parameter | Type | Default | Description |
| string enum |
| On-call team to query |
| string | now | ISO-8601 timestamp to resolve on-call for |
Returns the active responder, shift window, minutes into/remaining in shift, the handoff partner and its handoff time, the next rotation, the team's escalation ladder, and staffing-transparency metrics (rotations per day, distinct responders, follow-the-sun coverage hours, whether coverage is 24x7, single-operator risk).
create_incident
Raise an incident and persist it.
Parameter | Type | Default | Description |
| string | required | Incident title |
| string enum |
| Severity |
| string |
| Affected service or agent |
| string | - | What happened |
| string enum |
| Owning on-call team |
| string | now | ISO-8601 raise time |
| string | - | Optional acknowledgement time |
| string | - | Optional mitigation time |
| string | - | Optional resolution time |
| string enum |
| Initial status |
The responder is resolved from the rotation at the raise time. Acknowledge and mitigate deadlines
are derived from the severity multipliers and the team's response tier; the response tier's
mitigation window doubles as the SLA recovery window, and any breach is linked to the Agent
Failure-Recovery SLA service for credit computation. Timestamps that precede raised_at are
rejected with status: "error".
get_incident_history
Incident history, newest first.
Parameter | Type | Default | Description |
| string enum | - | Filter by team |
| string enum | - | Filter by severity |
| string | - | Filter by affected service |
| string enum | - | Filter by status |
| string | - | Only incidents raised at or after this ISO timestamp |
| integer | 50 | Maximum entries (1-500) |
Each incident carries its triage timeline (raised / acknowledged / mitigated / resolved with minutes-from-raise) and its post-mortem link.
get_response_metrics
Response metrics computed from the incident record set.
Parameter | Type | Default | Description |
| integer | 30 | Look-back window in days (1-365) |
| string enum | - | Filter by team |
| string | - | Filter by service |
Returns mean/median/p95/min/max time-to-acknowledge and time-to-mitigate, acknowledgement and mitigation SLA compliance percentages, escalation rate, incident volume by severity, and a daily time series. All figures are computed from the actual incident records with Python statistics.
Related MCP server: StackWitness
Installation
pip install -r requirements.txtUsage
python main.pyState is persisted as JSON in ./state/oncall_state.json. Override the location with
MCP_ONCALL_RETAINER_STATE_DIR.
Connecting to an MCP client
{
"mcpServers": {
"oncall-retainer": {
"command": "python3",
"args": ["/tmp/v3-services/mcp-oncall-retainer/main.py"]
}
}
}License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Manage incidents and on-call: list/create/update incidents, who is on call, on-call overrides.
Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents.
Uptime monitoring, status pages and on-call in one place. Create and tune monitors for HTTP, TCP, DNS, ping, TLS certificates, domain expiry, heartbeats and scripted browser logins. Run a check on demand, read uptime and response-time history, acknowledge and resolve incidents, post incident updates, schedule maintenance windows and edit public status pages. Read-only until you grant write access.
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.
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 gradedqualityDmaintenanceLet agents read and manage your org’s independent monitors, incidents, status pages, and alerts (honest measured state, no false greens).-- AlicenseAqualityBmaintenanceEnables 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.2881 npm4Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables users to retrieve and manage tickets and comments, analyze tickets and draft responses, and access Help Center articles as a knowledge base.-