secops-setup-gemini

Configures Gemini CLI's ~/.gemini/config.json to route Cloud Auth requests to Chronicle via remote-mcp-secops server with specified project ID and headers.

513|130|Updated Apr 2, 2025
One-click install
npx skills add https://github.com/google/mcp-security --skill secops-setup-gemini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secops-setup-gemini
Source: https://github.com/google/mcp-security/tree/main/extensions/google-secops/skills/setup-gemini-cli
Command: npx skills add https://github.com/google/mcp-security --skill secops-setup-gemini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gemini CLI users often struggle to correctly configure the Google SecOps Remote MCP Server. This Skill provides a guided setup flow to ensure proper integration, authentication, and server endpoint accuracy.

Core Features & Use Cases

  • Prerequisite validation: verifies uv availability and Google Cloud authentication readiness.
  • Gemini CLI integration: configures the Gemini client to point to the Chronicle MCP endpoint with the correct project and region.
  • Verification & troubleshooting: provides commands and checks to confirm successful setup and identify common issues.

Quick Start

  1. Install uv if it is not already installed: curl -LsSf https://astral.sh/uv/install.sh | sh
  2. Authenticate with Google Cloud: gcloud auth application-default login; gcloud auth application-default set-quota-project <YOUR_PROJECT_ID>
  3. Gather required values: PROJECT_ID, CUSTOMER_ID, REGION
  4. Update Gemini config at ~/.gemini/config.json by adding the "remote-mcp-secops" server with the provided httpUrl, authProviderType, oauth scopes, timeout, and headers including your project ID
  5. Verify by testing a sample Gemini prompt like: gemini prompt "list 3 soar cases"

Frequently Asked Questions about secops-setup-gemini

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure the Google SecOps Remote MCP Server for Gemini CLI?

To configure the Google SecOps Remote MCP Server for Gemini CLI, you add a server block to the ~/.gemini/config.json file, including the correct httpUrl, authProviderType, oauth scopes, and your Chronicle project headers.

What prerequisites do I need to set up Google SecOps with Gemini CLI?

Prerequisites for Google SecOps Gemini CLI setup include installing the uv tool, authenticating with Google Cloud via gcloud, and gathering your specific PROJECT_ID, CUSTOMER_ID, and REGION values.

How can I verify that my Gemini CLI SecOps setup is working correctly?

Verify your Gemini CLI SecOps setup by running a sample prompt like 'gemini prompt "list 3 soar cases"' to confirm the client successfully communicates with the Chronicle MCP endpoint.

Why does my Gemini CLI fail to connect to the Chronicle MCP endpoint?

Connection failures to the Chronicle MCP endpoint often stem from missing quota project configurations in gcloud, incorrect JSON config formatting, or missing uv installation prerequisites.

Can I use Google SecOps MCP Server with my local Gemini CLI workstation?

Yes, the Google SecOps MCP Server applies to users setting up Gemini CLI on local workstations by guiding authentication, server endpoint configuration, and prerequisite validation.

What is the best way to authenticate Google Cloud for SecOps MCP integration?

The best way to authenticate Google Cloud for SecOps MCP integration is running gcloud auth application-default login followed by setting your quota project with gcloud auth application-default set-quota-project.