splunk-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPLUNK_HOST | No | Splunk host address | 127.0.0.1 |
| SPLUNK_PORT | No | Splunk management port | 8089 |
| SPLUNK_SCHEME | No | Splunk scheme (http or https) | https |
| SPLUNK_PASSWORD | No | Splunk password | |
| SPLUNK_USERNAME | No | Splunk username |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_knowledge_objectsC | Get knowledge objects from Splunk. Supported types include saved_searches, lookups, macros, etc. |
| search_splunkC | Search Splunk logs with the given query. |
| get_splunk_indexesA | Get list of available Splunk indexes. |
| get_log_statsC | Get log statistics for a specific index. |
| get_all_usersA | Fetch all Splunk users. |
| get_user_infoC | Get detailed information about a specific Splunk user. |
| search_errorsC | Search for error logs across indexes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_indexes_resource | Get available Splunk indexes as a resource. |
TDQS
Scored across 7 tools
Each tool targets a distinct resource or operation: users (all vs specific), indexes, knowledge objects, log statistics, general search, and error search. No overlapping purposes.
Most tools follow 'get_' prefix (5 tools), but two use 'search_' prefix. There is a clear verb_noun pattern, though the verb varies between get and search.
7 tools is well-scoped for a Splunk MCP server, covering essential read and search operations without being excessive or minimal.
The toolset covers core retrieval and search operations, but lacks create/update/delete for knowledge objects and users, which are common Splunk operations.