Skip to content

SSO

Google MCP connector

The Google connector brings Drive files and folders, Docs, Forms responses, and Meet transcripts into Claude, ChatGPT, Cursor, or any MCP client, so each person can ask about them while signed in as themselves and every request is logged.

  • How it connects. Connects over OAuth. 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 to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Google once

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

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

  3. Approve it in Google. Google'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
Google
Auth0
Google Workspace
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 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 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 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 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.

Use cases

What teams do with Google through Elaichi

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

  • Sales

    Recap a customer call from the Meet transcript

    After a discovery call, pull the Google Meet transcript, see who was on the line, and get a short summary of what the prospect asked for before you write the follow-up.

  • Support

    Find the right help doc without digging

    Ask for the Google Doc that covers a refund or setup question and get the current version from Drive, instead of scrolling through shared folders.

  • Operations

    Read survey results without opening the spreadsheet

    Ask what people said in a Google Form, such as an office move survey or a vendor intake, and get the responses grouped and summarized.

  • People

    Check who attended the all-hands

    Pull the participant list and transcript from a Google Meet session to confirm attendance and capture the questions that came up.

  • Marketing

    Locate the latest version of a brief

    Search Drive and shared drives for the campaign brief or launch plan and pull the text of the Google Doc to work from, rather than an old copy someone emailed.

  • Legal

    Pull a contract draft from a shared drive

    Ask for the agreement stored in a specific Google shared drive, read its contents, and compare it with the meeting transcript where terms were discussed.

Try asking

  • “Summarize the responses to last week's onboarding form.”
  • “Find the folders shared with the Finance team.”
  • “List files created in the Marketing drive this month.”

See all 120 Google tools below

AI tools

Google tools for your AI agents

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

See it in Elaichi

What connecting Google gets you

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

The agent

Ask about Drive files in plain language.

Elaichi's agent answers from live Google files, folders, forms and responses.

  • files
  • folders
  • forms
  • responses

Ask Elaichi to work across your apps.

Summarize the responses to last week's onboarding form.

Find the folders shared with the Finance team.

List files created in the Marketing drive this month.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor share one endpoint.

Connect Google through one org-wide MCP endpoint over OAuth, no SDK, 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

120 Google tools ready without custom code.

Browse tool names, resources and methods for files, drives, folders and forms.

  • List all Google files
  • Get single Google file by ID
  • List all Google folders
  • Get single Google folder by ID
ElaichiTools
Tool Action Description
List all Google files List Retrieves the user's files stored in Google Drive. This method allows filtering results using the q parameter, which accepts search queries to find specific files based on name, type, ownership, and other metadata. The response includes key file attributes such as id, name, mimeType, createdTime, modifiedTime, owners, driveId, shared, and permissions.
Get single Google file by ID Get Retrieves metadata or content from a single file on the user's Google Drive. It always requires the ID to fetch.
List all Google folders List List all Google Drive folders. Returns folder objects including id, name, and mimeType, filtered automatically to items of type folder.
Get single Google folder by ID Get Get a single Google Drive folder by id. Returns the full folder metadata including id, name, mimeType, and parents. Required: id.
List all Google drive List List all shared drives available in Google Drive. Returns an array of drive objects including their metadata.

Toolboxes

Every team gets its own Google toolbox.

Curated toolboxes scope Drive and Forms tools to the teams that need them.

  • Sales
  • Marketing
  • People Ops
  • Finance
ElaichiToolboxes
Name Source template Tools Created

Sales toolbox

Google · proposal files and shared folders

Google starter 18 Mar 4, 2026

Marketing toolbox

Google · campaign forms and responses

9 Mar 2, 2026

People Ops toolbox

Google · onboarding forms and user info

24 Feb 27, 2026

Finance toolbox

Google · exported reports and drives

Google starter 6 Feb 19, 2026

Legal toolbox

Google · contract files and folder access

31 Jan 30, 2026

Engineering toolbox

Google · design docs and drive items

12 Jan 22, 2026

Shared connections

Teammates use Google accounts, never the credential.

See who connected each Google account and how many teams and members share it.

  • Sales EMEA
  • Marketing
  • People Ops
  • Finance
ElaichiConnections
Connection Scope Status Access
GO

Google (Sales EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
GO

Google (Marketing)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
GO

Google (People Ops)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
GO

Google (Finance)

Connected by Daniel Ortega

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

Google (Legal)

Connected by Clara Nowak

Personal • Active Not shared
GO

Google (Support)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Answer who exported which Google file.

Append-only log records when, who, what happened, type and resource for every call.

  • 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 Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Google Files Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Google Files 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, a digest posts back.

Six steps fetch Google form responses, group them, draft a digest, then a person approves.

Google digest

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

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch files

    Google

    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

    Queued

Collections and dashboards

Google numbers computed, not asked for.

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

Google health

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

Live

Files

1,284 ↓ 12%

Folders

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Files created

Last 14 days

By team

Share of activity

Sales EMEA 34%

Marketing 27%

People Ops 21%

Finance 18%

FAQ

Frequently asked questions

How do I connect Google to Claude?

First, connect Google in Elaichi. You are sent to the normal Google sign-in screen, you choose your account and click Allow, and you are done; there is no client ID or secret to generate. Then in Claude, open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and your Google files, Docs, Forms, and Meet records are available.

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

Yes. Once Google 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 once and every client you use picks it up.

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

With Google connected, an agent can search Drive and shared drives for files and folders, read the text of a Google Doc, list Google Forms and read their responses, and pull Google Meet conference records including transcripts and who attended. It reads and reports; the tools available today do not create, edit, or delete anything in Google. Because Google offers a lot of tools, short concrete asks like "find the Q3 pricing doc" work better than long paragraphs.

Does connecting Google give the AI access to everything in my Drive and shared drives?

No. When you connect Google, the agent sees only the files, folders, shared drives, Forms, and Meet records you could already open yourself, because every request runs under your own Google sign-in and Google's sharing rules still apply. Elaichi can narrow that access further, for example to search and reading only, but it can never widen it beyond what Google already lets you see.

Can my team share one Google connection?

Yes. One person connects Google in Elaichi and shares the connection with a team, and nobody else has to handle a password, token, or credential. Each teammate still signs in to Elaichi as themselves, so when they search Drive or read a Meet transcript the audit log names that person, not the person who set up the Google connection.

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

Yes, and with Google it is already the case: the tools this connector provides only list, search, and read Drive files, Docs, Forms responses, and Meet records, so nothing can be changed or deleted through it. Restrictions in Elaichi work per action, and a blocked action is never shown to Claude, ChatGPT, or Cursor at all, so no prompt, however worded, can reach it.

What happens to a Google connection when someone leaves?

When you offboard someone in Elaichi, their access to the Google connection ends at once, in Claude, ChatGPT, Cursor, and every other client together. If they were using a Google connection shared with their team, it keeps working for everyone else. If you want to remove Google entirely, disconnecting it once in Elaichi removes it from every client for everyone.

Put Google in front of your team

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