MCP Gateway · Cursor
Connect Splunk to Cursor
Cursor can bring Splunk search results into the editor next to the code that produced them. The Speakeasy MCP Gateway gives each developer one URL for Splunk, applies their role's rules to every tool call, and logs each search against the developer's email.
- Category
- Infrastructure
- Tools
- 9
- Authentication
- API key
- Cursor
- Editor and terminal
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 Cursor 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 Cursor
Add the gateway to Cursor in one click from the Organization Gateway page.
On the Organization Gateway page in Speakeasy, choose Cursor under Install.
Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.
- 04
Sign in and use Splunk from Cursor
The first time Cursor 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 Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.
For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.
Use cases
What Cursor users do with Splunk
Write an SPL search in the editor
Draft a search for a new dashboard panel, have Cursor run it, and adjust the SPL until the results look right before you save it.
Look up a macro or lookup
When a search uses a macro or lookup you don't recognize, Cursor fetches that knowledge object so you can see how it is defined before relying on it.
Check KV Store collection sizes
Before your code writes more records to a KV Store collection, Cursor pulls the size, count and storage figures for each collection.
Tools
9 tools
Each Splunk tool can be allowed or denied per team and role at the MCP Gateway before Cursor 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 Cursor
The gateway covers every client the same way. The rest depends on what Cursor 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 Cursor. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Cursor
Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.
User attribution
Cursor
Every Cursor hook event carries the user's email.
Budgets
Cursor
Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.
Device agent and MDM
Cursor
The device agent installs the marketplace and plugins and reapplies them every minute.
- Cursor Cloud agents need a checked-in
.cursor/hooks.json. Session and MCP-specific hooks don't run there. - After a plugin update, members run Developer: Reload Window.
Questions
Frequently asked questions
Is every Splunk call from Cursor tied to a person?
What do Cursor users do after the Splunk plugin changes?
How do Cursor users get Splunk?
Are Splunk calls from Cursor logged?
Connect more