Does Codex support the Google Drive MCP server?

Yes. Codex connects to the Google Drive 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 Drive to Codex?

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

Which Google Drive tools can Codex use?

All 29 Google Drive tools your team allows, such as Update Permission, Export File, Delete Comment. Admins can narrow that list per team.

Can I control which teammates use Google Drive in Codex?

Yes. Role-based access control decides who can use Google Drive 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 Drive tools?

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

Connect Google Drive to Codex (MCP setup guide)

Ask Codex to use the delete shared drive tool in Google Drive
Ask Codex to use the update shared drive tool in Google Drive
Ask Codex to use the update comment or reply tool in Google Drive
Ask Codex to use the get drive account information tool in Google Drive
Ask Codex to use the list changes tool in Google Drive

1. Enable Google Drive in Metorial
In your Metorial portal, enable the Google Drive 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 Drive tools.

Once Google Drive 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.

Update Permission: Change the role of an existing permission on a file or folder.
Export File: Export a Google Workspace file (Docs, Sheets, Slides, Drawings) to a standard format such as PDF, DOCX, XLSX, CSV, or plain text.
Delete Comment: Delete a comment from a file.
Reply to Comment: Add a reply to an existing comment thread on a file.
Upload File: Upload a file with content to Google Drive.
List Permissions: List all permissions (sharing settings) for a file or folder.
Create Comment: Add a comment to a file.
Copy File: Create a copy of an existing file in Google Drive.
Share File: Share a file or folder with a user, group, domain, or make it accessible to anyone with a link.
Create Shared Drive: Create a new shared drive for team collaboration.
List Shared Drives: List all shared drives the authenticated user has access to.
Create File or Folder: Create a new file or folder in Google Drive.
List Comments: List all comments on a file, including threaded replies.
Remove Permission: Remove a permission (revoke access) from a file or folder.
List Revisions: List the revision history of a file.
And 14 more on the Google Drive MCP server page.

Limit which Google Drive 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 Drive 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 Drive to AI agents with Metorial.

Does Codex support the Google Drive MCP server?
Yes. Codex connects to the Google Drive 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 Drive to Codex?
No. You sign in to Google Drive once through Metorial, and Codex uses that connection. No API keys go into Codex's settings.
Which Google Drive tools can Codex use?
All 29 Google Drive tools your team allows, such as Update Permission, Export File, Delete Comment. Admins can narrow that list per team.
Can I control which teammates use Google Drive in Codex?
Yes. Role-based access control decides who can use Google Drive 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 Drive tools?
Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.