Provides comprehensive tools for managing Splunk On-Call (VictorOps) data, allowing users to interact with the platform to list and resolve incidents, manage teams and users, handle escalation policies, and view on-call schedules.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-server-splunk-oncall who's currently on call across all teams?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for the Splunk On-Call (VictorOps) API. Full coverage of the REST API with automatic read-only detection.
Tool | Description |
| Check if API key is full-access or read-only |
Tool | Description |
| List all current incidents |
| Acknowledge incidents by number |
| Resolve incidents by number |
| Acknowledge all triggered incidents |
| Resolve all triggered incidents |
| Reroute incidents to another user or policy |
| Get event timeline for an incident |
Tool | Description |
| Who is currently on call across all teams |
| On-call schedule for a team |
| On-call schedule for a user |
Tool | Description |
| List all teams |
| Get team details |
| Create a new team |
| Update a team name |
| Delete a team |
| List members of a team |
| Add a user to a team |
| Remove a user from a team |
| List team admins |
| List escalation policies for a team |
Tool | Description |
| List all users |
| Get user details |
| Invite a new user |
| Delete a user (with replacement) |
| List contact methods (phone, email, SMS) |
| List push notification devices |
| User on-call schedule |
| User escalation policies |
| User team memberships |
Tool | Description |
| List routing keys and their policies |
| Create a routing key |
| Delete a routing key |
Tool | Description |
| List all escalation policies |
| Get escalation policy details |
| Create an escalation policy |
| Delete an escalation policy |
Tool | Description |
| List maintenance windows |
| Get maintenance window details |
| Create a maintenance window |
| End a maintenance window early |
Tool | Description |
| Get organization information |
| Organization-wide event timeline |
Tool | Description |
| List recent alerts |
| Historical incident data |
| On-call report for a team |
Related MCP server: mcp-server-splunk-oncall
uvx mcp-server-splunk-oncallOr install from PyPI:
pip install mcp-server-splunk-oncallThe server requires two environment variables:
SPLUNK_ONCALL_API_ID - Your Splunk On-Call API ID
SPLUNK_ONCALL_API_KEY - Your Splunk On-Call API key
Add to your Claude Code MCP settings:
{
"mcpServers": {
"splunk-oncall": {
"command": "uvx",
"args": ["mcp-server-splunk-oncall"],
"env": {
"SPLUNK_ONCALL_API_ID": "your-api-id",
"SPLUNK_ONCALL_API_KEY": "your-api-key"
}
}
}
}The server automatically detects whether the API key is read-only or full-access on first use. When a read-only key is provided, write operations return a clear error message instead of failing with a 403. Use get_access_mode to check.
You can also force read-only mode with a full-access key by setting:
"SPLUNK_ONCALL_READ_ONLY": "true"This is useful when you want to use a full-access key but prevent accidental writes.
MIT
This server cannot be deployed
Manage incidents and on-call: list/create/update incidents, who is on call, on-call overrides.
Manage incidents, alerts, monitors, status pages, on-call and telemetry in OneUptime.
Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents.
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.