Beta preview: OAuth for MCP Server
Version 1.1.0 of Splunk MCP Server offers a feature preview of OAuth for MCP Server. This feature can help make Splunk data easier to securely access from AI tools such as Glean, without the need to manage static credentials.
Preview disclaimer
Beta features described in this document are provided by Splunk to you "as is" without any warranties, maintenance and support, or service-level commitments. Splunk makes this Beta feature available at its sole discretion and may discontinue it at any time. Use of Beta features is subject to the Splunk Pre-Release Agreement for Hosted Services.
Participating in the beta preview
You must be a Splunk Cloud customer on Twix version 10.3.x or higher and running MCP Server version 1.1.0 to be eligible for this closed preview.
Complete the following steps:
-
Create a support ticket or ask your account manager to upgrade you to Twix version 10.3.x or higher on Splunk Cloud.
- To submit a support ticket, log into your Splunk account and Create a Case. See https://splunk.my.site.com/customer/s/need-help/create-case
- Include your stack name when submitting your upgrade request.
-
After you are upgraded to Twix, a member of the Splunk team requests OAuth 2.1 enablement for MCP.
- This request goes to the Splunk Identity Service (SIS) team with an expected response time of 1 week.
-
Through your support ticket or account manager you receive updates on the completion of OAuth 2.1 enablement for MCP and when you can being using it.