Splunk Automated Triage MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SMTP_TO | Yes | Recipient email address | triage@local.test |
| SMTP_FROM | Yes | Sender email address | splunk-triage@local.test |
| SMTP_HOST | Yes | SMTP server host | host.docker.internal |
| SMTP_PORT | Yes | SMTP server port | 1025 |
| SPLUNK_HOST | No | Splunk host | host.docker.internal |
| SPLUNK_WEB_BASE | No | Splunk web base URL for deep links | http://localhost:8000 |
| SPLUNK_API_TOKEN | Yes | Splunk REST API bearer token (minted by setup_splunk.py) | |
| SPLUNK_HEC_TOKEN | Yes | Splunk HEC token for data injection (minted by setup_splunk.py) | |
| SPLUNK_VERIFY_SSL | No | Verify SSL for Splunk connections | false |
| SPLUNK_WEB_LOCALE | No | Splunk web locale | en-US |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityStale
ResponsivenessNo issues