# How to connect Google Drive to Grok Bot (no API keys) > Connect Google Drive to Grok Bot with ClawLink in one click — 76 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup. Web version: https://claw-link.dev/grokbot/google-drive Grok Bot runs on its own cloud computer, so most Google Drive guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Google Drive setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Google Drive actions from chat with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Grok Bot to set up ClawLink:** > Set up ClawLink for me and tell me when it's ready. > 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login` > 2. I'll approve it in my browser, then reply "approved". > 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect google-drive` > 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Grok Bot to Google Drive. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect Google Drive** — `npx -y @useclawlink/cli connect google-drive`, then approve in the browser. 3. **Use it from chat** — ask Grok Bot in plain English. **The same CLI works from any agent with shell access:** ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect google-drive # connect Google Drive (browser OAuth) npx -y @useclawlink/cli actions google-drive # list available actions npx -y @useclawlink/cli run google-drive --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval: ```bash npx -y @useclawlink/cli login # prints an approval link, approve it in your browser npx -y @useclawlink/cli connect google-drive ``` Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI. Verify the connection by asking Grok Bot: > Use Google Drive to googledrive copy file advanced and walk me through the result in plain English. ### Using a different agent? The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Google Drive is connected in the dashboard, that agent calls the same 76 Google Drive tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Google Drive MCP for Grok Bot Looking for a Google Drive MCP server for Grok Bot? ClawLink connects Google Drive to Grok Bot and exposes 76 Google Drive tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using a different agent? The [OpenClaw Google Drive integration](https://claw-link.dev/openclaw/google-drive) and the [Hermes Google Drive integration](https://claw-link.dev/hermes/google-drive) connect the same ClawLink account the same way. ## What the Grok Bot Google Drive integration can do 76 Google Drive tools are ready for Grok Bot once the account is connected. The 30 below are the ones people reach for most; your agent can call all 76. ### 30 of 76 Google Drive tools for Grok Bot | Tool | What it does | |---|---| | **Copy file advanced** `googledrive_copy_file_advanced` | Copy a file with advanced options | | **Create comment** `googledrive_create_comment` | Create a comment on a Drive file | | **Create drive** `googledrive_create_drive` | Create a new shared drive | | **Create file** `googledrive_create_file` | Create a new file or folder with metadata | | **Create file from text** `googledrive_create_file_from_text` | Create a Drive file from text content | | **Create folder** `googledrive_create_folder` | Create a new folder in Google Drive | | **Create permission** `googledrive_create_permission` | Share a file or folder with users or make it public | | **Create reply** `googledrive_create_reply` | Reply to a comment on a Drive file | | **Create shortcut to file** `googledrive_create_shortcut_to_file` | Create a shortcut to an existing Drive item | | **Download file** `googledrive_download_file` | Download a file from Google Drive | | **Edit file** `googledrive_edit_file` | Update a Drive file's content (non-Google Workspace) | | **Export google workspace file** `googledrive_export_google_workspace_file` | Export a Google Workspace doc to a specific format | | **Find file** `googledrive_find_file` | Search for files in Google Drive by name, MIME type, or query | | **Find folder** `googledrive_find_folder` | Find a folder in Google Drive by name | | **Get about** `googledrive_get_about` | Get user, Drive, and storage quota info | | **Get drive** `googledrive_get_drive` | Get a shared drive by ID | | **Get file metadata** `googledrive_get_file_metadata` | Get a file's metadata by ID | | **List comments** `googledrive_list_comments` | List comments on a Google Drive file | | **List permissions** `googledrive_list_permissions` | List a file's sharing permissions | | **List replies** `googledrive_list_replies` | List replies to a comment | | **List revisions** `googledrive_list_revisions` | List a file's revision history | | **List shared drives** `googledrive_list_shared_drives` | List the user's shared drives | | **Move file** `googledrive_move_file` | Move a file to a different folder | | **Update file put** `googledrive_update_file_put` | Update file metadata like name, description, or parents | | **Upload file** `googledrive_upload_file` | Upload a file to Google Drive | | **Upload from URL** `googledrive_upload_from_url` | Fetch a URL and upload it to Google Drive | | **Download file operation** `googledrive_download_file_operation` | Download file content using long-running operations | | **Generate IDS** `googledrive_generate_ids` | Generates a set of file IDs which can be provided in create or copy requests | | **Get app** `googledrive_get_app` | Get information about a specific Drive app by ID | | **Get changes start page token** `googledrive_get_changes_start_page_token` | Get the starting pageToken for listing future changes in Google Drive | ## Example prompts **Googledrive Copy File Advanced** > Use Google Drive to googledrive copy file advanced and walk me through the result in plain English. **Googledrive Create Comment** > Use Google Drive to googledrive create comment and walk me through the result in plain English. **Googledrive Create Drive** > Use Google Drive to googledrive create drive and walk me through the result in plain English. **Googledrive Create File** > Use Google Drive to googledrive create file and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Drive working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Google Drive app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Google Drive through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Google Drive. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Google Drive actions to the runtime in a format your agent can reliably use. | 76 tools for Google Drive are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Google Drive to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Grok Bot users instead. You install the plugin once, connect Google Drive in the browser, and the 76 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ### Connection succeeds but no tools appear Reconnect Google Drive from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Google Drive tools Google Drive tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Google Drive call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Google Drive returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting Google Drive and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a Grok Bot Google Drive integration? Yes. ClawLink is the fastest way to connect Grok Bot to Google Drive: link your Google Drive account once in the browser and Grok Bot can call the Google Drive API through 76 ready-made tools — no custom code or token handling. ### How do I connect Google Drive to Grok Bot with ClawLink? Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal and approve the link it prints, then `npx -y @useclawlink/cli connect google-drive` to authorize Google Drive. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: no config files or API keys to manage. ### How long does it take to connect Google Drive to Grok Bot? About two minutes. Sign in, click Connect next to Google Drive in the dashboard, authenticate, and Grok Bot can use it from the next chat message. ### Why use ClawLink instead of wiring Google Drive up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Google Drive working from chat. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ## Related - [Google Super](https://claw-link.dev/grokbot/google-super) — Unified access to multiple Google services in one integration - [Google Analytics tools](https://claw-link.dev/grokbot/google-analytics) — Connect Google Analytics properties through hosted Google OAuth - [Connect Google BigQuery](https://claw-link.dev/grokbot/google-bigquery) — Query and manage datasets, tables, and jobs in Google BigQuery