secops-setup-antigravity

Configure Google SecOps Remote MCP Server for Antigravity deployments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the setup and configuration of the Google SecOps Remote MCP Server for Antigravity, eliminating manual, repetitive steps and reducing misconfigurations.

Core Features & Use Cases

  • Guided prerequisites: Verifies Google Cloud authentication and required identifiers (PROJECT_ID, CUSTOMER_ID, REGION) before proceeding.
  • Config merge automation: Reads mcp_config.template.json and merges a remote-mcp-secops entry into ~/.gemini/antigravity/mcp_config.json without overwriting existing servers.
  • Verification-ready: Provides a quick verification step to ensure the new server configuration is discoverable by MCP clients after setup.

Quick Start

Prepare your environment by ensuring you have a Google Cloud authenticated session, create a .env file with your PROJECT_ID and optional SERVER_URL, then run the Antigravity setup to merge your configuration into ~/.gemini/antigravity/mcp_config.json.

Frequently Asked Questions about secops-setup-antigravity

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

FAQPage Schema
How do I configure the Google SecOps MCP Server for Antigravity?

To configure the SecOps MCP Server, you must merge a remote-mcp-secops entry into your Antigravity mcp_config.json file. This process validates Google Cloud authentication, generates an access token, and merges configurations without overwriting existing servers.

What prerequisites do I need to set up SecOps MCP configuration?

Setting up SecOps MCP configuration requires an active Google Cloud authenticated session and specific environment variables. You must define your PROJECT_ID, CUSTOMER_ID, and REGION in a .env file before generating the gcloud access token and merging the configuration.

Can I add a remote-mcp-secops server without overwriting my existing MCP configuration?

Yes, you can add a remote-mcp-secops server without overwriting existing configurations. The setup reads mcp_config.template.json and safely merges the new server entry into ~/.gemini/antigravity/mcp_config.json, leaving other configured MCP servers untouched.

Why is my SecOps MCP setup not working in Antigravity?

Your SecOps MCP setup might fail if prerequisite checks for Google Cloud authentication, PROJECT_ID, CUSTOMER_ID, or REGION fail. The setup validates these requirements and the final configuration to ensure the new server is discoverable by MCP clients.

What is the best way to automate Google SecOps MCP configuration merges?

The best way to automate Google SecOps MCP configuration merges is by using a guided setup that generates gcloud access tokens and programmatically updates ~/.gemini/antigravity/mcp_config.json. This eliminates manual steps, reduces misconfigurations, and validates the final result.