Skip to content

SSO

Google Workspace MCP connector

The Google Workspace connector brings your users, groups, licenses, org units, roles, and usage reports into Claude, ChatGPT, Cursor, and any MCP client through one Elaichi endpoint, with each person working inside their own admin access.

Connect on Elaichi How to connect

  • How it connects. OAuth or API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Google Workspace to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Google Workspace once

  1. Open Connections, choose Add connection, and pick Google Workspace.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Approve it in Google Workspace. Google Workspace's own window opens. Whoever approves it decides what this connection can reach.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

google workspace
Google Workspace
Auth0
Google
Okta
Torii
World
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Google Workspace to 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.

Connect Google Workspace to 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 today. The plugin directory lives at chatgpt.com/plugins.

Connect Google Workspace to 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.

Connect Google Workspace 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.

Connect Google Workspace on Elaichi See pricing

Use cases

What teams do with Google Workspace through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • IT

    Set up a new hire before day one

    Create the Google Workspace account, add the person to the right groups, and confirm they sit in the correct org unit from a single request. No clicking through the admin console screen by screen.

  • IT

    Finish offboarding the same afternoon

    Look up a leaver's account, remove them from every group they belong to, and update or delete the account once HR gives the word.

  • People

    Keep group memberships honest

    Ask who is on the all-hands list or the regional sales group, spot people who moved teams months ago, and fix the membership on the spot.

  • Finance

    Reconcile license spend before renewal

    List assigned Google Workspace licenses alongside active users to find seats nobody is using, then bring a real number to the renewal conversation.

  • Security

    Review admin roles and third-party tokens

    List every role and who holds it, flag super admin assignments that should not exist, and see which outside apps have tokens granted by your users.

  • Operations

    Pull usage reports for the quarterly review

    Gather Google Workspace usage reports by org unit and turn them into a short summary of who is active and where adoption is thin.

Try asking

  • “List all Google Workspace groups with no members.”
  • “Which users were created in the last 14 days?”
  • “Show group members for the finance-team group.”

See all 21 Google Workspace tools below

AI tools

Google Workspace tools for your AI agents

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

See it in Elaichi

What connecting Google Workspace gets you

6 screens from the product, each doing one job for your Google Workspace account.

The agent

Ask about users and groups in plain language.

Starter prompts answer from live Google Workspace users, groups and members.

  • users
  • groups
  • group members
  • customers

Ask Elaichi to work across your apps.

List all Google Workspace groups with no members.

Which users were created in the last 14 days?

Show group members for the finance-team group.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor share one endpoint.

Connect any MCP client over OAuth, with no SDK and no shared key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

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

Emma Laurent

 • Connected 4 minutes ago
Cursor
S

Sofia Ricci

 • Connected 2 hours ago
ChatGPT
C

Clara Nowak

 • Connected Yesterday

Tool catalog

21 Google Workspace tools, no custom code.

Browse tool names, resources and methods for users, groups, members and customers.

  • List all Google Workspace users
  • Get single Google Workspace user by ID
  • Create a Google Workspace user
  • Update a Google Workspace user by ID
ElaichiTools
Tool Action Description
List all Google Workspace users List List all Google Workspace users in the directory. Returns a collection of user objects including id, primaryEmail, and name.
Get single Google Workspace user by ID Get Get a single Google Workspace user by id. Returns the full user object including id, primaryEmail, name, and associated account details. Required: id.
Create a Google Workspace user Create Create a new Google Workspace user in the directory. Returns the created user object including id and primaryEmail. Required: primaryEmail, name (givenName and familyName), and password.
Update a Google Workspace user by ID Update Update an existing Google Workspace user by id, replacing the resource with the supplied fields. Returns the updated user object including id and primaryEmail. Required: id.
Delete a Google Workspace user by ID Delete Delete a Google Workspace user by id. Returns an empty 204 response on success. Required: id.

Toolboxes

Every team gets its own curated toolbox.

IT, Security and HR each see only the Google Workspace tools they need.

  • IT operations
  • Security
  • People operations
  • Helpdesk
ElaichiToolboxes
Name Source template Tools Created

IT operations toolbox

Google Workspace · users and provisioning

 Google Workspace starter 18 Mar 4, 2026

Security toolbox

Google Workspace · group membership reviews

 — 9 Mar 2, 2026

People operations toolbox

Google Workspace · joiners and leavers

 — 24 Feb 27, 2026

Helpdesk toolbox

