While using the open standard Model Content Protocol (MCP) on a Splunk>Cloud instance all request to the 'https://<YOUR_SPLUNK_DEPLOYMENT_NAME>.api.scs.splunk.com/<YOUR_SPLUNK_DEPLOYMENT_NAME>/mcp/v1/ ' endpoint can only retrieve knowledge objects from whichever Search Head is set as primary on the selected Splunk>Cloud stack.
This limits the usefulness of the MCP implementation.
Splunk>Cloud implementation of MCP supports a custom header 'Splunk-Endpoint' which can overwrite the target Search Head for the request by using the full URL used to access the premium Search Head as a value.
For example:
'Splunk-Endpoint: https://es-<XYZ>.splunkcloud.com'
Connect and use an MCP client | Splunk Docs
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
01-Oct-2026
|
Initial Release |