How to connect Gmail to Grok Bot
Connect Gmail to Grok Bot with ClawLink in one click — 60 tools your AI agent can call from chat via hosted OAuth. No API keys, no manual setup.
GmailOAUTH2MCPSend, read, and manage emails. Once connected, Grok Bot can read and act on Gmail from chat — pairing, token refresh, and tool wiring handled for you.
Grok Bot runs on its own cloud computer, so most Gmail guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Gmail setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Gmail actions from chat with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Grok Bot. It runs the ClawLink CLI in its own terminal and pairs your account.
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 gmail
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 Gmail.
1Pair from the terminal
Ask Grok Bot to run the ClawLink CLI. It prints a link you approve once in your browser:
npx -y @useclawlink/cli login- 2
Connect Gmail
One-click OAuth in the dashboard.
- 3
Use it from chat
Ask Grok Bot: "What can you do with Gmail?"
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:
npx -y @useclawlink/cli login # prints an approval link, approve it in your browser
npx -y @useclawlink/cli connect gmailPair 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 Gmail to add label to email 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Gmail is connected in the dashboard, that agent calls the same 60 Gmail tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Gmail MCP for Grok Bot
Looking for a Gmail MCP server for Grok Bot? ClawLink connects Gmail to Grok Bot and exposes 60 Gmail tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using a different agent? The OpenClaw Gmail integration and the Hermes Gmail integration connect the same ClawLink account the same way.
What the Grok Bot Gmail integration can do
60 Gmail 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 60.
30 of 60 Gmail tools for Grok Bot
| Tool | What it does |
|---|---|
Add label to email gmail_add_label_to_email | Add a label to a Gmail message |
Create email draft gmail_create_email_draft | Create a Gmail draft |
Create label gmail_create_label | Create a Gmail label |
Fetch emails gmail_fetch_emails | Search and fetch Gmail messages |
Fetch message by message ID gmail_fetch_message_by_message_id | Get a Gmail message by ID |
Fetch message by thread ID gmail_fetch_message_by_thread_id | Get a Gmail message by thread ID |
Forward message gmail_forward_message | Forward a Gmail message |
Get attachment gmail_get_attachment | Get a Gmail attachment |
Get profile gmail_get_profile | Get the connected Gmail account profile |
List drafts gmail_list_drafts | List Gmail drafts |
List labels gmail_list_labels | List Gmail labels |
List send as gmail_list_send_as | List Gmail send-as aliases |
List threads gmail_list_threads | List Gmail threads |
Reply to thread gmail_reply_to_thread | Reply to a Gmail thread |
Send email gmail_send_email | Send a Gmail message |
Create prompt post gmail_create_prompt_post | Send a one-shot prompt to the Sanity Content Agent |
Get auto forwarding gmail_get_auto_forwarding | Get the auto-forwarding setting for the specified account |
Get contacts gmail_get_contacts | Fetches contacts (connections) for the authenticated Google account, allowing selection of |
Get draft gmail_get_draft | Retrieves a single Gmail draft by its ID |
Get filter gmail_get_filter | Retrieve a specific Gmail filter by its ID |
Get label gmail_get_label | Gets details for a specified Gmail label |
Get language settings gmail_get_language_settings | Retrieve the language settings for a Gmail user |
Get people gmail_get_people | Retrieves either a specific person's details (using resource_name) or lists 'Other Contacts' |
Get vacation settings gmail_get_vacation_settings | Retrieve vacation responder settings for a Gmail user |
List filters gmail_list_filters | List all Gmail filters (rules) in the mailbox |
List forwarding addresses gmail_list_forwarding_addresses | List all forwarding addresses for the specified Gmail account |
List history gmail_list_history | List Gmail mailbox change history since a known startHistoryId |
Search people gmail_search_people | Searches contacts by matching the query against names, nicknames, emails, phone numbers, and |
Settings send as get gmail_settings_send_as_get | Retrieve a specific send-as alias configuration for a Gmail user |
Batch modify messages gmail_batch_modify_messages | Modify labels on multiple Gmail messages in one efficient API call |
Try it: find the Gmail tool you need
Browse the 30 Gmail tools
Click any tool to see exactly what Grok Bot can do and copy a ready-to-use prompt.
Example prompts
Use Gmail to add label to email and walk me through the result in plain English.
Create it in Gmail for me, then confirm the important fields before you finish.
Create it in Gmail for me, then confirm the important fields before you finish.
Pull the relevant data from Gmail, summarize it in plain English, and point out anything that needs attention.
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 Gmail working from chat.
| Manual | ClawLink | |
|---|---|---|
| Connection flow | Register a Gmail app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Gmail 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 Gmail. | 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 Gmail actions to the runtime in a format your agent can reliably use. | 60 tools for Gmail are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Gmail 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 Gmail in the browser, and the 60 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 comparison.
Troubleshooting
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 Gmail 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 Gmail tools
Gmail 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 Gmail 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.
Gmail 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 Gmail and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete.
FAQ
Is there a Grok Bot Gmail integration?
Yes. ClawLink is the fastest way to connect Grok Bot to Gmail: link your Gmail account once in the browser and Grok Bot can call the Gmail API through 60 ready-made tools — no custom code or token handling.
How do I connect Gmail 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 gmail to authorize Gmail. 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 Gmail to Grok Bot?
About two minutes. Sign in, click Connect next to Gmail in the dashboard, authenticate, and Grok Bot can use it from the next chat message.
Why use ClawLink instead of wiring Gmail 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 Gmail 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.
