Skip to content

Google SecOps MCP connector

The Google SecOps connector brings alert grouping rules, announcements, case alert context and involved entities into Elaichi, so Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can work with them under each analyst's own access.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

List alert grouping rules that merge phishing alerts into one case

Working in Google SecOps with Elaichi

  • Get single Google SecOps alert grouping rule by ID
  • List all Google SecOps alert grouping rules
  • Get single Google SecOps announcement by ID
Ask anything…
Governance / Audit log Last 24 hours
Google SecOps Get single Google SecOps announcement by ID Emily Carter · ChatGPT · 9:41 AM Done
Google SecOps List all Google SecOps alert grouping rules Emily Carter · ChatGPT · 9:41 AM Done
Google SecOps Get single Google SecOps alert grouping rule by ID Emily Carter · ChatGPT · 9:41 AM Done
Google SecOps Create a Google SecOps alert grouping rule Megan Brooks · Claude · 9:38 AM Done
Google SecOps Update a Google SecOps alert grouping rule by ID Ryan Hayes · Cursor · 9:35 AM Done

How to connect Google SecOps to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Google SecOps MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Google SecOps MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Google SecOps MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Google SecOps MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Google SecOps MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Google SecOps to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with Google SecOps through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Google SecOps is logged.

  • SOC

    Catch a case alert up after triage

    Add what you found as context properties on the case alert and record the hosts, users and addresses involved, so the next analyst on shift sees the full picture in Google SecOps.

  • Detection engineering

    Tune alert grouping rules in plain language

    Ask which alert grouping rules exist in Google SecOps, review the one that keeps splitting related alerts, and update it so they land in a single case.

  • Incident response

    See everyone and everything involved in an alert

    Fetch the entity cards for a case alert and get a plain summary of the accounts, machines and indicators tied to it before you join the bridge call.

  • Threat intelligence

    Tag an involved entity with what you know

    Add or update a property on an involved entity in Google SecOps, such as a known-bad flag or a campaign name, so analysts see the intel beside the alert.

  • Security engineering

    Provision a BigQuery export for reporting

    Set up the Google SecOps export to BigQuery from a prompt, so the analytics team can query detections without waiting on a ticket.

  • Security leadership

    Post an announcement to the whole SOC

    Draft an announcement about a new playbook, a maintenance window or a shift change and publish it in Google SecOps where every analyst will see it.

Try asking

  • “List alert grouping rules that merge phishing alerts into one case”
  • “Show the involved entities on case alert 4821 and summarize them”
  • “Draft an announcement about tonight's SIEM maintenance window”

See all 573 Google SecOps tools →

What connecting Google SecOps gets you

6 screens from Elaichi, each doing one job for your Google SecOps account.

Elaichi Agent

Ask Elaichi to work across your apps.

List alert grouping rules that merge phishing alerts into one case

Show the involved entities on case alert 4821 and summarize them

Draft an announcement about tonight's SIEM maintenance window

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask Google SecOps questions in plain language.

Three starter prompts answer from live case alerts, grouping rules and announcements.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint connects Google SecOps to every client.

Claude, ChatGPT and Cursor share one governed endpoint, no SDK and no shared API key.

ElaichiTools
Tool Action Description
Create a Google SecOps alert grouping rule Create Creates a new alert grouping rule. Defines new criteria for alert aggregation, specifying how future incoming alerts should be consolidated into cases based on shared attributes or entity correlations. Returns a AlertGroupingRule. Required: entityType, categoryDetails, category, groupingType. [POST /v1/{parent}/alertGroupingRules]
Delete a Google SecOps alert grouping rule by ID Delete Deletes an alert grouping rule. This permanently removes the rule from the system, and alerts previously governed by this rule will no longer be aggregated based on its criteria. The id is the alert grouping rule ID (last segment of its resource name). Required: id. [DELETE /v1/{name}]
Get single Google SecOps alert grouping rule by ID Get Gets an alert grouping rule. Use this method to retrieve the configuration of a specific rule that defines how alerts are automatically grouped into cases based on criteria like alert type, product name, or data source upon ingestion. The id is the alert grouping rule ID (last segment of its resource name). Returns a AlertGroupingRule. Required: id. [GET /v1/{name}]
List all Google SecOps alert grouping rules List Lists alert grouping rules. Supports filtering by category or grouping type. [GET /v1/{parent}/alertGroupingRules]
Update a Google SecOps alert grouping rule by ID Update Updates an existing alert grouping rule. Use this method to modify rule criteria, such as the entity types used for correlation or the specific category details like alert types or products included in the rule. The id is the alert grouping rule ID (last segment of its resource name). Returns a AlertGroupingRule. Required: id, entityType, categoryDetails, category, groupingType. [PATCH /v1/{alertGroupingRule.name}]

Tool catalog

573 Google SecOps tools ready without any code.

