Splunk MCP Server

Splunk publishes the Splunk MCP Server app on Splunkbase (uid 7931, appid Splunk_MCP_Server), an installable package for a customer's own Splunk Search Head or Search Head Cluster that gives AI assistants a Streamable HTTP interface to Splunk platform data. As of 2026-09-15 the current release, 2.0.0, released September 3, 2026, documents 33 tools across three families: 16 splunk_-prefixed core platform tools such as splunk_run_query and splunk_get_indexes, 5 saia_-prefixed Splunk AI Assistant tools such as saia_generate_spl, and 12 o11y_-prefixed Splunk Observability tools such as o11y_get_apm_services. Clients authenticate with OAuth 2.1 Authorization Code plus PKCE, layered on Splunk's own token-based authentication; help.splunk.com documents dedicated setup pages for connecting Cursor and Claude to the server.

Authority is first-party on two Splunk-controlled surfaces: the app is documented at help.splunk.com under Splunk's own product docs, and it is listed on Splunkbase, Splunk's own app marketplace, with vendor field "Splunk LLC." No repository is linked from the advisory, the CVE record, or the Splunkbase listing; a similarly named repository, splunk/splunk-mcp-server2, is unrelated and self-describes as "Unofficial." The server is not registered in the official MCP Registry, which returned zero results for a Splunk search on 2026-09-15.

Splunk disclosed CVE-2026-76404 on 2026-08-19, assigned by Cisco's CNA (the CNA assignment is the only documented Cisco/Splunk connection; no page fetched states that Cisco owns Splunk), rated CVSS 9.1 critical. Versions of the Splunk MCP Server app below 1.2.1 deserialized untrusted data in the app's credential management component, letting a user holding the admin Splunk role execute arbitrary commands on the host. Splunk's own Splunkbase release API records version 1.2.1 as published 2026-06-25, roughly eight weeks before the advisory; its release entry does not mention security, describing a new MCP Telemetry Dashboard and Guardrails UI instead.