MCP Security MCP Server

This repository contains Model Context Protocol (MCP) servers that enable MCP clients (like Claude Desktop or the cline.bot VS Code extension) to

Local serverstdioPython

What is the MCP Security MCP server?

If you already use MCP Security, the mcp security mcp server is the piece that lets your assistant work with it directly. This repository contains Model Context Protocol (MCP) servers that enable MCP clients (like Claude Desktop or the cline.bot VS Code extension) to access Google's security products and services:.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Installation — You can install the packages using uv tool install (recommended):
  • UV_ENV_FILE — The --env-file option allows uv to use a .env file for environment variables. You can create this file or use system environment variables as
  • Troubleshooting — Running the MCP Server from the CLI (and outside of your MCP client) can reveal issues: uv --verbose \ --directory

Installation

gti_mcp on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Credentials and setup notes

Configuration is passed through the environment: CHRONICLE_PROJECT_ID, CHRONICLE_CUSTOMER_ID, CHRONICLE_REGION, VT_APIKEY, SOAR_URL, SOAR_APP_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Security's toolset — Installation, UV_ENV_FILE, Troubleshooting — is a fair guide to whether it matches your workflow. It is maintained by google; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

  • 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.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
InstallationYou can install the packages using uv tool install (recommended):
UV_ENV_FILEThe --env-file option allows uv to use a .env file for environment variables. You can create this file or use system environment variables as described in the usage guide.
TroubleshootingRunning the MCP Server from the CLI (and outside of your MCP client) can reveal issues: uv --verbose \ --directory "/Users/dandye/Projects/google-mcp-security/server/scc" \ run \ --env-file "/Users/dandye/Projects/google

How to install the MCP Security MCP server

{
  "mcpServers": {
    "secops": {
      "command": "uvx",
      "args": [
        "--from",
        "google-secops-mcp",
        "secops_mcp"
      ],
      "env": {
        "CHRONICLE_PROJECT_ID": "your-project-id",
        "CHRONICLE_CUSTOMER_ID": "01234567-abcd-4321-1234-0123456789ab",
        "CHRONICLE_REGION": "us"
      }
    },
    "gti": {
      "command": "uvx",
      "args": [
        "gti_mcp"
      ],
      "env": {
        "VT_APIKEY": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef"
      }
    },
    "scc-mcp": {
      "command": "uvx",
      "args": [
        "scc_mcp"
      ],
      "env": {}
    },
    "secops-soar": {
      "command": "uvx",
      "args": [
        "secops_soar_mcp",
        "--integrations",
        "CSV,OKTA"
      ],
      "env": {
        "SOAR_URL": "https://yours-here.siemplify-soar.com:443",
        "SOAR_APP_KEY": "01234567-abcd-4321-1234-0123456789ab"
      }
    }
  }
}

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

Configuration

VariableDescriptionRequired
CHRONICLE_PROJECT_IDConfiguration value read at startup.Optional
CHRONICLE_CUSTOMER_IDConfiguration value read at startup.Optional
CHRONICLE_REGIONConfiguration value read at startup.Optional
VT_APIKEYCredential the server authenticates with.Yes
SOAR_URLEndpoint or connection string the server talks to.Yes
SOAR_APP_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP Security to Installation.
  • Use MCP Security to UV ENV FILE.
  • Use MCP Security to Troubleshooting.

Frequently asked questions

It connects MCP Security to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Installation, UV_ENV_FILE, Troubleshooting) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Security directly.