Skip to main content

Splunk

The Official card calls the Splunk MCP Server app on a Splunk Cloud stack's management port: https://{stack}.splunkcloud.com:8089/services/mcp. You install the app from Splunkbase and create a token in it. Willow sends that token as Authorization: Bearer <token>. It is the Splunk card with the Official badge. Willow also has a built-in Splunk connector.

Splunk's newer MCP Gateway (https://region-{region}.api.scs.splunk.com/system/mcp-gateway/v1/) is a different endpoint. It needs extra headers (splunk_tenant, X-SF-TOKEN, X-SF-REALM) that this card does not send. Use the card for the management-port app. Add a custom MCP server if you need the gateway.

Set up Splunk​

  1. Install the Splunk MCP Server app (Splunkbase) on the Splunk Cloud stack. You need version 1.0.0 or later if you also use Observability tools.
  2. In the app, create an authentication token. Copy it. Splunk shows it once.
  3. Note the stack name, the subdomain of https://{stack}.splunkcloud.com.

Set up Willow​

  1. Go to MCP Servers → + Add MCP server, open the Splunk card with the Official badge, and click + Use.
  2. Enter the stack name.
  3. Keep API key. Paste Bearer followed by the token.
  4. Click Check connection. Assign groups and Publish.

Everyone who uses this server shares that token.

Troubleshooting​

Splunk returns 401​

Cause: The token was pasted without the Bearer prefix, or it was revoked.

Solution: Paste Bearer plus the token from the MCP Server app. Create a new token if the old one was revoked.

Additional Resources​