Splunk MCP Server
Runs Splunk searches and reads results against a Splunk Cloud deployment, authenticating via an interactive Microsoft Entra (Azure AD) SSO + MFA browser session and calling Splunk's REST layer through same-origin in-page fetches.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Splunk MCP Server
A self-contained Node.js MCP server that runs Splunk searches and reads results against a Splunk Cloud deployment where API tokens are disabled and the only auth path is interactive Microsoft Entra (Azure AD) SSO + MFA.
Instead of a token, the server drives an authenticated browser session: a
human logs in once through a Playwright-managed Chromium browser, and the server
reuses that session to call Splunk's REST layer via the in-page fetch model
(same-origin fetch executed inside the authenticated page, so the HttpOnly
session cookie is attached automatically).
See .kiro/specs/splunk-mcp-server/ for the full requirements and design.
Requirements
Node.js 20 or newer
Chromium (installed automatically via Playwright — see below)
Related MCP server: atlassian-browser-mcp
Install
npm installnpm install runs a postinstall step that downloads the Chromium browser
binary via playwright install chromium. This gives a "just works" setup on
machines with normal network access.
Restricted-network fallback
If your environment blocks network access during postinstall (common in
locked-down corporate setups), the Chromium download will be skipped or fail.
Install the browser explicitly afterwards with:
npx playwright install chromiumYou can also re-run it any time via the provided script:
npm run install:chromiumIf Chromium is still missing when the server starts, it exits with a clear
error telling you to run npx playwright install chromium rather than failing
deep inside the browser launch.
Build
npm run build # compile TypeScript -> dist/
npm run typecheck # type-check without emittingTest
Tests run once (single-execution mode), never in watch mode:
npm test(Watch mode is available for local development via npm run test:watch.)
Run
npm start # runs dist/server.js over the MCP stdio transportConfiguration
The server is configured entirely through environment variables (no config files). All values have documented defaults except where noted; see the design document for the full list. The most common variables:
Variable | Default | Purpose |
|
| Splunk Cloud base URL |
|
| Namespace app |
| (optional) | Not required — the non-namespaced |
Configure in Kiro (mcp.json)
Add the server to your Kiro MCP config. Kiro reads two config files and merges them (workspace overrides user):
User level (applies to all workspaces):
Windows:
%USERPROFILE%\.kiro\settings\mcp.json(e.g.C:\Users\<you>\.kiro\settings\mcp.json)macOS / Linux:
~/.kiro/settings/mcp.json
Workspace level (this project only):
.kiro/settings/mcp.jsonin the workspace root.
Use an absolute path to the built dist/server.js (relative paths only work
when Kiro's working directory is the workspace root). On Windows, escape
backslashes in JSON (\\), or use forward slashes:
{
"mcpServers": {
"splunk": {
"command": "node",
"args": ["C:\\Users\\<you>\\dev\\splunkMCP\\dist\\server.js"],
"env": {
"SPLUNK_BASE_URL": "https://hoopp.splunkcloud.com",
"SPLUNK_APP": "search"
},
"disabled": false
}
}
}macOS / Linux path form:
{
"mcpServers": {
"splunk": {
"command": "node",
"args": ["/Users/<you>/dev/splunkMCP/dist/server.js"],
"env": {
"SPLUNK_BASE_URL": "https://hoopp.splunkcloud.com",
"SPLUNK_APP": "search"
},
"disabled": false
}
}
}Setup order matters: dist/server.js only exists after you build. Run
npm install (pulls Chromium via postinstall) and npm run build first, then
point mcp.json at the absolute path to dist/server.js and reload the MCP
servers in Kiro. On the first tool call the server opens a visible browser
window for the MyApps → Splunk login; after that the persistent profile keeps
re-auth silent.
Security note
The persistent browser profile (user-data-dir) holds a live authenticated session and is as sensitive as being logged in. It is stored per-user with owner-only permissions. Use the logout path to clear it.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Browser MCP for logged-in tasks. Uses your Chrome — credentials stay local. Zero-token replay.
Undetectable cloud browser sessions for AI agents and scrapers. Navigate, extract, click, captcha.
Launch, inspect, control, and share isolated cloud browsers for your agents.
Cloud browsers for AI agents: get past bot detection, sign in with MFA, run web tasks at scale.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceFetches content from authenticated web pages by driving your signed-in Chrome/Edge browser via DevTools Protocol, automatically handling login redirects and reusing sessions across domains.9MIT
- AlicenseBqualityAmaintenanceBrowser-backed MCP wrapper for mcp-atlassian with Playwright SSO auth. Enables AI tools to access Atlassian Server/Data Center instances behind corporate SSO (Okta, SAML, ADFS) where API tokens are not available98186 PyPI4GPL 3.0
- AlicenseBqualityCmaintenanceAutomates Salesforce via browser using Playwright with persistent session. Supports Data Cloud, Setup, and other UI-only areas through generic tools.30MIT
- AlicenseAqualityDmaintenanceEnables MCP clients to automate a real Chrome browser via Playwright, supporting session sharing and tools for navigation, clicking, typing, and more.11108 npm2MIT