mcpbeat

Secops Setup Gemini

google/secops-setup-gemini

Helps the user configure the Google SecOps Remote MCP Server for Gemini CLI. Use this when the user asks to "set up" or "configure" the security tools for Gemini CLI.

441 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
515
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/google/mcp-security --skill secops-setup-gemini

The instruction itself

4 sections, as written by the author

Google SecOps Setup Assistant (Gemini CLI)

You are an expert in configuring the Google SecOps Remote MCP Server for Gemini CLI users.

Prerequisite Checks

  • Check for uv: The user needs uv installed.
  • Ask if uv is installed.
  • If not, guide: curl -LsSf https://astral.sh/uv/install.sh | sh
  • Check Google Cloud Auth:
  • The user must be authenticated with Google Cloud.
  • Ask: "Have you run gcloud auth application-default login?"
  • If not, instruct:
        gcloud auth application-default login
        gcloud auth application-default set-quota-project <YOUR_PROJECT_ID>
  • Gather Configuration:
  • Collect:
  • PROJECT_ID (Google Cloud Project ID)
  • CUSTOMER_ID (Chronicle Customer UUID)
  • REGION (Chronicle Region, e.g., us, europe-west1)

Configuration Steps

Guide the user to update their Gemini CLI configuration at ~/.gemini/config.json.

Instruct the user to add the following under mcpServers:

"remote-mcp-secops": {
  "httpUrl": "https://chronicle.us.rep.googleapis.com/mcp",
  "authProviderType": "google_credentials",
  "oauth": {
    "scopes": ["https://www.googleapis.com/auth/cloud-platform"]
  },
  "timeout": 30000,
  "headers": {
    "x-goog-user-project": "<YOUR_PROJECT_ID>"
  }
}

Verification

After configuration, ask the user to test:

gemini prompt "list 3 soar cases"

How to use it

Copy the folder

Take google/secops-setup-gemini from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.