SecurityInfrastructure MCP Server

A comprehensive collection of **secure** MCP (Model Context Protocol) server implementations for security platform integrations with enterprise-grade

Local serverstdioPython

What is the SecurityInfrastructure MCP server?

SecurityInfrastructure MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A comprehensive collection of secure MCP (Model Context Protocol) server implementations for security platform integrations with enterprise-grade security hardening.

What the assistant can call

Once SecurityInfrastructure is connected, these are the calls the assistant has available:

  • search-events — Execute sanitized SPL queries with injection prevention
  • search-detections — Query detections with FQL validation and whitelisting
  • search-attributes — Search IOCs with XSS and injection prevention
  • Installation — The Installation tool exposed by this server

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration and credentials

You will need 5 environment variables: SPLUNK_HOST, SPLUNK_TOKEN, SPLUNK_VERIFY_SSL, REPLACE_WITH_YOUR_SPLUNK_HOST, REPLACE_WITH_YOUR_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. SecurityInfrastructure's toolset — search-events, search-detections, search-attributes and 1 more — is a fair guide to whether it matches your workflow. It is maintained by jmstar85; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the securityinfrastructure mcp server does with a few real requests.

Available tools

ToolWhat it does
search-eventsExecute sanitized SPL queries with injection prevention
search-detectionsQuery detections with FQL validation and whitelisting
search-attributesSearch IOCs with XSS and injection prevention
InstallationThe Installation tool exposed by this server.

How to install the SecurityInfrastructure MCP server

{
  "mcpServers": {
    "security-infrastructure-splunk": {
      "command": "python",
      "args": ["/FULL/PATH/TO/SecurityInfrastructure/src/splunk_server.py"],
      "env": {
        "SPLUNK_HOST": "REPLACE_WITH_YOUR_SPLUNK_HOST",
        "SPLUNK_TOKEN": "REPLACE_WITH_YOUR_API_TOKEN",
        "SPLUNK_VERIFY_SSL": "true"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
SPLUNK_HOSTEndpoint or connection string the server talks to.Optional
SPLUNK_TOKENCredential the server authenticates with.Yes
SPLUNK_VERIFY_SSLConfiguration value read at startup.Optional
REPLACE_WITH_YOUR_SPLUNK_HOSTEndpoint or connection string the server talks to.Optional
REPLACE_WITH_YOUR_API_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use SecurityInfrastructure to search-events.
  • Use SecurityInfrastructure to search-detections.
  • Use SecurityInfrastructure to search-attributes.

Frequently asked questions

It connects SecurityInfrastructure to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (search-events, search-detections, search-attributes, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with SecurityInfrastructure directly.