Splunk MCP Server 2
Splunk MCP Server 2 is catalogued as a MCP server sub-tool of Splunk Observability, with an explicit repository and support boundary.
The current entry and its direct relationships are prominent; every other catalog technology and concept remains visible as muted background context.
10 directly connected nodes · 11 typed relationships · 208 muted catalog entries
List direct catalog relationships
- CatalogObservability Technology
- HierarchySplunk Observability
- RelatedSplunk Observability
- TelemetryMetrics
- TelemetryLogs
- ArchitectureHost Observability
- ArchitectureMicroservices Observability
- ArchitectureCloud Observability
- FunctionAd-Hoc Functions
- FunctionQuerying
- FunctionIntegrations
Catalog position
Splunk MCP Server 2 is nested under Splunk Observability as a MCP server. It is navigable as a companion tool but excluded from the product capability, cost, and market-breadth cohorts [1].
| Field | Catalog record |
|---|---|
| Auxiliary kind | MCP server |
| Parent technology | Splunk Observability |
| Support scope | community |
| Lifecycle | review-required |
| Repository | https://github.com/splunk/splunk-mcp-server2 |
Repository and support boundary
Repository is hosted by the Splunk organization but explicitly describes itself as unofficial. The catalog does not infer vendor support, service availability, or implementation ownership beyond that evidence [1].
Research stance
Verify the repository README, current releases, authentication model, and target product version before operational use. This profile records discoverability and provenance; it is not an endorsement or security review.
Technology-map evidence
Not yet evaluated
Capability, reference-workload cost, and market breadth have not been evaluated. This profile is available for research, but has no comparative score.
Source record
Bibliography
Splunk community, “Splunk MCP Server 2 repository.” GitHub. [Online]. Available: https://github.com/splunk/splunk-mcp-server2. [Accessed: Aug. 20, 2026].
Repository evidence used to identify the tool and delimit its community maintenance scope.Canonical source ↗Return to article ↑
Known limits
Unresolved unknowns
- Compatibility, authentication, release maturity, and support status can change and require version-specific verification.
Public review
Discuss and correct
Comments are public. Proposed factual corrections must be incorporated into version-controlled research before they are treated as published.
Local preview does not have Giscus configured. Native comments and Giscus are never presented as competing primary systems on the same page.