Does Codex support the Google Meet MCP server?

Yes. Codex connects to the Google Meet MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.

Do I need an API key to connect Google Meet to Codex?

No. You sign in to Google Meet once through Metorial, and Codex uses that connection. No API keys go into Codex's settings.

Which Google Meet tools can Codex use?

All 22 Google Meet tools your team allows, such as List Transcripts, Get Recording, Add Space Member. Admins can narrow that list per team.

Can I control which teammates use Google Meet in Codex?

Yes. Role-based access control decides who can use Google Meet and which of its tools appear in Codex, and every call is logged with the person's identity.

What if Codex doesn't show Google Meet tools?

Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.

Connect Google Meet to Codex (MCP setup guide)

Ask Codex to use the get transcript entry tool in Google Meet
Ask Codex to use the get smart note tool in Google Meet
Ask Codex to use the list transcripts tool in Google Meet
Ask Codex to use the get recording tool in Google Meet
Ask Codex to use the add space member tool in Google Meet

1. Enable Google Meet in Metorial
In your Metorial portal, enable the Google Meet MCP server and sign in with the account that owns the data. Access stays governed by your team policies.
2. Add the server and sign in
The Codex CLI, IDE extension and ChatGPT desktop app share this config.
```
codex mcp add metorial --url <your-magic-mcp-url>
codex mcp login metorial
```
3. Check the connection
Type /mcp in Codex to see Metorial and its Google Meet tools.

Once Google Meet is enabled in Metorial, teammates sign in with SSO and get the same connection in Codex, with only the tools their role allows.

One link covers every app you approve. See how the MCP gateway handles access, roles and audit logs for the whole company.

List Transcripts: List transcripts from a conference record.
Get Recording: Retrieve metadata for a specific recording, including its state and Google Drive file location.
Add Space Member: Add a member to a Google Meet space.
List Recordings: List recording resources from a conference record.
Update Meeting Space: Update the configuration of an existing Google Meet meeting space.
Create Meeting Space: Create a new Google Meet meeting space with optional configuration.
Get Conference Record: Retrieve details of a specific conference record including start/end times and the associated meeting space.
List Transcript Entries: List individual transcript entries from a transcript.
Get Participant Sessions: Retrieve the individual join/leave sessions for a specific participant in a conference.
Get Transcript: Retrieve metadata for a specific transcript including its state and Google Docs location.
List Participants: List participants of a conference.
List Space Members: List all members configured in a Google Meet space.
Get Meeting Space: Retrieve details about a Google Meet meeting space by its resource name or meeting code.
List Conference Records: List conference records for past and ongoing meetings.
Remove Space Member: Remove a member from a Google Meet space.
And 7 more on the Google Meet MCP server page.

Limit which Google Meet tools Codex sees with enabled_tools and disabled_tools on the metorial server in config.toml.
Set default_tools_approval_mode to auto, prompt, writes or approve. writes prompts only for tools that are not marked read-only.
Type /mcp in the composer to see the connected servers.
Override the approval behavior for a single Google Meet tool with tools.<tool>.approval_mode.

Metorial is listed but tools are missing: Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.
Metorial times out at startup: Codex waits 10 seconds by default. Raise startup_timeout_sec under [mcp_servers.metorial] in ~/.codex/config.toml.
Long tool calls fail after a minute: The default tool timeout is 60 seconds. Raise tool_timeout_sec for the metorial server in config.toml.

Based on the Codex MCP documentation.

Frequently asked questions

Common questions about connecting Google Meet to AI agents with Metorial.

Does Codex support the Google Meet MCP server?
Yes. Codex connects to the Google Meet MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.
Do I need an API key to connect Google Meet to Codex?
No. You sign in to Google Meet once through Metorial, and Codex uses that connection. No API keys go into Codex's settings.
Which Google Meet tools can Codex use?
All 22 Google Meet tools your team allows, such as List Transcripts, Get Recording, Add Space Member. Admins can narrow that list per team.
Can I control which teammates use Google Meet in Codex?
Yes. Role-based access control decides who can use Google Meet and which of its tools appear in Codex, and every call is logged with the person's identity.
What if Codex doesn't show Google Meet tools?
Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.