MCP Gateway · Claude Code
Connect Splunk to Claude Code
Claude Code can search Splunk for the log lines behind a failing request while the code is open in front of you. Through the Speakeasy MCP Gateway, each developer reaches Splunk at one URL, calls only the Splunk tools their role allows, and leaves an audit entry for every search.
- Category
- Infrastructure
- Tools
- 9
- Authentication
- API key
- Claude Code
- CLI
Behind the MCP Gateway
Run Splunk MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Splunk call inspected and logged.
Set up
Add Splunk to Claude Code in 4 steps
- 01
Add Splunk from the catalog
An admin finds Splunk in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Splunk authenticates with an API key. Enter it under Upstream headers in the install dialog, or later on the server's Settings tab. The key is stored on the server, sent with every upstream request, and never reaches anyone's client configuration.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Splunk
Give teams the
mcp:connectscope on the Splunk server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Splunk to their gateway on the next call, and removing it takes it away. - 03
Connect Claude Code
Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.
Run the command below with your organization gateway URL.
Open
/mcpin Claude Code and choose Authenticate to sign in.claude mcp add --transport http --scope user \ 'speakeasy' \ 'https://<organization host>/mcp/gateway/<organization slug>' - 04
Sign in and use Splunk from Claude Code
The first time Claude Code connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
From then on, Splunk's tools appear in Claude Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.
To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.
Use cases
What Claude Code users do with Splunk
Search logs for a failing request
Give Claude Code a request ID or error message and it runs an SPL search over the right time window, then points to the code path the matching events came from.
Find which index holds your logs
Before writing a search, list the indexes and pull the configuration of the likely one, so Claude Code queries the right data instead of guessing.
Confirm a new logger is reporting
After adding logging, check the hosts, sources and sourcetypes seen in the index over the last hour to confirm events from your service are arriving.
Tools
9 tools
Each Splunk tool can be allowed or denied per team and role at the MCP Gateway before Claude Code sees it.
splunk_get_info
Get comprehensive information about the Splunk instance. Retrieves system information including version, hardware specs, and operational status.
splunk_get_indexes
Get a list of indexes from Splunk. Indexes are data repositories where machine data is stored and organized.
splunk_get_index_info
Get detailed information about a specific Splunk index. Returns comprehensive configuration and status information for the specified index.
splunk_get_user_list
Get a list of users from Splunk. Retrieves information about all users including authentication details, roles, and account status.
splunk_get_user_info
Retrieves detailed information about the currently authenticated user including roles and permissions. Returns comprehensive user profile data for the current session.
splunk_run_query
Execute a Splunk search query and return the results. This is the primary tool for running Splunk searches using SPL (Search Processing Language). Use this to retrieve log data, perform aggregations, analyze events, and extract insights from your Splunk environment.
Control
What Speakeasy can see and stop in Claude Code
The gateway covers every client the same way. The rest depends on what Claude Code exposes to Speakeasy.
Tool logs
Gateway
Every Splunk call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Splunk tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Splunk can reject a tool request before it reaches the server, or withhold a result from Claude Code. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Claude Code
Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.
User attribution
Claude Code
Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.
Budgets
Claude Code
Spend limits can block Claude Code traffic once a budget is reached.
Device agent and MDM
Claude Code
The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.
Anthropic inference hooks
Claude Code
On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).
- Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
- Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.
Questions
Frequently asked questions
Can Claude Code run any SPL search against Splunk?
How are Splunk searches from Claude Code tied to a person?
How do Claude Code users get Splunk?
Are Splunk calls from Claude Code logged?
Connect more