Splunk On-Call FAQs

Question 1

What is Splunk On-Call MCP Server?

Accepted Answer

It's a Model Context Protocol (MCP) server designed for Splunk On-Call (formerly VictorOps), offering a comprehensive set of 45 tools to programmatically manage incidents, on-call schedules, teams, and users via its REST API.

Question 2

What key functions can I manage with this tool?

Accepted Answer

You can manage incidents (acknowledge, resolve, reroute), oversee on-call schedules, add/remove team members and users, configure routing keys and escalation policies, and control maintenance windows within your Splunk On-Call environment.

Question 3

Does it support read-only access and how is it handled?

Accepted Answer

Yes, it automatically detects if your API key provides read-only or full-access permissions. For added control, you can also explicitly force read-only mode, even with a full-access key, to prevent accidental write operations.

Question 4

How do I install and configure Splunk On-Call MCP Server?

Accepted Answer

You can install it via `pip install mcp-server-splunk-oncall`. Configuration requires setting two environment variables: `SPLUNK_ONCALL_API_ID` and `SPLUNK_ONCALL_API_KEY` with your respective credentials.

Question 5

What are the main benefits of using this MCP server?

Accepted Answer

This server streamlines your incident response workflows, automates complex on-call rotations, simplifies user and team administration, and enhances overall operational efficiency by providing robust, programmatic control over your Splunk On-Call platform.

Splunk On-Call

Splunk On-Call

Key Features

Use Cases

Key Features

Use Cases