Google Meet MCP Server

Soon

Connect Google Meet to Claude, ChatGPT, Grok, Perplexity, Claude Code, Codex, Cursor or Antigravity — one connection, from the subscription you already pay for.

The Google Meet MCP server is a connector on HeyMetra. Authorise Google Meet once with OAuth and it becomes tools your assistant can call — read-only, so nothing here can change your account.

Example exchange

At a glance

Category: Work
How you connect: OAuth
Access: Read-only
Status: Soon

What Google Meet is

Google Meet holds the part of a week that nobody writes down. A calendar says a meeting was going to happen; Meet says it did, how long it ran, who actually joined, and — where the meeting was transcribed — what was said in it. That is the record people go looking for weeks later and cannot find, because it is spread across one conference record per meeting and nothing lists them by subject.

What it can do, and what you can switch off

Each of these is a switch on the connection itself. Turn one off and the assistant is told, and cannot use it — so a team can read order volume without ever reaching the payouts. Where Google Meet itself will not serve something, it says so here rather than answering as though there were nothing to find.

Direct API access

Reads

Let your assistant use this account's own API for anything HeyMetra's other operations do not cover. It reads directly, and what comes back is the provider's own answer rather than a figure HeyMetra has checked. It can also propose changes — those are never applied until you approve them, and HeyMetra cannot undo one afterwards.

Limit A transcript exists only where somebody turned transcription on during the call, and that is off by default.

Limit A recording is named, never fetched: the API returns where it was put in Drive, and this connector holds no Drive access.

Limit Conference records are kept for 30 days, so a meeting older than that is gone from Meet whatever is asked.

Setting it up

You sign in on Google Meet's own screen, so no password reaches us. Then add HeyMetra as a remote MCP server where you ask.

Sign in with the account that was in the meetings

Meet answers about the conferences that account can see. A meeting somebody else hosted and never invited them to is not one of them, whatever else is shared.

Worth knowing An organisation's meetings are not pooled: connecting the admin's account does not reach everybody's calls.
Name the connection after the person

One sign-in is one connection and it is named after its address, because that is the only thing that tells two connected Google accounts apart when you ask.
If you want the words, turn transcription on

In the meeting itself, before it starts or while it runs. It is off by default and nothing can produce a transcript afterwards — a call that was not transcribed is a call this connector can tell you the length and the guest list of, and nothing more.

Worth knowing A Workspace admin can default it on for the whole organisation. It needs Business Standard or above.

When it does not work

These are the things that actually go wrong, written from what you see rather than from what caused it.

Google warns that this app is not verified.

Reading meetings is what Google calls a sensitive permission, and an app asking for one shows that screen until Google has reviewed it — the same as Calendar, Analytics and Search Console.

Fix Continue past it if you are comfortable, or wait for the review. Nothing about the connection behaves differently.

Meetings are listed but none has a transcript.

A transcript exists only where somebody turned it on during the call. It is off by default, and it is a Workspace edition feature — Business Standard and above.

Fix Turn transcription on in the meeting, or ask an admin to default it on. Nothing can produce one afterwards.

A recording is listed but cannot be played or read.

Meet reports where a recording was PUT — a file in Drive — and this connector holds no access to Drive. That is deliberate: Drive is Google's restricted class and asking for it would put an independent security assessment between you and this connector.

Fix Open the file in Drive yourself. If what you wanted was what was said, ask for the transcript instead — that comes back as text without touching Drive.

Where you ask

Frequently asked

Is the Google Meet connector available yet?

Not yet — Google Meet is marked Soon. When it opens it is on every plan: plans differ in how many accounts you connect at once, never in which ones. The connectors page names everything that is ready today.

What can I ask about Google Meet once it is connected?

Whatever the tools can answer — you type the question into Claude or ChatGPT, not into anything of ours. For example: “What was decided in yesterday's call?” or “Who actually joined the Monday standup this month?”

Can HeyMetra change my Google Meet account?

No. This connector is read-only: HeyMetra has no tool that writes to Google Meet.

How do I connect Google Meet to Claude or ChatGPT?

You connect Google Meet to HeyMetra once — by signing in on Google Meet, so no password reaches us — and then add HeyMetra as a remote MCP server in whichever of them you use. There is a setup page here for each one.

What does the Google Meet connector cost?

Nothing on its own. Plans are priced by how many connectors and seats you get, not per connector or per tool call, and every plan can reach every connector that is live. The pricing page carries the current figures.

Connectors next to this one

The other half of the question lives in a different category: Zoho Marketing Automation data sits behind the same connection, which is what lets one answer cover both.

Google Meet is not available yet

This page exists so it is ready when the connector is. Do not buy a plan for Google Meet — tell us you want it instead, and we will say when it lands rather than when we hope it will.

Tell us you want it See what works today