How google/mcp-security works
Project Type and Purpose
• This is a collection of backend microservices (Python packages) implementing Google’s Model Context Protocol (MCP) servers for security operations and threat intelligence.
• The goal is to let MCP-aware clients (e.g., Claude Desktop, the cline.bot VS Code extension, or a Google ADK agent) interact with Google SecOps products (Chronicle, SOAR, GTI, SCC) or third-party integrations in a uniform way.
High-Level Architectural Components
a. Clients
• Google ADK Agent (web UI at localhost:8000)
• MCP clients (Claude Desktop, cline.bot) via stdio transport or HTTP (uv)
b. MCP Server Microservices
• SecOps MCP (server/secops/secops_mcp/server.py)
• SecOps SOAR MCP (server/secops-soar/secops_soar_mcp/server.py)
• GTI MCP (server/gti/gti_mcp/server.py)
• SCC MCP (server/scc/scc_mcp.py)
c. Integration Adapters (within each microservice)
• SecOps SOAR: dozens of “marketplace” modules (one per third-party or Google service)
• SecOps: tool modules for entity lookup, IOC matching, alerts, events, threat intel
• GTI & SCC: lightweight adapters to Google APIs (VirusTotal, Chronicle, Security Command Center)
d. External Services
• Google Cloud APIs (Chronicle, Security Command Center, Vertex AI / GenAI SDK)
• Third-party SaaS / security products (ServiceNow, Slack, AWS GuardDuty, etc.)
e. Documentation & CI/CD
• docs/ folder with Sphinx-powered site, GitHub Actions for docs deployment
• .github/workflows/deploy-docs.yml
Relationships and Data Flows
• Clients → MCP Server: invoke MCP commands over STDIO or HTTP (Uvicorn/ASGI)
• MCP Server Core → Integration Adapters: load tool modules dynamically based on environment flags or CLI args
• Adapters → External Services: authenticate via ADC or API keys, call Google or third-party APIs, return responses
• Responses propagate back up: Adapter → Server Core → Client
Key Architectural Patterns
• Microservices: each MCP server is its own Python package, independently deployable
• Plugin/Adapter Pattern: SecOps SOAR server dynamically discovers and loads one Python module per integration
• Hexagonal (Ports & Adapters): core server logic defines MCP “ports,” adapters implement them for each external system
• Environment-driven Configuration: each server uses ENV Vars or .env files to enable/disable services
Technologies & Frameworks
• Python 3.11+, Uvicorn (ASGI server), FastAPI (likely underlying), Google ADK SDK, pytest for tests
• Sphinx for documentation, GitHub Actions for CI