splunk-indexes

Discover and inspect Splunk indexes and server configuration via the splunk-mcp server.

650|182|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/automateyournetwork/netclaw --skill splunk-indexes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: splunk-indexes
Source: https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/splunk-indexes
Command: npx skills add https://github.com/automateyournetwork/netclaw --skill splunk-indexes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Network and operations teams often lack quick visibility into which Splunk indexes exist and how the Splunk server is configured, forcing manual logins to the management console for basic discovery tasks.

Core Features & Use Cases

  • Index Discovery: List all available Splunk indexes to understand where log and event data is stored.
  • Server Configuration Inspection: Retrieve Splunk server configuration details through the management port.
  • Use Case: A network engineer investigating an outage asks which indexes contain network data, then inspects the server configuration to confirm data routing before running deeper searches.

Quick Start

Ask the agent to list all Splunk indexes and show which ones contain network data.

Frequently Asked Questions about splunk-indexes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list all Splunk indexes?

Use the get_indexes tool exposed by this skill to list all available Splunk indexes. It connects to the Splunk management port using your configured credentials and returns the full index inventory.

How do I check Splunk server configuration programmatically?

Use the get_config tool, which retrieves the Splunk server configuration through the management interface. You must provide SPLUNK_HOST, SPLUNK_PORT, SPLUNK_USERNAME, and SPLUNK_PASSWORD environment variables first.

What credentials are required to connect to Splunk?

The skill requires four environment variables: SPLUNK_HOST for the server hostname, SPLUNK_PORT for the management port (default 8089), and SPLUNK_USERNAME and SPLUNK_PASSWORD for a service account.

Can this skill search or query data inside Splunk indexes?

No, this skill only discovers indexes and inspects server configuration using get_indexes and get_config. Running SPL searches or retrieving event data from within indexes is outside its documented scope.

Why is the Splunk connection failing on the default port?

The default management port is 8089, but your Splunk deployment may use a different port or block management access. Verify SPLUNK_PORT matches your server settings and that the service account has permission to access the management endpoint.