Splunk
Run searches and read indexes/saved searches on Splunk Cloud Platform.
About
Splunk ships in the w6w first-party pack. It declares 8 actions, 1 health check, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.splunk- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Monitoring & Observability · DevOps & Infrastructure
Overview
Splunk brings search and monitoring data from a Splunk Cloud Platform stack into a workflow — dispatching searches, reading back results, and listing saved searches and indexes. Splunk’s search API is asynchronous by default: dispatching a search returns a job ID immediately, and separate actions check the job’s progress and fetch its results once complete, modeling the real asynchronous behavior rather than pretending it is instant.
A dedicated oneshot search action covers the opposite case — a search small enough to wait for inline, returning results directly without managing a job. Saved-search and index actions round out the picture: listing an account’s configured reports and the indexes available to search against, including metric indexes alongside the more common event indexes.
This app is scoped specifically to Splunk Cloud Platform rather than self-hosted Splunk Enterprise, since a self-hosted install can live at any hostname a workflow sandbox cannot know about ahead of time.
Build with Splunk
Three routes to the same 8 actions. The Workflow tab is generated from Splunk's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
List Saved Searches
saved-search-get-many List saved searches (Splunk Web's "Reports") visible to this credential.
Create Search Job
search-create Dispatch a search as an asynchronous job. Returns a `sid` — poll `search-get` for status, then `search-get-results`.
Get Search Job Results
search-get-results Fetch result rows for a search job by `sid`. Splunk returns nothing useful until the job is done — check with `search-get` first.
Run Search (Oneshot)
search-oneshot Run a search synchronously and get results back directly. Blocks until done — use `search-create` for anything that might run long.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Splunk's real ids.
{
"manifestVersion": "2",
"name": "splunk-example",
"steps": [
{
"id": "search-create",
"uses": {
"app": "io.w6w.splunk",
"action": "search-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"search": "<search>"
}
}
]
}Here are some of the things you can do
-
Create Search Job
performsearch-create -
List Indexes
searchindex-get-many -
List Saved Searches
searchsaved-search-get-many -
Get Search Job Status
readsearch-get -
List Search Jobs
searchsearch-get-many
+3 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Splunk, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Splunk. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "search-create",
payload: {
search: "<value>",
// earliestTime: "<value>",
// latestTime: "<value>",
// execMode: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action search-create --payload '{"search":"<value>"}'Give an AI agent Splunk — without giving it Splunk's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.splunk#search-create",
"input": {
"search": "<search>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Splunk connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Splunk's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Splunk itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Splunk declares its own checks, so its health is a property of the app rather than something the host guesses at.
Splunk Cloud Platform status
Statuspage.io summary from https://status.splunkcloud.com — overall indicator plus per-component state.