MCP Gateway · Claude Cowork
Connect Splunk to Claude Cowork
Cowork can run a longer Splunk investigation from start to finish: finding the right indexes, running a series of searches and writing up what they show. Splunk reaches Cowork as a plugin from your organization's synced marketplace, and Speakeasy checks each prompt before the step runs.
- Category
- Infrastructure
- Tools
- 9
- Authentication
- API key
- Claude Cowork
- Cowork tab in Claude Desktop
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 Cowork 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. Claude Cowork connects to the Splunk server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use Splunk from Claude Cowork
The first time Claude Cowork 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 Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with Splunk
Write a post-incident timeline
Cowork searches the logs across the incident window, orders the key events by time, and writes a timeline that names the hosts and sources involved.
Audit alerts and saved searches
Cowork pulls every alert and saved search, checks which indexes each one reads, and lists the ones pointing at indexes that no longer exist.
Prepare a Splunk access review
Cowork lists Splunk users and roles, compares them with a staff list you provide, and produces a table of accounts to keep, change or disable.
Tools
9 tools
Each Splunk tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork 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 Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
Is Splunk activity in Cowork tied to a person?
Does the device agent set up Splunk in Cowork?
How do Claude Cowork users get Splunk?
Are Splunk calls from Claude Cowork logged?
Connect more