Video
Google Meet MCP connector
Connect Google Meet to Elaichi and Claude, ChatGPT, Cursor, and the Elaichi Agent can look up past meetings, read their transcripts, and see who attended, with each person signed in as themselves and every request 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.
10 tools
How to connect
How to connect Google Meet to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Google Meet once
-
Open Connections, choose Add connection, and pick Google Meet.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Google Meet. Google Meet'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.
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 Meet to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Google Meet to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Google Meet to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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 Meet to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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 Meet through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Catch the deal up after a discovery call
Pull the transcript of yesterday's Google Meet call with a prospect and ask for the objections raised, the next steps promised, and who from their side was actually on the call.
-
Support
Turn an escalation call into case notes
After a screen-share session with an angry customer, ask for a plain summary of what was reported, what was tried on the call, and what the customer was told to expect.
-
Customer Success
Check who showed up to the quarterly review
See which participants joined the account review in Google Meet, how long each stayed, and whether the decision maker you invited ever appeared.
-
People
Prepare interview debriefs from the recording
Ask for the questions each interviewer asked and the answers the candidate gave, pulled straight from the Google Meet transcript, so the debrief starts from what was said rather than memory.
-
Operations
Find the decision buried in last week's standup
Ask which meeting agreed the vendor change and what exactly was decided, and get the transcript passage with the date and the people present.
-
Leadership
Get a digest of the meetings you missed
Ask for a short summary of every Google Meet call you were invited to this week but did not join, including who attended and what was decided.
Try asking
- “Summarize yesterday's customer call transcript for the account team.”
- “List participants across last week's Google Meet conference records.”
- “Pull transcript entries where pricing came up this month.”
AI tools
Google Meet tools for your AI agents
10 tools are ready to call through Elaichi's MCP endpoint the moment you connect Google Meet, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Google Meet gets you
6 screens from the product, each doing one job for your Google Meet account.
The agent
Ask about last week's Google Meet calls.
Plain questions return answers from live conference records, transcripts and participants.
- conference records
- transcripts
- transcript entries
- participants
Ask Elaichi to work across your apps.
Summarize yesterday's customer call transcript for the account team.
List participants across last week's Google Meet conference records.
Pull transcript entries where pricing came up this month.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Google Meet.
One org MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
10 Google Meet tools, no custom code.
Conference records, transcripts, transcript entries, participants and users, each with listed methods.
- List all Google Meet conference records
- Get single Google Meet conference record by ID
- List all Google Meet conference record transcripts
- Get single Google Meet conference record transcript by ID
ElaichiToolsToolboxes
Every team gets its own Google Meet toolbox.
Curate one toolbox per team and scope it to the work they do.
- Sales
- Customer Success
- Recruiting
- Support
ElaichiToolboxesShared connections
Teammates read meeting records without a credential.
Each Google Meet connection shows who connected it and which teams share it.
- Sales EMEA
- Customer Success
- Recruiting
- Support
ElaichiConnectionsAudit log
Answer who read which transcript, exactly when.
Append-only log with time, actor, action, type and resource for every call.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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 turns meetings into a posted digest.
Fetch conference records, group them, draft with an agent, approve, post back.
Google Meet digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch conference records
Google Meet
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Google Meet
Queued
Collections and dashboards
Google Meet health, counted on a schedule.
Four metrics, 14 days of conference records and a breakdown by team.
Google Meet health
Refreshed 4 minutes ago · every 15 minutes · from the conference records collection
Conference records
1,284 ↓ 12%
Transcripts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Conference records created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Customer Success 27%
Recruiting 21%
Support 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Google Meet to Claude?
Two steps. In Elaichi, choose Google Meet and connect it, which opens Google's own sign-in screen where you approve access with your Google account; there is no client ID or secret to generate and no application to register. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in when Claude asks and your Google Meet meetings, transcripts, and participant lists are available.
Does Google Meet work with ChatGPT and Cursor as well as Claude?
Yes. Once Google Meet 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 Meet once and every client you use can reach it.
What can an AI agent actually do with my Google Meet data?
With Google Meet connected, an agent can look up past meetings, read their transcripts line by line, see who joined and when, and check people in your Google Meet directory. That means it can summarize a call, pull out the action items, tell you who attended a review, or find the meeting where a decision was made. This connector reads Google Meet; it does not schedule, change, or delete meetings.
Does connecting Google Meet give the AI every meeting in my company?
No. Access follows the person who signed in, so an agent working through your Google Meet connection sees only the meetings, transcripts, and participant lists your own Google account can already see. Elaichi can narrow that further, for example hiding transcripts and leaving only attendance, but it can never widen it beyond what Google Meet grants you.
Can I stop an agent from deleting or changing things in Google Meet?
This connector only reads Google Meet: it lists meetings, transcripts, participants, and users, and cannot create, change, or delete anything, so there is nothing destructive to worry about. Restrictions in Elaichi still apply per action, so you can, for example, allow attendance lookups but block transcripts. A blocked action is never advertised to the AI client, so no prompt can reach it.
What happens to a Google Meet connection when someone leaves?
Offboarding a person in Elaichi ends their access to Google Meet through every connected client at once. If they had shared their Google Meet connection with a team, it keeps working for everyone else on that team. Disconnecting Google Meet once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Put Google Meet in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.