AI 클라이언트가 Google SecOps에서 위협을 조사하고, SOAR 작업을 실행하며, Google Threat Intelligence를 쿼리하고 클라우드 보안 탐지 결과를 감사할 수 있도록 지원합니다.
다른 이름 google/mcp-security
- 스타
- 544
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- —
- 마지막 커밋
- 2026년 11월 11일
- 라이선스
- Apache-2.0
Google Security Operations MCP란?
AI 클라이언트가 Google SecOps에서 위협을 조사하고, SOAR 작업을 실행하며, Google Threat Intelligence를 쿼리하고 클라우드 보안 탐지 결과를 감사할 수 있도록 지원합니다.
프로젝트 README에서 생성된 요약
Google Security Operations MCP server 정보
보안 분석가와 개발자는 Claude Desktop, Cline, Cursor와 같은 AI 클라이언트를 통해 디지털 위협을 조사하고 클라우드 리스크를 직접 관리할 수 있습니다. 이 server suite는 언어 모델을 Google 보안 생태계에 연결하여 자동화된 위협 헌팅, 보안 오케스트레이션 및 리스크 관리를 가능하게 합니다. 사용자는 Google SecOps를 통한 위협 탐지, Google Threat Intelligence를 통한 데이터 쿼리, Security Command Center를 통한 클라우드 탐지 결과 감사를 수행할 수 있습니다.
구현 방식은 유연하며, 완전 관리형 원격 MCP server와 uv 또는 pip를 통해 설치할 수 있는 독립형 패키지를 모두 제공합니다. 이 도구들을 사용하려면 Google Application Default Credentials 또는 CHRONICLE_PROJECT_ID, SOAR_APP_KEY와 같은 특정 환경 변수를 사용하여 인증을 구성해야 합니다. server는 stdio transport를 통해 작동하며 로컬 또는 Google Cloud Run의 FastAPI service로 배포할 수 있습니다.
활용 사례
- 1보안 위협 조사AI 클라이언트에 Google SecOps 내 위협 탐지 및 헌팅 수행을 요청합니다.
- 2보안 대응 자동화Google SecOps SOAR를 통해 오케스트레이션 및 대응 작업을 트리거합니다.
- 3클라우드 보안 리스크 감사Security Command Center 내의 탐지 결과를 관리하고 감사하는 데 server를 사용합니다.
- 4위협 인텔리전스 쿼리AI 인터페이스를 통해 Google의 전문 위협 인텔리전스 데이터에 접근합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
구성
CHRONICLE_CUSTOMER_IDCHRONICLE_PROJECT_IDCHRONICLE_REGIONSOAR_APP_KEYSOAR_URLVT_APIKEY
| 이름 | 설명 | 유형 |
|---|---|---|
| CHRONICLE_CUSTOMER_ID | — | |
| CHRONICLE_PROJECT_ID | — | |
| CHRONICLE_REGION | — | |
| SOAR_APP_KEY | — | |
| SOAR_URL | — | |
| VT_APIKEY | — |
자동 검사
2026년 11월 12일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능통과
- 오픈 소스 라이선스 (OSI)통과
- 최근 1년 내 커밋 또는 릴리스통과
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 원격 엔드포인트가 HTTPS 사용검사되지 않음
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 모델에 대한 숨겨진 지침 없음통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
README
GitHub에서 보기Google Security Operations and Threat Intelligence 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 access Google's security products and services:
- Remote MCP Server for Google SecOps - Fully managed, enterprise-ready MCP server (Recommended)
- Google Security Operations (Chronicle) - For threat detection, investigation, and hunting
- Google Security Operations SOAR - For security orchestration, automation, and response
- Google Threat Intelligence (GTI) - For access to Google's threat intelligence data
- Security Command Center (SCC) - For cloud security and risk management
For the new Remote MCP Server, please see the launch announcement and the setup guide.
Each server can be enabled and run separately, allowing flexibility for environments that don't require all capabilities.
Documentation
Comprehensive documentation is available in the docs folder. You can:
- Read the markdown files directly in the repository
- View the documentation website at https://google.github.io/mcp-security/
- Generate HTML documentation locally using Sphinx (see instructions in the docs folder)
The documentation covers:
- Detailed information about each MCP server
- Configuration options and requirements
- Usage examples and best practices
To get started with the documentation, see docs/index.md.
Authentication
The server uses Google's authentication. Make sure you have either:
- Set up Application Default Credentials (ADC)
- Set a GOOGLE_APPLICATION_CREDENTIALS environment variable
- Used
gcloud auth application-default login
Standalone Usage
Each MCP server can be installed and used as a standalone package.
Installation
You can install the packages using uv tool install (recommended):
# Install packages
uv tool install google-secops-mcp
uv tool install gti-mcp
uv tool install scc-mcp
uv tool install secops-soar-mcp
Alternatively, you can use pip:
pip install google-secops-mcp
pip install gti-mcp
pip install scc-mcp
pip install secops-soar-mcp
Running Standalone
After installation, you can run the servers directly using uvx:
# Run SecOps MCP server
uvx --from google-secops-mcp secops_mcp
# Run GTI MCP server
uvx gti_mcp
# Run SCC MCP server
uvx scc_mcp
# Run SecOps SOAR MCP server (with optional integrations)
uvx secops_soar_mcp --integrations CSV,OKTA
With environment variables:
CHRONICLE_PROJECT_ID="your-project-id" \
CHRONICLE_CUSTOMER_ID="01234567-abcd-4321-1234-0123456789ab" \
CHRONICLE_REGION="us" \
uvx secops_mcp
Using with MCP Clients (Recommended)
You can configure MCP clients to use the installed packages with uvx. Here's an example configuration:
{
"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"
}
}
}
}
You can also use environment files with uvx:
{
"mcpServers": {
"secops": {
"command": "uvx",
"args": [
"--env-file",
"/path/to/.env",
"secops_mcp"
]
}
}
}
Client Configurations
The MCP servers from this repo can be used with the following clients
- Cline, Claude Desktop, and other MCP supported clients
- Google ADK(Agent Development Kit) Agents (a prebuilt agent is provided, details below)
- Google SecOps Extension - Install our example extension for Gemini CLI to get specialized security skills (Triage, Investigate, Hunt).
The configuration for Claude Desktop and Cline is the same (provided below for uv and pip). We use the stdio transport.
Using the Google ADK Autonomous SOC Agent
The repository includes a prebuilt Autonomous Security Operations Center (SOC) Agent powered by Google ADK v2 and the Model Context Protocol in run-with-google-adk.
It can be run locally via an interactive CLI REPL or launched as a FastAPI service for Google Cloud Run:
cd run-with-google-adk
cp .env.example .env
# Interactive terminal investigation REPL
uv run mcp-security-agent chat
# Web UI and Cloud Run REST API server
uv run mcp-security-agent serve --port 8080
For full setup, architecture details, and Cloud Run deployment guides, see the ADK Agent Guide.
MCP Client Config Locations
MCP clients all use the same JSON configuration format (see the MCP Server Configuration Reference), but they expect the file in different locations.
| Client Application | Scope | macOS / Linux Location | Windows Location | Notes |
|---|---|---|---|---|
| Gemini CLI | Global | ~/.gemini/settings.json |
%USERPROFILE%\.gemini\settings.json |
File must include mcpServers. Confirmed in Google Security Ops post. |
| Claude Desktop | Global | ~/Claude/claude_desktop_config.json |
%USERPROFILE%\Claude\claude_desktop_config.json |
Config accessible via Claude > Settings > Developer > Edit Config. |
| Claude Code | Global | ~/.claude.json |
%USERPROFILE%\.claude.json |
Primary config file for Claude Code CLI and extensions. |
| Cursor IDE (Global) | Global | ~/.cursor/mcp.json |
%USERPROFILE%\.cursor\mcp.json |
Enables MCP servers globally across all projects. |
| Cursor IDE (Project) | Project | <project-root>/.cursor/mcp.json |
<project-root>/.cursor/mcp.json |
Workspace/project-specific config file. |
| VS Code (Workspace) | Workspace | <project-root>/.vscode/mcp.json |
<project-root>/.vscode/mcp.json |
Workspace-level config used when an MCP extension (like Cline) is installed. Overrides global config if present. |
| Cline (VS Code Ext.) | Global | Inside VS Code extension data | %APPDATA%\Code\User\globalStorage\<extension-id>\settings\cline_mcp_settings.json |
Exact path varies by VS Code variant and platform. <extension-id> corresponds to the installed extension folder (e.g., saoudrizwan.claude-dev). |
Additional Notes for Windows
%USERPROFILE%→C:\Users\<username>%APPDATA%→C:\Users\<username>\AppData\Roaming<project-root>→ folder opened in VS Code or IDE for the project<extension-id>→ name of the installed extension folder (e.g.,saoudrizwan.claude-devfor Claude/Cline)
Tip: Single Config with Symlinks
If you use multiple MCP clients, you can maintain a single config file and symlink it into each expected location. This avoids drift and keeps your server definitions consistent.
Using uv (Recommended)
{
"mcpServers": {
"secops": {
"command": "uv",
"args": [
"--directory",
"/path/to/the/repo/server/secops/secops_mcp",
"run",
"server.py"
],
"env": {
"CHRONICLE_PROJECT_ID": "your-project-id",
"CHRONICLE_CUSTOMER_ID": "01234567-abcd-4321-1234-0123456789ab",
"CHRONICLE_REGION": "us"
}
},
"secops-soar": {
"command": "uv",
"args": [
"--directory",
"/path/to/the/repo/server/secops-soar/secops_soar_mcp",
"run",
"server.py",
"--integrations",
"CSV,OKTA"
],
"env": {
"SOAR_URL": "https://yours-here.siemplify-soar.com:443",
"SOAR_APP_KEY": "01234567-abcd-4321-1234-0123456789ab"
}
},
"gti": {
"command": "uv",
"args": [
"--directory",
"/path/to/the/repo/server/gti/gti_mcp",
"run",
"server.py"
],
"env": {
"VT_APIKEY": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef"
}
},
"scc-mcp": {
"command": "uv",
"args": [
"--directory",
"/path/to/the/repo/server/scc",
"run",
"scc_mcp.py"
],
"env": {
}
}
}
}
NOTE: uv also supports passing an .env file like so:
"command": "uv",
"args": [
"--directory",
"/path/to/the/repo/server/...",
"run",
"--env-file",
"/path/to/the/repo/server/.env",
"server.py"
]
SOAR_APP_KEY and VT_APIKEY are good candidates for .env
Using pip
You can also use pip instead of uv to install and run the MCP servers. This approach uses a bash command to:
- Change to the server directory
- Install the package in development mode
- Run the server binary
{
"mcpServers": {
"secops": {
"command": "/bin/bash",
"args": [
"-c",
"cd /path/to/the/repo/server/secops && pip install -e . && secops_mcp"
],
"env": {
"CHRONICLE_PROJECT_ID": "your-project-id",
"CHRONICLE_CUSTOMER_ID": "01234567-abcd-4321-1234-0123456789ab",
"CHRONICLE_REGION": "us"
},
"alwaysAllow": [
]
},
"gti": {
"command": "/bin/bash",
"args": [
"-c",
"cd /path/to/the/repo/server/gti && pip install -e . && gti_mcp"
],
"env": {
"VT_APIKEY": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef"
},
"alwaysAllow": [
]
},
"scc-mcp": {
"command": "/bin/bash",
"args": [
"-c",
"cd /path/to/the/repo/server/scc && pip install -e . && scc_mcp"
],
"env": {
},
"alwaysAllow": []
},
"secops-soar": {
"timeout": 60,
"command": "/bin/bash",
"args": [
"-c",
"cd /path/to/the/repo/server/secops-soar && pip install -e . && python secops_soar_mcp/server.py"
],
"env": {
"SOAR_URL": "https://yours-here.siemplify-soar.com:443",
"SOAR_APP_KEY": "01234567-abcd-4321-1234-0123456789ab"
},
"transportType": "stdio"
}
}
}
When to use uv vs pip
- uv: Recommended for most users because it offers faster package installation, better dependency resolution, and isolated environments. It also supports loading environment variables from a file.
- pip: Use when you prefer the standard Python package manager or when you have specific environment setup requirements.
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 described in the usage guide.
Alternatively, you can set UV_ENV_FILE to your .env file and omit the --env-file portion of the configuration.
Refer to the usage guide for detailed instructions on how to set up these environment variables.
Troubleshooting
Running 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-mcp-security/.env" \
scc_mcp.py
Check your PATH(s):
which uv # you may need to restart MCP Client after installing uv
which python || which python3
python --version || python3 --version
Installing in Claude Desktop
To use the MCP servers with Claude Desktop:
- Install Claude Desktop
- Open Claude Desktop and select "Settings" from the Claude menu
- Click on "Developer" in the lefthand bar, then click "Edit Config"
- Update your
claude_desktop_config.jsonwith the configuration (replace paths with your actual paths) - Save the file and restart Claude Desktop
- You should now see the hammer icon in the Claude Desktop interface, indicating the MCP server is active
Installing in cline (vscode extension)
- Install cline.bot extension in VSCode
- Update your
cline_mcp_settings.jsonwith the configuration (replace paths with your actual paths) - Save the file and restart VS Code
License
Apache 2.0
Google Security Operations MCP 질문
Google SecOps MCP server 인증은 어떻게 하나요?
Application Default Credentials, GOOGLE_APPLICATION_CREDENTIALS 변수 또는 gcloud auth application-default login을 통한 Google 인증을 사용합니다. 일부 server는 VT_APIKEY 또는 SOAR_APP_KEY와 같은 자체 키가 필요할 수 있습니다.
Google SecOps MCP server를 어떻게 설치하나요?
uv tool install 또는 pip를 사용하여 google-secops-mcp, gti-mcp, scc-mcp, secops-soar-mcp와 같은 독립형 패키지를 설치합니다. 설치 후 uvx로 실행할 수 있습니다.
이 보안 MCP server와 호환되는 클라이언트는 무엇인가요?
Cline, Claude Desktop, Claude Code, Cursor, Gemini CLI 및 기타 MCP 지원 클라이언트와 Google ADK agent에서 사용할 수 있습니다.
Google Threat Intelligence server에 필요한 사항은 무엇인가요?
GTI server는 VT_APIKEY 환경 변수에 설정된 VirusTotal API key가 필요합니다. MCP client config의 env 블록에서 설정합니다.
이 server들로 사전 구축된 자율 SOC agent를 실행할 수 있나요?
네, 해당 repo에는 Google ADK와 MCP 기반으로 구축된 Autonomous SOC Agent가 포함되어 있습니다. 대화형 CLI REPL 또는 Cloud Run용 FastAPI service로 실행할 수 있습니다.