Google Workspace · user lookups and resets

 Google Workspace starter 6 Feb 19, 2026

Compliance toolbox

Google Workspace · access evidence and reports

 — 31 Jan 30, 2026

Finance toolbox

Google Workspace · license counts per customer

 — 12 Jan 22, 2026

Shared connections

Teammates work without ever seeing a credential.

See who connected each Google Workspace account and which teams and members share it.

  • Corporate directory
  • EMEA staff
  • Contractors
  • Helpdesk read only
ElaichiConnections
Connection Scope Status Access
GO

Google Workspace (Corporate directory)

Connected by Emma Laurent

 Personal • Active 1 team · 6 members
GO

Google Workspace (EMEA staff)

Connected by James Whitfield

 Organization • Active 3 teams · 24 members
GO

Google Workspace (Contractors)

Connected by Sofia Ricci

 Organization • Active 2 teams · 11 members
GO

Google Workspace (Helpdesk read only)

Connected by Daniel Ortega

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

Google Workspace (Security review)

Connected by Clara Nowak

 Personal • Active Not shared
GO

Google Workspace (Subsidiary domain)

Connected by Michael Brennan

 Personal • Active 2 teams · 9 members

Audit log

Answer who changed which group member.

Every call records when, who, what happened, type and resource, append only.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM
E

Emma Laurent

[email protected]

 Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM
J

James Whitfield

[email protected]

 Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM
S

Sofia Ricci

[email protected]

 Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM
D

Daniel Ortega

[email protected]

 Google Workspace Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
C

Clara Nowak

[email protected]

 Google Workspace Users Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
M

Michael Brennan

[email protected]

 Google Workspace Users List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires, an offboarding digest posts back.

Six steps fetch users and groups, group them, draft, get approval, post.

Google Workspace digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. ✓

    Schedule

    Every weekday at 08:00

    0.2s
  2. ✓

    Fetch users

    Google Workspace

    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 Michael Brennan

    Approve

  6. Post the digest

    Google Workspace

    Queued

Collections and dashboards

Google Workspace numbers computed, not asked for.

Four metrics, 14 days of users created, and a team breakdown, refreshed on schedule.

Google Workspace health

Refreshed 4 minutes ago · every 15 minutes · from the users collection

Live

Users

1,284 ↓ 12%

Groups

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Users created

Last 14 days

By team

Share of activity

Corporate directory 34%

EMEA staff 27%

Contractors 21%

Helpdesk read only 18%

Related connectors

More from the catalog

Browse all 400+ connectors →

FAQ

Frequently asked questions

How do I connect Google Workspace to Claude?

Connect Google Workspace in Elaichi first, either by signing in with your Google admin account through OAuth or by pasting an API key, whichever your organization prefers. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. There is no OAuth application to register in Google and no client ID or secret to generate. Sign in when Claude asks and you are working with your Google Workspace users and groups.

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

Yes. Once Google Workspace is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Google Workspace once and every client sees it, with the same access rules in each.

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

With Google Workspace connected, an agent can look up a user or a group, create a new account, update someone's details, add or remove people from groups, and delete an account when someone leaves. It can also list licenses, org units, admin roles and who holds them, third-party tokens users have granted, and usage reports, so you can ask questions like who is a super admin or which licenses are unused and get an answer from live records.

Does connecting Google Workspace give the AI full admin access to my organization?

No. Every request to Google Workspace runs as the person who signed in, so an agent can only see and change what that person's own Google admin role allows. Elaichi can narrow that further, for example to reading users and groups only, but it can never grant more than the person already has in Google Workspace.

Can my team share one Google Workspace connection?

Yes. One admin connects Google Workspace in Elaichi and shares the connection with a team, and nobody else ever handles an API key or signs in to Google on the team's behalf. Each person still signs in to Elaichi as themselves, so the audit log records exactly who created a user or removed a group member, not a shared account.

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

Yes. Restrictions in Elaichi apply per action, so you can allow listing Google Workspace users and groups while blocking creating, updating, or deleting them. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client at all, so no prompt, however worded, can reach it.

What happens to a Google Workspace connection when someone leaves?

Offboarding that person in Elaichi ends their access to Google Workspace through every AI client at once. If they had shared the connection with a team, it keeps working for everyone else. Disconnecting Google Workspace in Elaichi removes it from every client in one step, with no need to visit Claude, ChatGPT, and Cursor separately.

Put Google Workspace in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.

Connect Google Workspace Talk to us