Hi, I am trying to validate connectivity to the official Splunk MCP Server app before integrating it with an MCP client / Google ADK. Current environment: - Splunk MCP Server app version: 1.0.3 - App status: Enabled - Server status in app: active - Encrypted MCP token was generated successfully The app publishes these endpoints: 1. https://SPLUNK_HOST:8089/services/mcp 2. https://SPLUNK_HOST:443/en-US/splunkd/__raw/services/mcp I tested both endpoints using the client recommended in Splunk documentation: npx -y mcp-remote "https://SPLUNK_HOST:8089/services/mcp" --header "Authorization: Bearer ENCRYPTED_TOKEN" and npx -y mcp-remote "https://SPLUNK_HOST:443/en-US/splunkd/__raw/services/mcp" --header "Authorization: Bearer ENCRYPTED_TOKEN" Observed behavior: - Endpoint https://SPLUNK_HOST:8089/services/mcp - http-first => HTTP 405 Method Not Allowed - sse-only => HTTP 405 - Endpoint https://SPLUNK_HOST:443/en-US/splunkd/__raw/services/mcp - http-first => HTTP 404 Page not found - sse-only => HTTP 405 At this point I have already ruled out: - local client issues - Python / ADK issues - missing encrypted token - basic network connectivity issues Questions: 1. For Splunk MCP Server 1.0.3, which of these endpoints is the correct one for remote MCP clients such as mcp-remote? 2. Should the published endpoint support streamable HTTP / SSE out of the box? 3. Is any additional server-side configuration required beyond enabling the app and generating encrypted tokens? 4. Could missing capabilities such as mcp_tool_execute cause this behavior, or would that normally produce a different error? 5. Are there known cases where the app UI shows endpoints, but the remote transport is not actually exposed correctly? Thanks. cto para clientes MCP remotos como ... View more