mcp-server-splunk-oncall
Provides tools for interacting with the Splunk On-Call (VictorOps) API, enabling management of incidents (list, acknowledge, resolve, reroute), on-call schedules, teams (CRUD, members, admins, policies), users (CRUD, contact methods, devices, policies, teams), routing keys, escalation policies, maintenance windows, and organization information.
Click on "Install 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-oncallwho is on call right now?"
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-splunk-oncall
MCP server for the Splunk On-Call (VictorOps) API. Full coverage of the REST API with automatic read-only detection.
Tools (45)
Access
Tool | Description |
| Check if API key is full-access or read-only |
Incidents
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 |
On-Call
Tool | Description |
| Who is currently on call across all teams |
| On-call schedule for a team |
| On-call schedule for a user |
Teams
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 |
Users
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 |
Routing Keys
Tool | Description |
| List routing keys and their policies |
| Create a routing key |
| Delete a routing key |
Escalation Policies
Tool | Description |
| List all escalation policies |
| Get escalation policy details |
| Create an escalation policy |
| Delete an escalation policy |
Maintenance
Tool | Description |
| List maintenance windows |
| Get maintenance window details |
| Create a maintenance window |
| End a maintenance window early |
Organization
Tool | Description |
| Get organization information |
| Organization-wide event timeline |
Alerts and Reporting
Tool | Description |
| List recent alerts |
| Historical incident data |
| On-call report for a team |
Related MCP server: splunk-mcp-server
Installation
uvx mcp-server-splunk-oncallOr install from PyPI:
pip install mcp-server-splunk-oncallConfiguration
The server requires two environment variables:
SPLUNK_ONCALL_API_ID- Your Splunk On-Call API IDSPLUNK_ONCALL_API_KEY- Your Splunk On-Call API key
Claude Code
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"
}
}
}
}Read-Only Mode
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.
License
MIT
This server cannot be installed
Maintenance
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/arnstarn/mcp-server-splunk-oncall'
If you have feedback or need assistance with the MCP directory API, please join our Discord server