# 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. Source: https://elaichi.ai/connectors/googlemeet/ ## Facts | | | | --- | --- | | Application | Google Meet | | Category | Video | | AI tools | 10 | | Authentication | Connects over OAuth | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Google Meet is connected - 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. ## Connect Google Meet in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Google Meet. 2. Optionally set Share with, then press Connect. 3. Approve it in Google Meet. Google Meet's own window opens. Whoever approves it decides what this connection can reach. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Google Meet tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Google Meet to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Google Meet to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Google Meet tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Google Meet through Elaichi ### Catch the deal up after a discovery call Sales. 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. ### Turn an escalation call into case notes Support. 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. ### Check who showed up to the quarterly review Customer Success. See which participants joined the account review in Google Meet, how long each stayed, and whether the decision maker you invited ever appeared. ### Prepare interview debriefs from the recording People. 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. ### Find the decision buried in last week's standup Operations. Ask which meeting agreed the vendor change and what exactly was decided, and get the transcript passage with the date and the people present. ### Get a digest of the meetings you missed Leadership. 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. ## 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 my team share one Google Meet connection? Yes. One person connects Google Meet in Elaichi and shares it with a team, and nobody else ever handles a Google credential or approves anything in Google. Each teammate still signs in to Elaichi as themselves, so every question asked of Google Meet is logged under the name of the person who asked it. ### 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. ## All 10 Google Meet tools Every tool below is callable through https://api.elaichi.ai/mcp once Google Meet is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Google Meet conference records** (List). List Google Meet conference records. Returns a collection of conferenceRecords objects from the Google Meet API. - **Get single Google Meet conference record by ID** (Get). Get a single Google Meet conference record by id. Returns the conference record object. Required: id. - **List all Google Meet conference record transcripts** (List). List transcripts for a Google Meet conference record. Returns a collection of transcript objects associated with the specified conference record. Required: conference_record_id. - **Get single Google Meet conference record transcript by ID** (Get). Get a single transcript from a Google Meet conference record by id. Returns the transcript object for the specified conference record and transcript. Required: conference_record_id and id. - **List all Google Meet conference record transcript entries** (List). List transcript entries for a specific Google Meet conference record transcript. Returns a collection of transcript entries. Required: conference_record_id, conference_record__transcript_id. - **Get single Google Meet conference record transcript entry by ID** (Get). Get a single transcript entry from a Google Meet conference record transcript by id. Required: conference_record_id, conference_record__transcript_id, id. - **List all Google Meet conference record participants** (List). List participants for a specific Google Meet conference record. Returns an array of participant objects. Required: conference_record_id. - **Get single Google Meet conference record participant by ID** (Get). Get a single participant from a Google Meet conference record by id. Returns the participant object. Required: conference_record_id and id. - **List all Google Meet user info** (List). Retrieves basic profile information about the authenticated user in Google Calendar. The response includes essential details such as the user's unique identifier (sub), full name (name), first name (given_name), last name (family_name), profile picture URL (picture), and email address (email). - **List all Google Meet users** (List). List all Google Workspace users in the directory. Returns a collection of user objects including id, primaryEmail, and name.