MCP Gateway · Claude
Connect Splunk to Claude
Security and operations staff can ask Claude questions about Splunk data in plain language. Claude writes the SPL, runs it and explains the result, while the Speakeasy MCP Gateway limits each person to the Splunk tools their role can reach and logs every call.
- Category
- Infrastructure
- Tools
- 9
- Authentication
- API key
- Claude
- Web, desktop and mobile
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 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
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use Splunk from Claude
The first time Claude 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, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with Splunk
Summarize overnight failed logins
Ask Claude how many failed logins happened overnight and from where, and it runs the search and returns a short summary you can paste into the shift handover.
Review who has access to Splunk
For an access review, Claude lists Splunk users with their roles and account status and flags the accounts that look inactive.
Explain what an alert checks
Claude retrieves a saved search or alert and describes in plain words what it looks for, so people outside the security team understand why it fired.
Tools
9 tools
Each Splunk tool can be allowed or denied per team and role at the MCP Gateway before Claude 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
The gateway covers every client the same way. The rest depends on what Claude 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. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Can past Claude conversations about Splunk be reviewed?
Who sets up the Speakeasy connector in Claude?
How do Claude users get Splunk?
Are Splunk calls from Claude logged?
Connect more