Alert grouping rules, announcements, case alerts and involved entities, every resource and method cataloged.

ElaichiToolboxes
Name Source template Tools Created

SOC toolbox

Google SecOps · case alerts and involved entities

Google SecOps starter 18 Mar 4, 2026

Detection engineering toolbox

Google SecOps · alert grouping rules

— 9 Mar 2, 2026

Incident response toolbox

Google SecOps · case alert context and entity cards

— 24 Feb 27, 2026

Threat intelligence toolbox

Google SecOps · entity properties and indicators

Google SecOps starter 6 Feb 19, 2026

Security engineering toolbox

Google SecOps · BigQuery exports and announcements

— 31 Jan 30, 2026

Security leadership toolbox

Google SecOps · announcements and case oversight

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Google SecOps toolbox.

SOC, detection engineering and incident response each see only the tools their work needs.

ElaichiConnections
Connection Scope Status Access
GO

Google SecOps (SOC Tier 1)

Connected by Emily Carter

Personal • Active 1 team · 6 members
GO

Google SecOps (SOC Tier 2)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
GO

Google SecOps (Detection Engineering)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
GO

Google SecOps (Incident Response)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
GO

Google SecOps (Threat Intel)

Connected by Ryan Hayes

Personal • Active Not shared
GO

Google SecOps (Security Leadership)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates work through one Google SecOps connection.

One person connects, shares with teams and members, and nobody else sees a credential.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Google SecOps Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Google SecOps Alert grouping rules Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Google SecOps Alert grouping rules List Toolbox

Audit log

Every Google SecOps call lands in the log.

When, who, what happened, type and resource, so you can answer who changed a rule.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Google SecOps digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch alert grouping rules

    Google SecOps

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Google SecOps

    Queued

Workflows

Schedules run Google SecOps work end to end.

Case alerts are fetched, grouped, drafted into a digest, approved by a person, then posted back.

Google SecOps health

Refreshed 4 minutes ago · every 15 minutes · from the alert grouping rules collection

Live

Alert grouping rules

1,284 ↓ 12%

Announcements

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Alert grouping rules created

Last 14 days

By team

Share of activity

SOC Tier 1 34%

SOC Tier 2 27%

Detection Engineering 21%

Incident Response 18%

Collections and dashboards

Google SecOps metrics computed with no model.

Four metrics, fourteen days of case alerts created and a split by team, refreshed on schedule.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Google SecOps

All three can connect Google SecOps to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Google SecOps, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Google SecOps tools Allow or restrict single Google SecOps tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Google SecOps call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Google SecOps tools for your AI agents

573 tools are ready to call through Elaichi's MCP endpoint the moment you connect Google SecOps, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Showing 226 of 573 Google SecOps tools here. Connect Google SecOps and call search_tools or tools/list over the MCP endpoint for the complete set.

Questions, answered

How do I connect Google SecOps to Claude?

Connect Google SecOps in Elaichi first, then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Google SecOps connects over OAuth, but it needs an OAuth application registered inside Google SecOps itself, so an administrator brings that client ID and secret into Elaichi once. After that, each person signs in to Google SecOps with their own account and nobody else handles a credential.

Does Google SecOps work with ChatGPT and Cursor as well as Claude?

Yes. Once Google SecOps is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Google SecOps once and every client picks it up.

What can an AI agent actually do with my Google SecOps data?

It can list, read, create, update and delete alert grouping rules and announcements in Google SecOps, add context and involved entities to a case alert, fetch the entity cards tied to an alert, and provision a BigQuery export. Clients do not get a long menu of tools, they search for what they need, so short concrete asks such as list the grouping rules for phishing work better than long sentences.

Does connecting Google SecOps give the AI access to everything in my SIEM?

No. Every call into Google SecOps runs as the person who signed in, so the agent sees the cases, rules and entities that person's Google SecOps role already allows and nothing more. Elaichi can narrow that access further with roles and restrictions, but it can never widen it beyond what Google SecOps itself grants.

Can my team share one Google SecOps connection?

Yes. One administrator connects Google SecOps in Elaichi and shares the connection with a team, and nobody else ever sees or handles the client ID and secret. Each analyst still signs in to Google SecOps as themselves, so the audit log names the actual person behind every case update or rule change.

Can I stop an agent from deleting or changing things in Google SecOps?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting alert grouping rules or updating announcements in Google SecOps for a role or for one person. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

What happens to a Google SecOps connection when someone leaves?

Offboarding that person in Elaichi ends their access to Google SecOps through every client at once. A shared Google SecOps connection keeps working for everyone else on the team. If you want to remove Google SecOps entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

Does the Google SecOps MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Google SecOps is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Google SecOps?

Yes. Both let Claude, ChatGPT or Cursor use Google SecOps. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Google SecOps call.

How is Elaichi different from Composio for Google SecOps?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Google SecOps: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Google SecOps in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot